A good apology email does three things and stops: says what happened, says sorry without conditions, says what happens next. Most bad ones fail by adding a fourth thing, usually a defence.
Nine templates below, covering the situations that actually generate apology emails, plus the question most guides avoid: when to attach compensation, and when attaching it makes you look worse. For replies to complaints that have already arrived, use the complaint response library instead.
The anatomy
| Element | Rule |
|---|---|
| Subject line | Say what it is about. "About your appointment on Tuesday" beats "An update from us". Never bury an apology behind a neutral subject. |
| First sentence | The apology or the fact. Not a greeting paragraph, not context. |
| The apology itself | Once, unconditional, no "if" and no "any". |
| Cause | One sentence, plain language, no architecture and no blame. |
| Remedy | Specific, with a date. Already done beats offered. |
| Next step | Who does what, by when, and what the customer needs to do, which is ideally nothing. |
| Length | Under 150 words unless the incident genuinely warrants more. |
The three phrases to delete
"We apologise for any inconvenience caused." The "any" makes it conditional and the passive voice removes the actor. It is the single most recognisable non-apology in business writing. Replace with the specific inconvenience: "I'm sorry you lost a morning waiting for us."
"I'm sorry you feel that way." This apologises for their reaction, not your conduct. It reads as a brush-off because it is one.
"Unfortunately..." Almost always introduces a defence. Cut the word and see whether the sentence still needs to be there.
Sorry, or sorry we got it wrong?
Two different sentences doing two different jobs, and mixing them up is what produces hedged, mealy-mouthed apology emails.
- •"I'm sorry this happened to you." Describes their experience. Always available. Costs nothing, admits nothing.
- •"I'm sorry we got this wrong." Describes your conduct. Use it when it is true, and when it is true, use it plainly. Hedging a genuine fault is more damaging than the fault.
Only in matters touching injury, property damage, insurance, regulated services or an active dispute does wording need legal care. For everything else, teams hedge far beyond the actual risk, and the hedging is what customers read as insincerity. When the customer is already angry rather than merely owed an apology, de-escalation comes first.
The nine templates
1. Service delay
Subject: Your order [number] is running late
Hi [Name],
>
Your order was due [date] and it has not shipped. I'm sorry - you planned around that date and we moved it without telling you.
>
The hold-up is [plain cause]. It now ships [date] and reaches you by [date].
>
I've refunded the shipping without you needing to ask. If the new date does not work, reply and I'll cancel and refund in full today.
>
[Name]
Compensation: yes, small and automatic. A delay costs the customer planning, and refunding the shipping acknowledges that without being a negotiation.
2. Service outage
Subject: [Service] was down on [date] - what happened
Hi [Name],
>
[Service] was unavailable between [time] and [time] on [date]. If you were trying to [specific thing people use it for] during that window, it would not have worked. I'm sorry.
>
The cause was [plain-language cause, one sentence]. It is fixed, and [specific change] is in place so this particular failure cannot repeat.
>
[If applicable: your account has been credited [amount] for the affected period, applied automatically.]
>
Status is always at [link] if you want to check in future.
>
[Name]
Compensation: yes if the outage breached a stated commitment or the customer pays for availability. Apply it automatically rather than on request. Making people claim a credit for your outage is a second insult.
3. Wrong information given
Subject: Correcting what we told you on [date]
Hi [Name],
>
On [date] we told you [wrong information]. That was incorrect, and I'm sorry - you may have made decisions based on it.
>
The correct position is [right information].
>
[If they acted on it: here is what I'm doing to put you back where you should have been: specific action.] [If they have not yet: nothing has gone wrong, but I wanted you to know before it did.]
>
If the wrong information cost you anything, tell me what and I'll see what I can do.
>
[Name]
Compensation: depends entirely on whether they acted on it. Ask rather than assume. Sending money to someone who lost nothing is odd; ignoring someone who booked a flight on your bad information is worse.
4. Missed appointment
Subject: We missed your appointment this morning
Hi [Name],
>
Your appointment was [time] on [date] and nobody arrived. I'm sorry. I know that usually means a wasted morning, sometimes a day off work.
>
The reason was [honest, brief cause]. That is an explanation, not an excuse.
>
I can offer [next available slot] or [alternative]. Whichever you pick, [remedy: fee waived / discount / priority booking] applies, and I'll confirm it in writing before the day.
>
[Name]
Compensation: yes, and it should be meaningful. A missed appointment costs the customer time that cannot be returned, which is the one thing you genuinely cannot replace.
5. Billing error
Subject: We overcharged you - refunded
Hi [Name],
>
You were charged [wrong amount] on [date]. The correct amount is [right amount]. The difference, [amount], has been refunded and should reach your [card / account] within [number] working days.
>
The cause was [brief cause]. It is corrected on your account and will not repeat.
>
I've checked your previous [period] as well, and [no other charge is affected / here is what else I found].
>
[Name]
Compensation: the refund is the remedy, not compensation. Adding a credit on top of returning money you should not have taken can read as buying silence. Add something only if the error caused a knock-on cost, like a failed payment elsewhere or a bank charge, in which case cover that specifically.
6. Damaged order
Subject: Replacement on its way for order [number]
Hi [Name],
>
Thank you for the photos. That is not the state anything should arrive in and I'm sorry.
>
A replacement is dispatched today, arriving [date]. Keep the damaged one until it lands, then [disposal / return instructions]. You will not be charged twice at any point.
>
I've sent the photos to our packing team, because this type of damage usually points to how it was boxed rather than how it was carried.
>
[Name]
Compensation: the replacement is the remedy. Add more only if the damage caused a missed occasion, the item was a gift, or this is the second time.
7. Employee mistake
Subject: About your visit on [date]
Hi [Name],
>
Thank you for telling me what happened when you [visited / called] on [date]. What you described is not how we want anyone to be treated, and I'm sorry it was your experience of us.
>
I'm dealing with it directly. Because it involves a member of staff I won't be sharing that side of it with you, which I hope you understand.
>
What changes for you: [specific action]. I'd also like to [remedy], if you'll let me.
>
[Name]
Compensation: usually yes, modest, and framed as an invitation rather than a payment. Never discuss the employee's discipline with the customer, in either direction.
8. The same problem again
Subject: This shouldn't have happened a third time
Hi [Name],
>
[Issue] has now affected you on [date], [date] and [date]. Apologising again would be worth very little, so here is what is actually different.
>
[Named person] now owns this for your account. [Specific structural change] is in place from [date]. I will check in with you on [date] whether or not it recurs.
>
If it happens again, [concrete consequence: refund, release from contract, exit without penalty].
>
[Name]
Compensation: a discount alone is the wrong answer here and often makes things worse, because it reads as being paid to tolerate the problem. Pair any credit with a named owner and a structural change, or skip the credit.
9. Major inconvenience
Subject: What happened to your [booking / order / account], and what we're doing
Hi [Name],
>
[What happened, specifically, in one or two sentences with no softening.] I'm sorry. This was a significant failure and it affected [specific consequence to them].
>
What we have done already: [action, completed].
What happens next: [action, with owner and date].
What you need to do: [ideally, nothing].
>
[Remedy, specific and proportionate.] If that is not adequate, I would rather hear it from you than not. Reply to this message and it reaches me directly.
>
[Name]
Compensation: yes, and err on the generous side. In a serious failure the cost of over-compensating is smaller than the cost of appearing to haggle.
When compensation helps, and when it does not
Teams tend to treat compensation as a dial between stingy and generous. It is better understood as a question about what the customer lost.
Offer it when:
- •The customer lost something real and unrecoverable: time, money, an occasion, a deadline.
- •You breached something you stated: a delivery date, an availability commitment, a booked slot.
- •It is a repeat failure. Here it is close to mandatory, but never on its own.
- •The remedy itself takes a long time and they are inconvenienced while waiting.
Do not offer it when:
- •You can simply fix the problem quickly and nothing was lost. Reflexive compensation on first contact suggests you expect the fix to be inadequate.
- •You are returning money you should not have taken. That is a correction, not a gesture.
- •The customer caused the problem and you are helping anyway. Help generously; do not pay as well.
- •It would be the fourth gesture to the same customer and the underlying issue has not changed. At that point money is substituting for a fix, and both of you know it.
- •It is being offered in exchange for a review being removed or withheld. Never. Responding to negative feedback explains why.
How much is less important than how fast and whether they had to ask. A small automatic credit usually lands better than a larger one extracted over three emails. Set your own ladder before you need it: what any agent can offer unprompted, what needs a manager, and what is never offered.
Sending the apology before the complaint
The strongest apologies are the ones that arrive first. If your systems know an order has missed its date, a slot was not attended, or a service was down for ninety minutes, the customer should hear it from you before they write to you.
This changes the entire conversation. An apology you send is an act of care. An apology you send after being asked twice is damage control, and the customer can tell the difference immediately.
Three things make proactive apologies practical: knowing which failures are detectable, having the wording ready so nobody has to write it under pressure, and publishing the standing answers to the questions a failure generates, so the apology email does not have to carry everything and the customer can check status without writing again.
Frequently asked questions
How do you apologise professionally in an email?
Say what happened, apologise once without conditions, give the cause in one plain sentence, state the remedy with a date, and say what happens next. Put the apology near the top, not after three sentences of context.
Should I say "sorry for the inconvenience"?
Not in that form. "Any inconvenience" is conditional and the passive construction hides who did it. Name the actual inconvenience: "I'm sorry you lost a morning waiting for us" does the same job and sounds like a person.
Should an apology email include compensation?
When the customer lost something real, when you broke a stated commitment, or when it is a repeat failure. Not when you can simply fix the issue, and not when you are returning money you should not have charged, which is a correction rather than a gesture.
Who should send an apology email?
Whoever can actually do something about it, signed with a name rather than a team alias. For serious failures, someone senior enough that the customer can tell the escalation already happened without them asking.
How long should an apology email be?
Under 150 words for most situations. Length reads as defensiveness. The exception is a serious failure where the customer reasonably wants to know what happened in detail.
Is it bad to apologise too much?
Yes, in two ways. Repeating the apology within one message dilutes it, and apologising reflexively for things that are not your fault trains customers to expect a gesture every time. One clear apology plus one clear action beats four sorries.
Generate your FAQ page
Paste your product description and get a complete FAQ page - free, no sign-up.
Try Answrii free →