Skill Locker
All skills
v1.3.03 loop iterations

Refund & Dispute Response

Refund requests are not a tax to be minimised — they're the highest-stakes message you'll send a customer. The Refund & Dispute Response handles them strategically: grant gracefully, offer alternatives, decline professionally. How you say no matters as much as whether you say yes.

What this skill does

Refund decisions are usually framed as a binary — yes or no — when the strategic answer almost always lives in between. The Refund & Dispute Response runs a four-dimensional assessment before writing a word: legitimacy of the claim, customer value over time, business impact of the resolution, and emotional state of the requester. Those four together point to one of four strategies — Grant with Grace, Offer an Alternative, Partial Resolution, Decline Professionally — and the response is built from there.

A graceful refund is a retention tool, not a loss. A customer whose problem is resolved well becomes more loyal than one who never had a problem, and a same-day full refund with a discount code for next time often converts a leaving customer into a future one. The skill enforces that behaviour where it fits — speed, sincerity, and a small additional gesture — and rejects the corporate instinct to drag the resolution out across multiple emails.

Decline responses are where most businesses lose customers unnecessarily. "Unfortunately, our policy states..." is rejected as an opener every time. People accept "no" when they understand the reasoning — service fully delivered, well outside the window, pattern of misuse — and they reject "no" when it sounds like a rule being read off a page. The RESOLVE structure (Recognise, Explain, State, Offer, Leave valued, Verify, Exit) keeps the response human even when the answer is firm.

Every response ships with a prepared push-back reply. The customer often does not accept the first answer, and improvising the second message — usually written under more pressure than the first — is where escalations start. The skill writes the second message in advance: holding the line where the line should hold, conceding where the goodwill is worth more than the policy, and leaving the door open in a way that doesn't sound desperate.

Internal notes are part of the deliverable. Flag the account if there's a pattern. Note policy implications if this decision sets precedent. Capture whether the situation reveals a product or process issue worth fixing upstream — because the most useful refund response is often the one that stops similar refunds being requested next quarter. Chargebacks are flagged for separate handling, since the deadlines and evidence requirements are not the same conversation.

When this triggers

  • ·A customer wants their money back and you're staring at the reply box for the third time
  • ·You need to decline a refund without losing the customer or the review
  • ·A grey-area request landed and you're not sure between full, partial, or alternative
  • ·A chargeback came in and you have a deadline plus an evidence requirement
  • ·You keep refunding everything to avoid arguments and the leakage is showing in the margin

Example

Trigger

User: 'Customer used my £89 course for 4 weeks, completed 3 of 6 modules, now wants full refund saying it wasn't what they expected. Standard customer, no history. My policy is 14-day no-questions, then case-by-case.'

Output

Situation Assessment Legitimacy: Grey area — outside 14-day window, partially consumed Customer value: Standard, first purchase Business impact: Low (£89) Emotional state: Calm but firm Recommended strategy: Partial Resolution Response Hi [name], Thanks for taking the time to write — I'd rather hear this directly than have you quietly disappointed. You're outside the 14-day window we use for no-questions refunds, and you've worked through half the material. So a full refund isn't something I can offer here without rewriting the policy for everyone, which wouldn't be fair. Here's what I can do: a 50% refund (£44.50) plus keep your access to the remaining modules in case the rest changes your mind. That feels honest given where things are — you've used part of it, we're meeting in the middle. If you'd rather complete the course and tell me specifically what didn't land for you, I'd take that feedback seriously and we can revisit. No pressure either way. Let me know which works for you. [Sign-off] If they push back If they insist on the full amount: hold the partial position, but reframe — "I want to be fair to you AND fair to the other 340 students who've finished the course at full price. The 50% offer is the line I can hold." Internal notes · No flag on the account — clean request, fair grey area · Policy is working as intended; no exception precedent created · If pattern of buyer's remorse > 14 days appears 3+ more times, revisit policy length

Get this skill + 7 more

Get the full Customer Support pillar (8 skills) or the complete library.

Get the full stack — $299

What you get

  • 173-line SKILL.md, ready to drop into ~/.claude/skills/
  • Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
  • Triggers automatically when relevant — no command to remember
  • Lifetime updates as the skill is refined further

More from Customer Support

Browse the full library

297 skills across 31 categories. One purchase, lifetime updates.

See all bundles