How to Write an Apology Email: 15 Templates + Examples

Quick answer: Start by taking responsibility in the first sentence — research finds this is the single most important part of an apology. Then say exactly what you will do to fix it. Add regret and a brief explanation, keep it under 150 words, and send it fast. Do not ask to be forgiven.

Most apology email guides give you templates that break their own rules. This one starts with the evidence and builds the templates from it.

What Makes an Apology Actually Work?

There is real research on this, and it is more specific than most advice suggests.

Roy Lewicki, Beth Polin and Robert Lount tested six components of an apology across two studies with more than 750 participants, published in Negotiation and Conflict Management Research in 2016. They found that apologies containing all six components were rated most effective — but the components are not equally important.

Here is the ranking:

Rank	Component	What it sounds like
1	Acknowledgment of responsibility	“This was our mistake.”
2	Offer of repair	“Here is what we are doing to fix it.”
3	Expression of regret	“I’m sorry.”
3	Explanation of what went wrong	“The cause was X.”
3	Declaration of repentance	“We’ve changed the process.”
6	Request for forgiveness	“Please forgive us.”

Lewicki’s summary of the findings was direct: the most important component is acknowledging responsibility — say it is your fault, that you made a mistake. The second most important was the offer of repair, because it commits you to action rather than just words.

Elements three, four and five were essentially tied. And the least effective component was asking for forgiveness.

Three things follow from this, and they contradict most template libraries:

Responsibility goes first, not after pleasantries. Most templates open with “I hope you’re doing well, it’s [name] here, and I’m writing to apologise for…” That buries the highest-value element behind small talk.

“Sorry” is not the most important word in the email. It matters — it is tied for third — but “this was our mistake” and “here is what we are doing” both outrank it. An email full of sorry with no repair offer is a weak apology.

Do not ask to be forgiven. It ranks last, it puts a burden on the person you wronged, and it makes the email about your relief rather than their problem.

One note on the evidence: reports of this study vary slightly on whether “explanation” ranks second or is tied for third. The primary summary from Ohio State puts offer of repair second, with explanation tied for third. Either way, responsibility is first and forgiveness is last.

What Is the Best Apology Email Structure?

Built directly from the ranking above.

1. Name what happened and own it — first sentence.

Your order arrived four days late. That was our error.

2. Say what you are doing about it — second.

We’ve refunded your shipping and your replacement ships today.

3. Add the regret and the reason — briefly.

I’m sorry for the disruption. A stock sync failure meant your item showed as available when it wasn’t.

4. Say what changed, only if something actually did.

We’ve added a check that flags mismatches before an order confirms.

5. Close with a way to reach you. Not a request.

If anything else is wrong, reply here and it comes straight to me.

That’s the whole thing. Five sentences, roughly 90 words, and it contains the two highest-ranked components in the first two lines.

How to Start an Apology Email

Start with the mistake and your responsibility for it — in the first sentence, before any greeting pleasantries.

The greeting itself is fine. “Hi Sarah,” then straight into it. What you skip is the warm-up.

Weak opening	Why it fails	Strong opening
“I hope this email finds you well.”	Wastes the highest-value position	“Your invoice was wrong. That’s my mistake.”
“I wanted to reach out regarding a recent issue.”	Vague, delays the point	“We charged you twice for your March order.”
“Thank you for your patience.”	Thanks them before acknowledging anything	“You waited nine days for a reply. That’s not acceptable.”
“Unfortunately, an error occurred.”	Passive voice hides who did it	“I sent you the wrong file.”

Three openings that work in almost any situation:

1. State the fact, then own it. “The report I sent you had the Q3 figures in the Q2 column. That was my error.”
2. Name the impact first. “You spent an hour on a call that I should have cancelled.”
3. Be direct when it’s serious. “Our service was down for six hours yesterday. Here’s what happened and what we’re doing.”

The one thing never to do at the start: open with “I’m sorry if…” Conditional apologies are covered below, and they are the fastest way to make an apology worse than sending nothing.

