Say no in the first two sentences, give the reason in one plain line, and follow with what you can do instead. Do not bury the refusal under apologies, do not hide behind “our policy” without explaining it, and do not hint that the answer might change if it will not. A clear no with a useful alternative keeps more goodwill than a vague maybe that ends in the same no a week later.
Why do refusals by email go wrong?
Most refusals fail in one of four ways:
- The no is buried. Three sentences of sympathy before the answer, so the customer reads it twice to find out what you decided.
- Too many apologies. Apologising for a rule you stand behind sounds like the rule is unfair.
- Policy-speak. “As per our terms and conditions” tells the customer you did not think about their case.
- False hope. “We’ll see what we can do” when you already know the answer. The eventual no then feels like a broken promise.
Each one creates a follow-up email. A clear refusal usually ends the thread; a vague one starts an argument.
What does a good no look like?
Four parts, in this order:
- The answer. “We can’t refund this order.”
- One reason, in plain words. “It was delivered more than 30 days ago, which is the limit for refunds.” (Use your own rule.)
- What you can do. An alternative, a partial option, or a useful next step.
- A clear close. What happens next, or nothing more if the matter is settled.
Keep it short. A refusal gains nothing from length; every extra sentence gives the customer something to argue with.
What does that look like in practice?
A refund outside the window. The customer writes that they never used the product and want their money back, two months after delivery.
Vague: Hi Sam, thank you so much for reaching out, and we’re really sorry to hear the product wasn’t right for you. We completely understand how frustrating this must be. Unfortunately, as per our terms and conditions, we are unable to process refunds after a certain period. We’ll look into whether anything can be done. Kind regards, Customer Service
Clear: Hi Sam, we can’t refund this order: it was delivered in July, and refunds are possible for 30 days after delivery. What we can do is exchange it for another item of the same value, or give you store credit for the full amount. Just reply with which you prefer. Best, Lisa
A feature request you will not build:
Hi Priya, thanks for the suggestion. We’re not planning to add a calendar export: we’re keeping the app focused on invoicing, and a calendar would pull it in a different direction. You can export your invoices as a spreadsheet and import the due dates into your calendar, which covers most of what you describe. Best, Tom
Only offer a workaround that really exists and that you have tried yourself.
A discount request:
Hi Alex, we don’t offer discounts on single orders, so the price stays at €120. If you order ten or more, the volume price on our pricing page applies automatically. Best, Lisa
Which phrases make a refusal worse?
| Phrase | Why it hurts | Instead |
|---|---|---|
| “Unfortunately, as per our policy…” | Sounds like a form letter | State the rule itself: “Refunds are possible for 30 days” |
| “We apologise for any inconvenience” | Vague, and apologises for the wrong thing | Skip it, or be specific: “Sorry the size didn’t work out” |
| “There’s nothing we can do” | Closes every door | Say what you can do, even if small |
| “We’ll see what we can do” | False hope if the answer is fixed | Only say it if you will genuinely check, and say when you’ll reply |
| “I’m afraid…” | Softens so much the no gets lost | Start with the answer |
| “Please understand that…” | Tells the customer how to feel | Give the reason and let it stand |
When should you make an exception?
Sometimes the right answer is yes, even against your own rule. A few questions help you decide consistently:
- Was it partly our fault? A delayed delivery, unclear information on the website: lean towards yes.
- Is the cost small compared to the relationship? A long-standing customer asking for a small exception.
- Would you do the same for the next customer who asks? If not, the exception will cause trouble later.
If you make an exception, say it is one, so it does not become the new rule: “Our refund window is 30 days, but as the delay was on our side, we’ll refund this one.” And write it down, so a colleague who gets the same request knows what was decided.
What if the customer pushes back?
Answer once more, briefly, and do not repeat the whole reasoning.
- Acknowledge what is new in their reply, if anything is.
- Restate the answer in one sentence.
- Offer the alternative again, or a different route if one exists.
- Hand over if needed. If the customer is very unhappy or the stakes are high, let someone senior reply. A new voice often settles what a third reply from the same person cannot.
Do not change your answer just because the second email is angrier. If a fact changes, the answer can change; if only the tone changes, it should not.
Should AI write your refusals?
It can draft them, but a person should always send them. Refusals combine judgement, money and emotion, which is exactly where a fluent draft can do damage: an apology that concedes a point, an offer you do not make, an exception that becomes a precedent. Draft or auto-send: when should AI send customer email itself? lists the kinds of email that should always stay with a person.
With ReplyPen, every reply is a Draft that you send yourself. Drafts follow your Tone profile, the Check note shows which policy page or past reply the answer relied on, and when you correct how a Draft says no, ReplyPen records it in the Knowledge log for the next similar request.
For the full routine around fast, accurate replies, read How to answer customer email faster without lowering quality.
