How to Respond to a Refund Request: Yes, No and the Grey Zone
10 min read
How to respond to a refund request depends on a decision you make before you write a word: yes, no, or an exception. This lesson gives you a reply for each, the prompt behind them, and the policy that makes most of these emails easy.
Refund emails are stressful because two decisions are tangled together. One is about money: do they get it back? The other is about words: how do I say it? Owners try to solve both at once, at the keyboard, and end up with a reply that's either a pushover or a wall.
Separate them. Decide first. Then let AI help with the wording, which is the easy half.
Start with a policy a customer can read in ten seconds
Most refund arguments come from a policy that's missing, vague or hidden. If yours lives in your head, every request is a negotiation.
A usable policy answers five questions: how long do they have, what condition must the item be in, what's excluded (custom work, sale items, opened consumables), how is the money returned, and who pays return shipping. For services: what happens on cancellation, and what's your remedy when the work wasn't right?
The free Refund & Return Policy Writer builds one from a short interview. Put it on your website, your receipts and your booking confirmations. A policy the customer saw before buying is one you can point to without a fight.
A legal note, kept short. Across most of Canada and the US, a shop isn't generally required to refund a non-defective item because the customer changed their mind, but you are expected to honour the policy you posted, and faulty goods and services not delivered are a different matter with rules that vary by province and state. Distance sales and some contracts carry cancellation rights. If refunds are a big part of your business, have a professional look at your policy once.
The three replies
Yes. The easiest email you'll send, and most businesses still do it badly by making the customer wait and wonder. Confirm the amount, the method, and the date they'll see it. Three sentences. A fast, gracious yes is some of the cheapest marketing you'll ever do, because people tell friends about it.
No, with somewhere to go. A bare no starts an argument. A no with an alternative usually ends one. Store credit, an exchange, a repair, a discount on the next order, a free return visit to fix the work. State the policy once, plainly, without "unfortunately" or "as per". Then spend the rest of the reply on what you can do.
The exception. Outside the policy, but you're going to say yes anyway: a loyal customer, a small amount, a situation where you'd want the same grace. Say yes warmly and label it as a one-time exception, so it doesn't become the new policy in their mind or in their friends'.
Here is my support brief, including our refund policy:
[PASTE BRIEF]
A customer asked for a refund. Personal details removed.
My decision: [YES IN FULL / NO, BUT I CAN OFFER ___ /
ONE-TIME EXCEPTION BECAUSE ___]
Draft the reply. Rules:
- First sentence gives the decision. No build-up.
- If yes: amount, method, and when they'll see it.
- If no: state the relevant policy once in plain words, then
the alternative I'm offering and how to take it up.
- If exception: warm, and say clearly it's a one-time
exception to our usual policy.
- 4 to 6 sentences, our voice. No "unfortunately", no
"as per our policy", no "we regret to inform you".
- Do not offer anything I did not decide. Use only my facts.
Facts: [ORDER DATE, WHAT THEY BOUGHT, WHAT THEY SAID WAS WRONG]
Customer message: [PASTE]Deciding the grey-zone ones
When you can't make up your mind, ask for the business case, not the verdict:
Help me think through a refund decision. Do not decide for me.
Situation: [WHAT HAPPENED]
Our policy says: [POLICY]
Amount at stake: $[AMOUNT]
What I know about this customer: [HISTORY, WITHOUT NAMES]
Lay out: the cost of saying yes, the cost of saying no
(including a possible chargeback, a bad review, and my time
arguing), what a fair middle option could be, and what
precedent each choice sets. Keep it to one screen.Two costs get forgotten. A card dispute can cost you the sale amount, a dispute fee and an hour of paperwork, so for small sums a refund is often cheaper than being right. And your own time has a price. If you've spent forty minutes drafting replies over a $35 order, you've already lost.
Set a threshold for your team: "Anyone can approve a refund up to $50 without asking." It speeds things up, it tells staff you trust them, and it stops small issues from becoming long threads.
Watch the pattern, not only the case
Once a month, list the refunds and ask what they have in common. One product? One courier? One staff member's jobs? A service customers misunderstand because of how your website describes it? Paste the list, with names removed, and ask your assistant to group the causes. Five refunds with one cause is a product problem wearing a customer service costume.
Where this breaks
AI is a poor judge of fairness between you and a customer it knows nothing about, and it tends to draft generously. Left alone, it offers refunds, discounts and free months you never approved. That's why the prompts above make you state the decision before any drafting happens. Read every draft for promises before it goes out.
Try it now
Check whether a customer can find your refund policy in under ten seconds on your website. If not, write it today with the policy tool and publish it. Then save three template replies, one for each decision, in your inbox templates from Chapter 2.