Calm, empathetic reply to an angry customer
Turn a furious customer message into a reply that acknowledges the problem, takes ownership and offers a clear next step without grovelling.
Reply to an unhappy customer with a sincere, specific apology and a clear remedy, not canned phrases.
Write a reply to an unhappy customer.
Customer's message:
{{complaint}}
What actually went wrong (internal facts): {{what_happened}}
What we can offer: {{remedy}}
What we cannot do: {{limits}}
Brand voice: {{voice}}
Channel: {{channel}}
Write the reply so that:
- It opens by acknowledging the specific problem in plain words, with an apology for it. No "we apologise for any inconvenience".
- It gives a short, honest explanation without excuses or blaming a third party.
- It states exactly what we will do, by when, and who they can contact.
- It does not promise anything beyond what is listed under "What we can offer".
- It matches the customer's emotional level, calm if they are angry and brisk if they are rushed.
- It is under 150 words.
Output format: the reply, then one line noting the single biggest risk in the wording and a safer alternative.Supplying real internal facts allows an honest explanation rather than a canned one. Keep the 'cannot do' field filled so the reply never overpromises.
Licensed CC0 (public domain) Version 1 · history
Turn a furious customer message into a reply that acknowledges the problem, takes ownership and offers a clear next step without grovelling.
Say no to a refund or policy-exception request clearly and kindly, explain the reason, and offer real alternatives so the customer feels respected.
Turn your week's work into a crisp status update covering progress, blockers and next steps.
Paste an incoming email and your intent, and get a reply that answers every point in the right tone.
Say no clearly and kindly to a request or invitation, protecting the relationship and your time.
Deliver hard news or feedback clearly and kindly, without burying the point or sounding cold.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.