How to End an Apology Email

End by giving them a direct way to reach you, then stop. No request for forgiveness, no reassurance loops, no thanking them for understanding they haven’t offered yet.

Weak ending	Why it fails
“I hope you can forgive us.”	Ranked least effective; makes it about you
“Thank you for your understanding.”	Assumes understanding you haven’t earned yet
“We hope you’ll continue to shop with us.”	Turns an apology into a retention pitch
“Again, I sincerely apologise for any inconvenience.”	Repeating “sorry” adds nothing
“Please don’t hesitate to reach out.”	Filler; say the actual channel

Endings that work:

• “If anything’s still wrong, reply here and it comes to me directly.”
• “I’m on [number] today if you’d rather talk it through.”
• “I’ll email you Friday to confirm it’s resolved.”
• “You don’t need to do anything — the refund is already processed.”

The best ending is often a commitment with a date. “I’ll confirm on Friday” is a promise you can be held to, which is more reassuring than any amount of sincere-sounding language.

What Should an Apology Email Subject Line Say?

Be plain. This is not a subject line to be clever with — the reader should know what it is before opening.

Situation	Subject line
Order problem	Your order — our mistake, and the fix
Late delivery	Your order was late. Refund processed.
Billing error	We double-charged you. Refunded today.
Missed deadline	The [project] deadline — my error
Wrong file or document	Corrected [document] attached — sorry for the error
Late reply	Sorry for the slow reply — answering now
Meeting mix-up	I missed our 2pm. My fault.
Service outage	Yesterday’s outage: what happened
To a client	About last week — and what we’re changing
Wrong recipient	Please disregard my last email

Two rules. Put the resolution in the subject line where you have one — “Refunded today” gets opened faster than “Our apologies.” And never use “Apology” alone; it tells the reader nothing about whether they need to act.

How Long Should an Apology Email Be?

Under 150 words for most situations. Roughly five to seven short sentences.

Situation	Target length
Small mistake (typo, wrong file, late reply)	40–80 words
Customer order or service problem	80–150 words
Apology to a client after a real failure	150–250 words
Company-wide incident or outage	250–400 words

Length signals something whether you mean it to or not. A 400-word apology for a typo looks like anxiety. A 40-word apology for losing a client’s data looks like indifference. Match the length to the size of the harm.

And the paradox: long apologies are usually longer because they contain explanation and self-justification, which rank low. Cutting an apology almost always strengthens it, because what gets cut is the part defending you.

What Should You Never Say in an Apology Email? 7 Phrases to Cut

These are the most common failure mode in business apologies, and every one of them shows up in published template libraries.

1. “I’m sorry if this caused any inconvenience.” The conditional “if” says you’re not sure any harm happened. It converts an apology into a hypothetical. → “I’m sorry this cost you two hours.”

2. “Mistakes were made.” Passive voice with no subject. Nobody did anything; mistakes simply occurred. → “I made a mistake.”

3. “We apologise for any inconvenience caused.” “Any” and “caused” both distance you from the act. It’s the most-used phrase in customer service and it reads as boilerplate. → “We’re sorry your delivery was three days late.”

4. “This was due to factors outside our control.” This is a defence wearing an apology’s clothes. It directly contradicts the highest-ranked component. If a supplier failed, that is still your supplier. → “Our supplier missed a shipment and we didn’t have a backup. That’s on us.”

5. “I’m sorry you feel that way.” Apologises for their emotion rather than your action. Widely read as an insult. → “You’re right to be annoyed. Here’s what went wrong.”

6. “As you know, our policy states…” Policy citations belong in a different email. Quoting terms during an apology reads as building a case. → Explain the fix, then handle policy separately if needed.

7. “I promise this will never happen again.” Often a promise you can’t keep, and one broken promise costs more than the original mistake. → “We’ve added a check that catches this specific problem.” Say what changed, not what you guarantee.

The test for all seven: could a lawyer have written this sentence to limit liability? If yes, rewrite it. Readers detect defensive language instantly, even when they can’t name what’s wrong.

