Apology Emails to Customers: 12 Templates

Almost every apology email you've received opened the same way: We sincerely apologize for any inconvenience this may have caused. It's the default because it feels safe. It's also the weakest sentence you could lead with.

Psychologists Roy Lewicki, Beth Polin and Robert Lount studied what actually makes apologies land and found six components that do the work. They also ranked them. First was the acknowledgement of responsibility. Second was the offer of repair. The expression of regret — the part everyone remembers to include — came third, tied with two others.

Saying sorry is the easiest component to write and the one carrying the least weight.

So the fix is small and it's mostly about order. Name what you did before you say how you feel about it.

The sentence that does the most work

Two openings for the same billing error.

We sincerely apologize for any inconvenience this may have caused.

We charged your card twice on March 4. That was our error, in our billing system, and you shouldn't have had to notice it.

The second says what happened, whose fault it was, and — by implication — that the customer was right to be annoyed, which removes their need to argue.

The first hedges twice. Any suggests you're not sure there was an inconvenience; may have suggests you're not sure it happened. You've apologized in a way that leaves room for having done nothing wrong, and customers hear that.

Three questions before you write

One person or a list? A single customer wants their specific problem named. A thousand customers want scope, cause and timeline. The mass version sent to one person reads as canned; the personal version sent to a list is impossible.

Whose fault was it, really? Not rhetorically — actually. If a carrier lost the package, you didn't lose the package. There's still an email to write, but it isn't an apology in the same sense.

Does this need something attached? Decide before you draft. An apology ending with "let me know if there's anything I can do" is asking the customer to do your job.

Harvard Business Review's guidance from Schweitzer, Brooks and Galinsky adds a scaling rule worth holding onto: the more central the failure is to what you promise, and the more people it affects, the more the apology has to be right. A late shipment from a shipping company is a core failure. From a software company it's an annoyance.

When you shouldn't apologize

Every guide on this subject assumes the answer is always yes. It isn't.

When you didn't do anything wrong. A customer who misread the pricing page and is angry about the charge doesn't need an apology, because you haven't wronged them. Apologizing anyway teaches them the pricing page was misleading — which you've now conceded in writing — and it teaches you nothing, because you'll go looking for a problem that isn't there. Be warm, be helpful, fix it if you want to. Don't say sorry for a thing you didn't do.

When the apology is standing in for the fix. If the outage isn't resolved, an apology email is a way of feeling like you've responded without having responded. Customers can tell. Send the status update instead and apologize when you can also say it's over.

When you've already apologized for this. The second apology for the same unfixed problem reads as worse than silence, because it demonstrates that apologizing is the whole of your response.

When it's a legal matter. I'm not a lawyer and I'm not going to pretend that the wording of an apology carries the same weight in every jurisdiction and industry. If you're in healthcare, finance, insurance, or anything with a regulator, ask someone who does this for a living before you put fault in writing. For ordinary commercial mistakes, this doesn't apply.

One customer, your mistake

The six most common versions. All of them name the error before they name the feeling.

1. Billing error

Subject: We charged you twice — refund on the way

Hi [Name],

We charged your card twice on [date], for [amount]. That was an error on our side, in [system/process], and you shouldn't have had to catch it.

I've issued a refund for the duplicate charge. It should land in [timeframe] depending on your bank. If it hasn't by [date], reply here and I'll chase it.

Sorry for the trouble this caused.

[Your name]

2. Late shipment

Subject: Your order is late — here's where it is

Hi [Name],

Your order [number] should have arrived on [date]. It hasn't, because [specific reason — it sat in our warehouse for three days, we oversold the item, we shipped it to the wrong facility].

It's now [current status] and should reach you by [date]. Tracking is here: [link].

I'm sorry — you planned around a date we gave you and we didn't hold up our end.

[Your name]

3. A bad experience with your team

Subject: About your conversation with our team

Hi [Name],

I read the exchange you had with [name/our team] on [date]. You were told [what they were told], and that was wrong — both the information and the way it was delivered.

Here's what's actually true: [correct information]. And here's what I'm doing about the rest: [specific action].

I'm sorry. You shouldn't have had to have that conversation.

[Your name]

4. Wrong item

Subject: We sent the wrong item — fixing it now

Hi [Name],

You ordered [correct item] and we sent [wrong item]. That's a picking error on our side.

The right one ships today and should arrive [date]. Keep the wrong one or send it back with the label attached — whichever is less trouble for you.

Sorry for the extra step.

[Your name]

5. Unexpected renewal charge

Subject: Your renewal charge — refunding it

Hi [Name],

You were charged [amount] on [date] for your annual renewal. Our reminder email went out [late / not at all / to an old address], so this arrived without warning. That's on us.

I've cancelled the renewal and refunded the charge. If you'd rather keep the subscription, tell me and I'll reinstate it at the same rate.

Sorry for the surprise.

[Your name]

This one has a mirror image: if you're the customer trying to undo a renewal you didn't expect, the cancellation email works differently from the apology — it names a decision rather than a regret.

6. Missed deadline on work you owed

Subject: [Project] — I missed the date

Hi [Name],

I owed you [deliverable] on [date] and I didn't deliver it. The reason is [honest reason], which is an explanation and not an excuse.

Here's where it stands: [current state]. You'll have it by [new date], and I'm not going to move that date again.

I know this pushed your own timeline. I'm sorry.

[Your name]

If you're adapting these to your own situation and voice, the AI response generator will rework the tone and keep the length down.

Many customers at once

Different rules. You can't name one person's specific loss, so the currency is scope, cause and timeline. And you must not claim more certainty than you have — the mass apology that turns out to be wrong is a second incident.

7. Outage or downtime

Subject: [Product] was down for [duration] today

