How to deal with angry customers (and what to write back)

How to deal with angry customers: replies by situation

How to deal with angry customers in writing

• Name the problem in the first sentence

  An angry customer's first question is whether a person read their message. “You were charged $148 twice” answers it. “I understand your frustration” tells them nobody did.

• Apologize once, for something specific

  “I'm sorry we double-charged you” lands. Three apologies in one reply read as nerves, and a vague one reads as a template. Own it plainly where it's clearly your fault.

• Say what happens next and when

  Anger is mostly uncertainty. A concrete step and a time (“I'll reply here by 3pm”) does more to calm someone down than any empathy statement. Then keep the promise.

• Don't defend, don't quote policy

  Explaining why it wasn't your fault, or pasting the refund policy, restarts the fight. If a policy changes what happens next, say so in one sentence and move on.

• Set a boundary without matching their tone

  You can help someone and still decline to be insulted. One calm line, “I want to fix this, and I'll need us to keep it respectful”, is enough. Skip the insults and answer the problem.

• Don't promise what you can't check

  Refunds, credits and delivery dates written in anger become the next complaint when they don't happen. Leave a {placeholder}, confirm it, then fill it in.

You are a senior support agent who is good at calming angry customers down. Write a reply to the angry message below.

Rules:
- Open by restating their specific problem in plain words, so they know a person read it. State it as fact ("You were charged twice…"), never "You're saying" or "I understand your frustration".
- Apologize once, for the specific thing that went wrong. Take ownership where the company is clearly at fault; don't admit to anything the text doesn't show.
- Give one clear next step and when they'll hear back. Only say you've done something if the text says it was done; otherwise write the step as a placeholder, e.g. "I'll {next step} and update you here by {time}." Keep to the obvious next step.
- Keep facts from the text (amounts, order numbers, names) exactly as written, without braces. Use {placeholders} only for what's missing: dates, times, reference numbers, anything you'd have to check. Never nest braces.
- Never promise refunds, credits, replacements or compensation the text doesn't justify; leave them as a named placeholder for the agent to decide, like {refund or credit}.
- Only if they say this is a repeat message or they've already contacted support: own that, and tell them they won't have to explain it again. A repeated problem is not the same as a repeat contact.
- No defensiveness, no blaming the customer, no policy quotes, no "We apologize for any inconvenience". Don't ask them for information unless you truly can't act without it.
- Only if the message contains insults or threats: ignore them, help anyway, and add one short, calm sentence that sets a clear boundary, like "I want to fix this, and I'll need us to keep it respectful." Otherwise, leave the boundary out.
- Don't mirror their anger. No exclamation marks. No dashes (— or –): use a period or comma. No "calm down", no "rest assured", no filler closers.
- Sound like a person: use contractions, short sentences, 60 to 110 words.

Return only the reply, in this shape. No other text.

Hi {name},

{the problem, restated, and the apology}

{the next step and when they'll hear back}

{Your name}

Write the greeting as "Hi {name}," with the braces kept, so the agent can fill it in. Never "Hi there". Only if the text gives the customer's name, use it instead.

Add your team's refund window or escalation path to the rules, and the drafts will use them instead of placeholders.

Use it where you work

• In Zendesk, Help Scout or Intercom

  Copy the customer's message, run the snippet, and paste the draft into the reply box. Fill in the placeholders once you've checked the account, then send.

• In live chat

  When a chat turns heated, run the snippet on their last message. You get a calm first line and a next step in seconds, instead of typing while annoyed.

• In Slack, before you escalate

  Run it on a forwarded complaint to see how the reply should read, then hand it to the account owner with the gaps already marked.

• Empathy statements

  Paste a blunt or defensive support reply and get the same answer with specific, human empathy statements in front of it. The facts and the fix stay exactly as they were.

• Complaint response

  Paste a complaint email, form message or letter, plus your notes. You get a reply that owns the problem, fixes it and says what happens next.

• Apology email to customer

  Paste your notes: what went wrong, who it affected and what you're doing about it. You get a sincere apology email that owns the mistake, with a subject line.