15 Apology Email Templates You Can Copy

Every template below leads with responsibility, follows with repair, and contains no deflection or forgiveness request.

Customer and e-commerce

1. Wrong item shipped

Subject: Wrong item sent — correct one ships today

Hi [Name],

We sent you the wrong item. That’s our packing error, not anything to do with your order.

The correct [item] ships today on express delivery at no charge, and you’ll have tracking within a few hours. Keep or bin the wrong item — no need to return it.

I’m sorry for the hassle of unpacking something you didn’t order.

If it doesn’t arrive by [date], reply here and it comes straight to me.

[Name], [Role]

Why it works: responsibility in sentence one, repair in sentence two, and it removes a task from the customer rather than adding one.

2. Late delivery

Subject: Your order was late. Shipping refunded.

Hi [Name],

Your order arrived four days after the date we promised. We got that wrong.

I’ve refunded your shipping — it’ll be back on your card in 3–5 days, no action needed from you.

The cause was a stock count error on our side that let the order confirm before the item was actually available.

We’ve since added a check that stops an order confirming when the counts don’t match.

[Name], [Role]

3. Double charge or billing error

Subject: We double-charged you. Refunded today.

Hi [Name],

We charged you twice for order [number]. That was a payment processing error on our end.

The duplicate charge of [amount] was refunded this morning. Depending on your bank it should clear within 3–5 working days.

I’m sorry — being charged twice is unsettling even when it’s fixed quickly.

If it hasn’t cleared by [date], reply here and I’ll chase it with our processor directly.

[Name], [Role]

4. Damaged item

Subject: Your [item] arrived damaged — replacement on the way

Hi [Name],

Your [item] arrived damaged. Our packaging wasn’t up to the job.

A replacement ships today. You don’t need to return the damaged one or send photos.

We’ve switched to heavier packaging for this item, which should have happened before your order went out.

[Name], [Role]

5. Out of stock after ordering

Subject: Your order can’t ship — full refund or a swap

Hi [Name],

We’ve sold you something we don’t have. Our stock count was wrong and your order shouldn’t have been accepted.

Two options, whichever suits you: · Full refund, processed today · Swap for [alternative], which is in stock, plus [amount] credit for the trouble

Just reply with which you’d prefer. If I don’t hear from you by [date] I’ll process the refund, so you’re not left waiting on me.

[Name], [Role]

6. Service outage

Subject: Yesterday’s outage: what happened

Hi [Name],

[Product] was unavailable for 4 hours and 20 minutes yesterday, from 09:10 to 13:30 UTC. That was caused by a failed database migration we ran without an adequate rollback plan.

Everything is back and no customer data was lost.

What we’re changing: migrations now run in a staging environment first, and we’ve added an automatic rollback trigger.

If the outage cost you something concrete, reply and tell me — we’ll sort out credit case by case rather than making you ask twice.

[Name], [Role]

Why it works: exact numbers and duration, a named cause, no vague “technical difficulties,” and it invites specific claims rather than blanket reassurance.

Clients

7. Missed deadline

Subject: The [project] deadline — my error

Hi [Name],

I missed Friday’s deadline on [deliverable]. I underestimated the [specific part] and didn’t flag it early enough for you to plan around.

Where things stand: [specific component] is done and attached. The rest will be with you by Wednesday at 5pm, and I’ll send a progress note Tuesday so you’re not waiting in the dark.

The real failure was not telling you on Tuesday when I first knew it was tight. I’ve moved my check-in on this project to weekly so it doesn’t repeat.

Happy to talk it through — I’m free most of tomorrow.

[Name]

8. Poor quality work delivered

Subject: About last week’s [deliverable] — and what we’re changing

Hi [Name],

The [deliverable] we sent last week wasn’t good enough. You were right to push back, and the issues you raised were all fair.

We’re not charging you for it. I’ve reassigned it to [Name], who’s done similar work for [context], and you’ll have a revised version by [date].

What went wrong on our side: it went out without a second review because we were trying to hit the date. That was the wrong trade-off and it was my call.