Hi [Name],

[Product] was unavailable from [time] to [time] today. During that window, [what customers couldn't do].

The cause was [plain-language cause]. It's resolved, and [specific prevention step] is in progress so it doesn't recur in the same way.

If this cost you something concrete, reply and tell me — we'll sort it individually.

[Your name], [role]

8. Email sent in error

Subject: Please ignore our last email

Hi [Name],

You received an email from us [today/yesterday] about [subject]. It was sent by mistake and [doesn't apply to you / contained the wrong figures / went to the wrong list].

Nothing you need to do. Nothing has changed with your account. The correct information is [correct information].

Sorry for the confusion.

[Your name]

9. Data or security incident

This is the one to run past someone before sending. Disclosure obligations vary by jurisdiction and the wording is not a marketing decision.

Subject: Important: a security incident affecting your account

Hi [Name],

On [date] we identified [plain description]. Based on what we know now, [what was and wasn't affected].

What we've done: [containment steps]. What we're asking you to do: [specific actions, ordered by priority].

We'll update you by [date] whether or not there's more to report. Questions go to [dedicated contact].

[Name], [senior role]

When it isn't your fault

The trap here is that "sorry" is doing two different jobs in English — regret about an event, and admission of fault. These emails need the first without the second. The difference lives in what follows the word: I'm sorry this happened is regret. I'm sorry we did this is fault. You can be genuinely sorry a customer's week was ruined without agreeing that you ruined it.

10. Carrier delay

Subject: Your order is delayed in transit

Hi [Name],

Your order left us on [date] and is currently held at [carrier]'s [location] facility because of [reason]. Their updated estimate is [date].

I've opened a trace with them and I'll tell you what comes back. If it isn't moving by [date], I'll send a replacement rather than keep you waiting on it.

Sorry you're stuck in the middle of this.

[Your name]

11. The customer made the mistake

Subject: About your [order/account]

Hi [Name],

I've looked into this. What happened is [neutral description of what occurred, without assigning blame in either direction].

Here's what I can do: [the fix, if you're offering one]. It'll take [timeframe].

I can see why this was frustrating, and I'd rather sort it than argue about how it happened.

[Your name]

12. Weather, strikes, and things nobody controls

Subject: [Service] disruption — [cause]

Hi [Name],

[Event] is affecting [specific service] in [area]. Right now that means [concrete impact on them].

We expect normal service by [date], though that depends on [dependency] and I'll tell you if it slips.

I know this doesn't help your [deadline/plans]. If there's a workaround on our side that would, tell me and I'll look.

[Your name]

Should you offer something?

Yes when the customer lost money or time that you can put a number on. A duplicate charge gets refunded. A missed deadline that cost them a day gets a credit.

No when nothing measurable was lost. And this is the part people get wrong: an unprompted discount attached to a small mistake tells the customer the mistake was bigger than they thought. You've now made them wonder what else went wrong. A $5 credit for a two-hour delay reads as either an insult or an admission, depending on the customer, and it's rarely the thing they wanted.

There's a second cost, and it's slower. Compensating every complaint teaches the loudest customers what complaining is worth. Support teams who do this find, a year later, that they've built a queue of people who escalate as a first move rather than a last one.

This is where the research is more useful than it first looks. The offer of repair ranked second of the six components — ahead of regret, ahead of explanation. But an offer of repair is not the same thing as compensation. Telling a customer what you've fixed so it doesn't happen again is repair. A discount code is a payment, and payments only make sense when there's a loss to cover.

The rule I'd use: compensate the loss, not the feeling. If you can't name the loss in a number, fix the problem, say what you fixed, and skip the credit.

When the complaint isn't right

Sometimes you'll read a complaint and know that what the customer describes didn't happen, or happened because of something they did. The advice everywhere is to apologize anyway, lead with empathy, and move on. I think that's wrong often enough to be worth separating out.

Three situations, three different emails.

They're factually mistaken. They were charged the amount on the pricing page, or the feature works the way the documentation says. Don't apologize — you'd be conceding a defect that doesn't exist, in writing, to someone who may forward it. Instead: state what happened neutrally, show the evidence without making it a rebuttal, and offer the fix if you're willing to give one anyway. Something like: "Looking at your account, the charge on March 4 was for the annual plan selected at signup. I can see how the timing was confusing, and I'm happy to switch you to monthly from here if that works better." You've corrected the record and left them somewhere to go.

The complaint is a demand. "I want a full refund or I'm posting about this." The refund question and the complaint question are now separate, and you should answer them separately. Address the actual problem first. Then answer the demand plainly — yes or no, with the reason, once. Negotiating under a threat sets the price for the next one.

It's abuse rather than a complaint. Personal insults, threats, sustained hostility across several messages. There's no email template for this because the answer isn't a better email. It's one reply stating what you'll do and what you won't, and then escalation to whoever owns that decision. Apologizing here doesn't de-escalate; it signals that the approach is working.

What links all three: an apology is a claim about what happened. If your claim isn't true, don't make it — no matter how much easier it would be.

What makes it worse

• "We're sorry you feel that way." This is not an apology. It relocates the problem into the customer's head, and every customer knows it.
• Explaining at length. A one-clause reason is context. Three sentences of reason is a defense, and a defense invites rebuttal.
• Passive voice. "An error occurred in processing" has no subject. Somebody processed it.
• Apologizing to the wrong depth. A grave apology for a small thing is unsettling. A breezy one for a serious thing is worse.
• Sending it from a no-reply address. You've asked for forgiveness and closed the channel for the answer.

Before you send it

Find the first sentence and check whether it names what happened or names your feelings about it. If it's the second, swap them.

That single edit does more than any other change you could make to these emails, and it takes about ten seconds.