Browse
Support

Reply to an angry customer without sounding like a bot

Paste the complaint and what really happened, and get a reply that deals with the problem in the first line, says what happens next and when, and skips the canned apology.

No votes yet this week
Output
Text
Written with
Claude Fable 5.1
Added

The prompt

A customer is angry. Help me write the reply.

Their message:
<message>
[PASTE IT]
</message>

What actually happened, honestly: [e.g. we shipped the wrong size, our fault. Or: their bank declined the card, not us]
What I can offer: [e.g. a replacement sent today, a refund, a credit, or nothing beyond fixing it]
What I can't do: [e.g. refund the delivery charge, expedite internationally]
How our brand sounds: [e.g. friendly and direct, formal]

Write it like this:
- The first sentence deals with their actual problem. No "Thank you for reaching out" and no "We apologise for any inconvenience".
- If it's our fault, say so in plain words. If it isn't, explain what happened without blaming them.
- Say exactly what happens next and when. A day of the week beats "as soon as possible".
- If they asked for something I can't do, say no clearly and offer the nearest thing I can.
- Under 150 words. Sign off with my first name: [NAME].

Then give me one line on what we should change internally so this doesn't happen again, if anything.
  • customer-support
  • email
  • tone

What it generates

Example

NoteThis is an example. Results change between runs and model versions. Claude Prompts is a fan project and is not affiliated with Anthropic.

Getting the most from this prompt

Skip the opening ritual

"Thank you for reaching out. We're sorry for any inconvenience this may have caused." Every angry customer has read that sentence a hundred times, and it tells them a template is answering. The prompt bans it and makes the first line about their problem. When the reply opens with "You ordered a medium and we sent you a large", the reader knows a person looked.

Whose fault it was

The "what actually happened, honestly" field is the one that decides whether the reply works. If it was your mistake, the reply says so, and that single admission takes most of the heat out. If it wasn't, the reply explains without turning it back on the customer, which is harder to write and exactly what Claude is asked to do. Don't leave the field vague. "Not sure" produces a hedged reply, and hedged replies make angry people angrier.

The offer has to be something you'll do

Fill in what you can and can't offer before you run the prompt, not after. A reply that promises a refund the finance team later blocks is worse than one that says no clearly. The prompt also asks for a date rather than "soon", so pick a date you can meet with room to spare.

The internal note at the end is easy to ignore. Read it anyway. The third complaint about the same thing is usually a process problem wearing a customer's name.

How to use this prompt

  1. [01] Copy

    Copy the prompt

    Use the copy button above. The full text is included, nothing is cut off.

  2. [02] Fill in

    Replace the yellow parts

    Everything highlighted in yellow is a placeholder. Swap it for your own topic, audience or data.

  3. [03] Vote

    Run it in Claude and vote

    If the result helped, press the heart. Votes decide which prompts make the weekly top 10.

More like this

All support prompts
Text output

Subject lines your new checkout question about mobile carts one page checkouts The email Hi Dana, I saw the one page checkout you launched last week. The address autocomplete is really nice. I am curious whether it changed...

A cold email that sounds human

Short, specific outreach that reads like you wrote it in five minutes. Comes with three subject lines and a follow-up that adds something new.

Text output

Translation (English to French, informal and friendly) Votre commande est en route ! On a bien reçu votre paiement, et vos affaires sont déjà en train d'être emballées. Comptez 2 à 4 jours ouvrés pour la livraison. Un petit...

Translate it and keep the tone

A translation that reads like it was written in the target language, with notes on the places where a literal version would have sounded off.

Learn the technique

All articles
2 min read

How the weekly ranking works

One vote per prompt, a fresh count every Monday, and a simple tie-break. Everything about how prompts reach the top three, in plain words.

2 min read

How to use XML tags in Claude prompts

Wrapping parts of your prompt in simple tags is one of the easiest ways to get more reliable answers from Claude. A practical guide with examples.