I’d like 20 minutes this week to check the brief is right before we start again, rather than assume it was.

[Name], [Role]

Workplace

9. Made a mistake at work

Subject: The [report] figures — my mistake

Hi [Name],

The figures in the report I sent yesterday were wrong. I pulled Q2 data into the Q3 column.

Corrected version attached. The changed numbers are in rows 14 to 22, and the conclusion doesn’t change.

I’ve added a second-pass check on my own numbers before anything goes out.

[Name]

10. Apology to your boss

Subject: Yesterday’s client call — my responsibility

Hi [Name],

I handled yesterday’s call with [client] badly. I was underprepared on [topic] and it showed.

I’ve emailed them the answers I couldn’t give in the meeting and offered a follow-up call this week.

Going forward I’m blocking 30 minutes before every client call for prep, which I’d stopped doing.

Happy to talk through anything else you’d want handled differently.

[Name]

11. Missed a meeting

Subject: I missed our 2pm. My fault.

Hi [Name],

I missed our 2pm — I didn’t put it in my calendar after we agreed it verbally.

I’ve sent a new invite for Thursday at the same time. If that doesn’t work, pick anything from my calendar.

Sorry for the wasted twenty minutes.

[Name]

12. Late reply

Subject: Sorry for the slow reply — answering now

Hi [Name],

Your email sat unanswered for nine days. That’s too long and there’s no good reason for it.

Answering your actual question: [answer].

Anything else outstanding, tell me and I’ll turn it round today.

[Name]

13. Something you said

Subject: What I said in today’s meeting

Hi [Name],

What I said in today’s meeting about [topic] was dismissive, and I said it in front of the team. That wasn’t fair to you.

I’ve been thinking about why I reacted that way and it was about my own pressure on [thing], not about your work.

I’ll say so in tomorrow’s standup unless you’d rather I didn’t — your call, tell me either way.

[Name]

14. Wrong recipient

Subject: Please disregard my last email

Hi [Name],

I sent you an email that was meant for someone else. Please delete it.

Nothing is needed from you. I’ve changed how I handle recipient fields so it doesn’t happen again.

Sorry for the confusion.

[Name]

Important: if that email contained someone else’s personal data, deleting it may not be the end of your obligations. See the legal section below.

The one you should not send

15. Too serious for email

Subject: Can we talk today?

Hi [Name],

I need to talk to you about [thing] and I don’t want to do it over email.

Are you free at [time] today? If not, tell me when and I’ll make it work.

[Name]

Some apologies should not be emails. If the harm was personal, if the person is genuinely upset, or if the situation is complicated enough that tone will be misread, the email’s only job is to arrange the conversation. Sending a written apology in these cases can read as avoidance.

How to Write a Sincere Apology Email to a Client

Client apologies are different from customer apologies in one important way: the client has to justify keeping you to somebody else. Their boss, their board, their own client. Your apology needs to give them something to say.

Five things a client apology needs:

1. Own it without hedging. Clients have heard every version of “circumstances beyond our control.” One unhedged sentence buys more credibility than three paragraphs of context.

2. Name the real failure, not the surface one. Missing a deadline is the symptom. Not warning them early enough is usually the actual failure — and the one they care about, because it removed their ability to plan.

3. Make the repair concrete and costly to you. Not charging for the work, reassigning it to someone more senior, or absorbing a delay. A repair that costs you nothing does not read as a repair.

4. Say what changed in your process. Clients are deciding whether this recurs. A specific process change answers that; “we’ll do better” does not.

5. Offer a conversation, and mean it. Written apologies let people stay angry privately. Twenty minutes on a call usually resolves more than the email did.

What to leave out: how busy you were, how unusual this is, how much you value the relationship, and any mention of your other clients. All four read as excuses even when they’re true.

What Are the Best Templates for Apology Emails to Customers in E-Commerce?

E-commerce apologies have their own pattern, because the customer usually wants a resolution rather than an explanation.

