The three sentences that matter are: what happened, what you have done about it, and what happens next. Almost every failed apology email misses at least one. Most miss the third, which is the one the customer is actually waiting for โ it tells them whether to keep waiting, do something themselves, or leave.
The other rule is that the apology belongs to the organisation, not to the conditions. "We apologise for any inconvenience" apologises for nothing. "We sent the wrong item" apologises for something, and it is verifiable. Customers forgive specifics; they do not forgive hedging.
The six templates
1. Delay with a known new date
Use when: you have missed a date and you know when it will actually land.
Subject: Your order [number] โ now shipping [date]
[Name],
Your [item] was due on [original date] and it has not shipped. It will ship on [new date] and arrive by [new arrival date].
The delay is [specific cause, stated plainly]. We have [specific action taken โ reserved stock, upgraded shipping, moved you to the front of the queue].
You do not need to do anything. If the new date does not work, reply to this email and we will [specific alternative].
[Your name], [Company]
2. Delay with no confirmed date
Use when: you genuinely do not know yet โ say so, and commit to a date by which you will know.
Subject: Update on your order [number]
[Name],
Your [item] has not shipped and I do not have a confirmed date yet. I will email you by [date] with either a shipping date or [alternative option].
What I can tell you now: [known facts]. What I am waiting on: [specific dependency].
If you would rather not wait, reply and we will [refund / swap / cancel] immediately.
[Your name], [Company]
3. We made an error
Use when: the mistake is yours and the customer has already noticed or will.
Subject: We made a mistake on your [order/service] โ here is what we are doing
[Name],
We [specific error]. That is our error, not a system issue or a misunderstanding.
We have already [specific correction]. You will see [specific result] by [date].
To make it right, we are also [specific remedy โ refund, credit, repeat at no charge].
Reply to this email if you would like to talk it through.
[Your name], [Company]
4. Billing mistake
Use when: you charged the wrong amount, twice, or after cancellation.
Subject: Correction to your invoice [number]
[Name],
We charged you [wrong amount] on [date]. The correct amount is [correct amount].
The difference of [amount] has been refunded to [original payment method] and will appear within [number] business days.
Your correct invoice is attached. I have noted the account so this does not recur.
[Your name], [Company]
5. Missed appointment or no-show on your side
Use when: you failed to turn up or the service did not happen.
Subject: We missed our appointment โ rescheduling at no charge
[Name],
We did not attend the appointment scheduled for [date] at [time]. There is no adequate explanation for that, and I am not going to offer one.
I have [specific remedy], and I have held [specific time slots] if any of them suit you.
Reply with a time, or call [phone] and ask for me directly.
[Your name], [Company]
6. Complaint that went public
Use when: replying to a review, a post, or a public thread.
Subject: [reply channel] โ response from [Company]
[Name],
I am [Your name], [Title] at [Company]. I have read what you posted and I am looking into it.
What I can confirm now: [verifiable facts]. What I am still checking: [specific item].
I will post an update here by [date]. If you would rather handle it directly, email me at [email].
[Your name], [Company]
What to leave out
Three habits reliably make things worse. Conditional apology โ "we apologise if you were unhappy" disputes the customer's account. Blaming a system or a supplier, which reads as avoiding ownership even when it is factually true. Over-explaining the internal cause, which spends the reader's patience on details that change nothing for them.
When to pick up the phone instead
Email is right when the issue is minor, the customer has shown they prefer writing, or you need a record. Call when the customer has lost money or time, when the fix requires their decision, or when they are angry enough that a slow reply will be read as indifference. In our testing, the threshold that matters is not the size of the problem but whether the customer is waiting on you to act.
Say what happened, then say what is next
Draft the structure in a tool. The specifics โ the date, the cause, the remedy โ have to be yours.
Try Rytr โFrequently Asked Questions
How long should an apology email be?
Short. What happened, what you did, what happens next โ usually under 150 words.
Should I apologise if it was not our fault?
Acknowledge the impact without accepting blame you cannot substantiate. "I understand the delay was disruptive" is accurate without conceding fault.
Is "we apologise for any inconvenience" acceptable?
It reads as boilerplate. Replace it with a specific statement of what went wrong.
What if I do not have a fix yet?
Say so, and commit to a date you will have one. An unanswered wait is what loses customers.
Should I offer compensation?
When the customer lost money or time, yes โ and state the amount rather than asking them to name it.
When should I call instead of email?
When the customer is waiting on your decision, or has already lost money or time.