Write an apology email to a customer

Apology email template

**Subject:** Sorry about {the specific problem, e.g. the wrong size in order #4471}

Hi {first name},

I'm sorry we {the specific mistake, in plain words}. That was our mistake.

{What happened, in one sentence. No excuses.} I know this meant {the real impact on them}.

{What we've done already, e.g. refunded, reshipped, fixed.} {What you get, e.g. a credit or a code, only if you're offering one.}

{What we're changing so this doesn't happen again.}

If you have any questions, reply to this email or call me on {direct number}.

Best,
{Your name}
{Role, Company}

Apology email to customer examples

How to write an apology email to a customer

• Say sorry for the specific thing

  “I'm sorry we sent you the wrong size” beats “we apologize for any inconvenience”. Naming the mistake shows you understand what happened.

• Own it, without the excuses

  One plain sentence on what happened is enough. Don't blame a new hire, a courier or the customer. “That was our mistake” builds more trust than a paragraph of context.

• Acknowledge the impact on them

  They couldn't take bookings, or didn't get the size they ordered. One sentence shows you see it from their side.

• Lead with what you've done

  A refund already sent or a replacement already shipped matters more than any wording. Only offer a credit you've actually approved, and say exactly what it is.

• Say how it won't happen again

  A real change, like a check on duplicate charges, turns an apology into a fix. If you don't know yet, say you're looking into it. Don't promise what you haven't decided.

• Keep it short and signed by a person

  Apologize once, near the top, then get to the facts. End with a named person and a direct way to reach them.

You are a customer support lead who writes sincere, specific apology emails. Turn the notes below into an apology email to the customer or client.

Rules:
- Use only the facts in the notes. Never invent a cause, a timeline, a fix, a process change, a refund, a discount, a credit or a promise. Where a needed fact is missing, use a {placeholder}, e.g. {first name}, {order number}.
- Subject line: the specific problem in plain words, e.g. "Sorry about the wrong size in order #4471" or "We charged you twice for your September renewal". Never just "Our apologies" or "Important update". No dashes.
- Open with "Hi {first name}," (use the name if given).
- First sentence: "I'm sorry" or "We're sorry" plus the specific mistake, owned plainly ("We're sorry we sent you the wrong size", not "mistakes were made"). Use "I" if the notes are written by one person about their own work. If the notes say whose fault it was, you may say "That was our mistake." No "we apologize for any inconvenience", no "we value your business", no "unfortunately".
- Then what happened, in one plain sentence, only if the notes give a cause. No excuses, and no blaming staff, vendors or the customer by name.
- Then one sentence acknowledging the impact on them. Keep it to what obviously follows from the notes; don't add meetings, plans or feelings that aren't mentioned.
- Then what you've done and what they get, exactly as given. A refund, replacement, fix, credit or new date already counts, so don't add a placeholder next to it. Only if the notes give no action or remedy at all, write {what we're doing to put it right}.
- Always include how you'll stop it happening again, as its own short paragraph. If the notes give a prevention step, write it in a plain sentence. If they don't, write exactly {what we're changing so this doesn't happen again}, with the curly braces, and nothing else in that paragraph. A cause ("the warehouse picked the wrong bin") is not a prevention step; never make one up.
- Speak to the one reader. Don't mention how many other customers were affected unless the notes ask you to.
- For anything involving personal data or security: state only the facts given, including what data was and wasn't involved if the notes say so. Never speculate about causes, never say data is safe unless stated, and make no legal promises.
- Close with a direct way to reach a person (reply to this email, or a phone number if given), then a blank line and a short sign-off ("Best," or "Thanks,") with {Your name} on the next line. Apologize once, in the opening; don't repeat "sorry" in every paragraph.
- Warm, plain and direct. No em dashes; write number ranges as "5 to 10". 3–5 short paragraphs separated by blank lines. Under 170 words.

Return "Subject: …" on the first line, a blank line, then the email. No other text.

Add your name, role, direct phone number and any standard remedy you're allowed to offer to the snippet once, and every apology comes out signed and ready to check.

Use it where you work

• In Zendesk, Intercom or Help Scout

  Type what went wrong and what you're doing about it into the reply, select it and run the snippet. The apology replaces your notes.

• In Apple Mail or Outlook

  Write the honest version to a client, “missed Friday, my fault, Wednesday 10am, no charge”, and turn it into an email you're comfortable sending.

• For an incident affecting many customers

  Draft the outage notes in Notes or Google Docs, run the snippet, and paste the result into your email tool.

• 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.

• 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.

• Thank you for your patience

  “Thank you for your patience” is polite, but on its own it says nothing. Paste a reply that leans on stock phrases and get one that thanks the customer for something real, says what happened and what happens next.