The e-commerce rule: lead with the resolution, not the reason.

A customer whose order is late does not primarily want to know about your warehouse. They want to know whether they are getting their money or their product. Put that in the subject line and the first two sentences. The explanation can come third.

Templates 1 through 6 above cover the six scenarios that account for most e-commerce apologies: wrong item, late delivery, double charge, damaged goods, out of stock after ordering, and service outage.

Four e-commerce-specific rules:

Remove tasks, don’t add them. “No need to return it,” “no photos needed,” “no action required from you.” Every step you remove is worth more than a sentence of sympathy.

Give the refund before they ask. A refund offered is worth far more than a refund granted on request. Processing it first, then telling them, changes the whole tone.

Be specific about timing. “3 to 5 working days” beats “shortly.” Vague timelines generate a second complaint email.

Don’t bundle a discount code with the apology as the main remedy. Fix the actual problem first. A discount presented as the primary repair reads as buying them off, and it only works on customers who intended to order again anyway. Offer it after the fix, as a small extra, or not at all.

One thing to check before you send at scale: if you are apologising to a whole customer list, that email is marketing-adjacent and unsubscribe and sender requirements still apply. Send it from a real reply-to address that a human monitors, because a mass apology from a no-reply address generates more anger than the original problem.

How Do You Write an Apology Email for a Mistake?

For a straightforward, self-contained mistake — a typo, a wrong file, a bad number, a missed message — the whole thing is four sentences.

1. What was wrong. “The invoice I sent had the wrong total.”
2. That it was yours. “That was my error.”
3. The correction. “Corrected version attached — the total is [amount].”
4. The prevention, if real. “I’ve added a check before sending.”

Under 60 words. Do not explain how it happened unless the explanation genuinely helps them, and do not apologise twice.

The most common error on small mistakes is over-apologising. Four paragraphs about a typo draws more attention to it than the typo did, and it makes the recipient manage your discomfort. Fix it, name it, move on.

Does an Apology Email Have Legal Implications?

This section is educational and not legal advice. Requirements vary by jurisdiction and by the kind of data involved. Talk to your legal or compliance team about your specific situation.

Some apologies come with a statutory deadline, and most guides on this topic treat them as purely social.

The most common one: the misdirected email. Under GDPR, a personal data breach is defined in Article 4(12) as a security breach leading to accidental or unlawful destruction, loss, alteration, or unauthorised disclosure of or access to personal data. Accidental disclosure counts — there is no requirement of malicious intent. Sending someone else’s personal data to the wrong recipient can be a breach.

If it is, two obligations may apply:

Article	Obligation
Article 33	Notify your supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware — unless the breach is unlikely to risk individuals’ rights
Article 34	Notify the affected individuals directly when the breach is likely to result in a high risk to their rights and freedoms

Two points worth knowing. The 72 hours starts when you have reasonable certainty a breach occurred, not when your investigation finishes. And late notification is a violation in its own right — it can attract a fine independently of the underlying breach.

Not every incident qualifies. A single internal email to the wrong colleague containing nothing sensitive is generally low risk and needs internal documentation rather than notification. But you have to assess and record it, not just apologise and delete.

Other regimes have different clocks. HIPAA allows 60 days for breaches of health data. California’s CCPA/CPRA works to a 30-day consumer notification, with 15 days to the Attorney General where 500 or more residents are affected. Canada’s PIPEDA requires notice “as soon as feasible” where there is a real risk of significant harm.

What this means practically: if your apology email involves someone’s personal data going somewhere it shouldn’t, the apology is not the compliance step. Loop in whoever owns data protection at your organisation before you send, and keep a written record of when you became aware.

When Should You Not Send an Apology Email?

Four situations where email is the wrong channel:

When the person is genuinely upset. Email removes tone, and an upset reader supplies the harshest possible reading of every sentence.

When the harm was personal rather than procedural. Something you said, a trust broken, a relationship damaged. Email reads as avoidance.

When it’s complicated. If the apology needs three paragraphs of context, it needs a conversation. Use template 15 to arrange one.

When you don’t yet know what happened. An apology built on a guess often has to be corrected, and a corrected apology is worse than a slow one. Send a short holding note — “I’m looking into this and I’ll come back to you by [time]” — and then apologise properly.

What Are the Best AI Tools for Drafting Customer Apology Emails?

AI is genuinely well suited to this task, for a slightly counterintuitive reason: apology emails are hard to write because you are emotionally involved, and the model isn’t.

When you’ve made a mistake, the natural instinct is to explain and defend. That instinct produces exactly the low-ranked components — explanation and self-justification — while crowding out responsibility and repair. A draft you didn’t write emotionally is often structurally better.

What AI does well here:

• Producing the five-part structure consistently, so responsibility comes first
• Holding a word count, which is where most apologies fail
• Adjusting formality for a customer versus a client versus your boss
• Generating the same apology in several languages for international customers
• Stripping defensive phrasing you can’t see in your own writing

What it can’t do:

• Decide what your actual repair offer is. That’s a business decision with a cost.
• Know what really went wrong. If you feed it a vague description, you get a vague apology.
• Judge whether email is the right channel at all.
• Handle the compliance question in the section above.

A workflow that works:

1. Write down the facts plainly — what happened, whose fault, what you’ll do about it
2. Have AI draft it in the five-part structure, under 150 words
3. Read it and delete anything defensive
4. Check responsibility is in sentence one and repair in sentence two
5. Add one specific detail only you would know — a number, a date, a name
6. Read it aloud before sending

Step five is the one that matters. A structurally perfect apology with no specifics reads as generated, and readers are getting fast at spotting that. The number, the exact duration, the named cause — that’s what makes it credible.

Write Better Apology Emails with Writegenic AI

Writegenic AI is a writing platform with 300+ templates and support for 120+ languages. For apology emails specifically:

• AI Writer and tools library — drafting to the five-part structure and holding the word count
• AI Prompt Generator — build one reusable prompt encoding responsibility-first order and your tone rules, so every apology comes out shaped correctly. Our guide to what an AI prompt generator is covers how
• 120+ languages — the same apology for customers who’d rather read in their own language
• Team features — so your support team apologises consistently instead of five people improvising under pressure

Being straight about the limits. Writegenic drafts the email. It does not decide your refund policy, know what your engineer broke, or tell you whether an incident is a notifiable breach. Those stay with you, and on the compliance question specifically, ask your legal team rather than a writing tool.

Start with Writegenic AI free.

8 Mistakes That Ruin an Apology Email

1. Burying responsibility behind pleasantries. “I hope you’re well” costs you the most valuable position in the email.

2. Using “if.” “Sorry if this caused any inconvenience” is not an apology.

3. Passive voice. “Mistakes were made” has no subject on purpose.

4. Explaining more than repairing. Explanation ranks tied-third. Repair ranks second.

5. Asking for forgiveness. Ranked least effective of the six components.

6. Promising it will never happen again. Say what changed instead.

7. Leading with a discount code. Fix the problem, then offer the extra.

8. Sending from a no-reply address. An apology you can’t reply to isn’t one.

Apology Email Checklist

• [ ] Responsibility is in the first sentence
• [ ] The repair offer is in the second
• [ ] No conditional “if”
• [ ] No passive voice hiding who did it
• [ ] No request for forgiveness
• [ ] No promise you can’t keep
• [ ] Under 150 words for a standard situation
• [ ] Contains one specific number, date, or name
• [ ] Explanation is one sentence, not a paragraph
• [ ] Real reply-to address that a person monitors
• [ ] Subject line names the problem and the fix
• [ ] Sent within hours, not days
• [ ] Checked whether email is the right channel at all
• [ ] Checked whether personal data was involved, and escalated if so
• [ ] Read aloud once before sending

Frequently Asked Questions About How to Write an Apology Email

Related reading: How to Write a Perfect Welcome Email · LinkedIn Post Guide · What Is an AI Prompt Generator? · AI Article Wizard