Most searches for an apology email sample are made under time pressure, with a client already waiting and a draft on screen that has been rewritten four times. The drafts get longer each pass. That is the tell: the rewriting is not improving the apology, it is adding explanation, and explanation is the part the client did not ask for.
The templates that come up for this query are generous in number and thin in a specific way. They give the words and not the decisions. Which situation calls for a reason and which does not, how much detail a client can be told before it reads as excuse making, whether to offer anything, and who sends the message when two people noticed the problem at the same time. Those decisions are what make an apology land, and none of them are solved by a better sentence.
What is actually being decided
An apology email carries three payloads at once, and the tension between them is the reason the draft keeps growing.
The first is acknowledgement. The client wants to know that the problem is understood as a problem, in their terms, not reframed as a minor process deviation.
The second is information. They want to know enough to make their own decisions. If a deliverable is late, the useful information is the new date, not the reason for the delay. If an invoice was wrong, the useful information is what the corrected figure is and what they should do with the one already in their system.
The third is reassurance about the future. Not a promise that nothing will ever go wrong again, which nobody believes, but a statement of what has changed.
Explaining is what happens when the first payload is weak and the writer tries to compensate. A long causal account reads as a request for sympathy, and it invites the client to audit the reasoning. A short acknowledgement followed by concrete next steps reads as competence, because it shows the situation is already under control.
The five parts that have to be present
Almost every apology worth sending has the same skeleton, in this order.
The subject line says what it is about. Not Apologies on its own, and not Regarding your recent order. Naming the thing means the client can find the message again in six weeks, which matters more than tone. The subject Invoice 4417 was sent with the wrong total does a full sentence of work before anything is opened.
The apology comes first and stands alone. One sentence, at the top, with no clause attached to it. The moment a "but" or a "however" follows, the apology stops being one.
The facts take one or two lines. What happened, stated plainly, in the client's terms rather than in internal vocabulary. The file we sent on Tuesday was an earlier draft is a fact. A version control issue occurred during handover is a description of an internal process that the client has no use for.
The remedy is specific and dated. A correction going out today, a replacement arriving Thursday, a credit applied to the next invoice. Vague reassurance in this slot is what turns an apology into a second problem, because the client now has to chase the remedy as well.
The next step is assigned to a person. Either it is clear that nothing is required from the client, or exactly one thing is asked of them. Never leave it ambiguous, and never ask for two things.
Anything that does not fit one of those five slots is a candidate for deletion. That single rule shortens most drafts by a third.
Four samples
Each of these is deliberately short. Length signals anxiety, and anxiety is not reassuring to somebody who is already annoyed.
A small slip, caught quickly
Subject: Correction to the figures in this morning's report
Hello [name],
Apologies for the error in the report sent this morning.
The revenue column on page three used last quarter's figures.
A corrected version is attached, and the totals on every other
page are unaffected.
Nothing is needed from you. If the earlier version has already
been shared onward, let me know and I will send a note to the
same list.
Best regards,
[name]
Note what is absent. No explanation of how the wrong file got attached, because the client's exposure is limited to one column and it is already fixed.
A missed deadline
Subject: [project] delivery is moving to Thursday 14th
Hello [name],
Apologies. The draft promised for today will not be ready, and
the new date is Thursday 14th.
Two of the three sections are complete and are attached so you
can start reviewing. The remaining section covers the pricing
comparison and needs one more round of checking before it is
worth your time.
If Thursday causes a problem for the board pack, say so today
and the pricing section can go over as a standalone note on
Tuesday instead.
Best regards,
[name]
The structural choice here is giving the client something usable in the same message as the bad news. A missed date with nothing attached forces them to wait twice.
An error that reached the client's own customers
Subject: Incorrect discount code in yesterday's campaign
Hello [name],
Apologies for the incorrect code in the email that went out
yesterday afternoon.
The code in the message expired on the 31st. Roughly 2,400
recipients would have seen the error, and 38 attempted to use
it.
A replacement code valid until the end of next month has been
created and is ready to send. The draft correction email is
attached for approval, and it can go out within an hour of
your reply. The 38 who tried the expired code will be
contacted individually.
One decision is needed from you: whether the correction goes
to the full list or only to the 38.
Best regards,
[name]
Numbers do the work that adjectives cannot. The phrase a small number of recipients invites a question. The sentence 38 attempted to use it answers it.
When the cause is not yet known
Subject: Uploads failing on your account since 09:40
Hello [name],
Apologies for the disruption. Uploads on your account have
been failing since 09:40 and the cause is still being
identified.
What is known: the failure affects uploads only, and files
already in the account are unaffected. Work is ongoing now.
An update will follow by 14:00 whether or not the cause has
been found by then. Nothing is needed from you in the
meantime.
Best regards,
[name]
Committing to the time of the next update, rather than to a fix, is the part that keeps an unresolved incident from generating five inbound emails.
The explaining that makes it worse
Four habits account for most of the damage in apology emails, and all four come from good intentions.
The causal essay. Three paragraphs on how the situation arose. It reads as a defence, and a defence implies the writer thinks a defence is needed. Keep the cause to one clause, or omit it where the client's exposure is already closed.
The passive construction. Phrasings such as An error was made describe events without actors, which is precisely why they are reached for. Clients read it as distancing. The sentence The file was not sent and the sentence I did not send the file carry the same information and land completely differently.
Borrowed formality. The phrase We sincerely regret any inconvenience this may have caused is four hedges in one sentence: sincerely, any, may, have caused. A client who has genuinely been inconvenienced reads the hedging accurately.
Pre emptive defence. Explaining the safeguards that were in place before the failure, in the same message as the failure. It reads as an argument that the failure was unreasonable, and it directs attention at the one thing nobody wants examined.
| Instead of | Write |
|---|---|
We sincerely regret any inconvenience |
Apologies for the disruption |
Due to unforeseen circumstances |
The supplier missed the shipping date |
An error occurred in processing |
The invoice was calculated on the old rate |
We will look into this as a matter of urgency |
An update will follow by 14:00 |
We value your business |
Nothing further is needed from you |
Please accept our apologies for any issues experienced |
Apologies. Here is what happened and what is being done |
Apologising to a list rather than to one client
An apology that has to reach four hundred clients is a different piece of writing, and treating it as the single client version with a bigger recipient field goes wrong in predictable ways.
Send it individually rather than to a list. A client who can see three hundred other addresses learns two things at once: that they were affected as part of a batch, and that the sender is careless with contact details. Where the tooling cannot personalise, one message per recipient sent from a proper mailing tool is still better than a visible list.
Say less about the cause, not more. A broad message is read by people with very different stakes, including some who were not materially affected and who will form their impression of the incident entirely from this paragraph. A short factual line travels better across that range than a detailed account, which invites the most exposed reader to look for the part that lets them off and the least exposed reader to wonder what else is going on.
Name one channel for replies and make sure it is staffed before the message goes out. A broadcast apology generates inbound volume in the first hour, concentrated and impatient, and the worst outcome available is an apology followed by silence when people answer it. Estimating that volume is worth doing crudely: if one in twenty recipients replies, four hundred recipients means twenty conversations arriving at once.
Decide in advance who owns those replies. This is the situation where duplicate and contradictory answers are most likely, because volume creates urgency and urgency makes people skip the check on whether a colleague has already responded. Agreeing beforehand that inbound goes to one queue, with an owner assigned per message, costs ten minutes and prevents the second incident.
Finally, keep one canonical version of what was sent. When a client forwards the message back three weeks later asking why the promised credit has not appeared, the answer depends on the exact wording that went out, and reconstructing it from memory is not an option.
When compensation belongs in the message
Offering something in the apology itself is right when the loss is clear, measurable, and attributable. A refund of a delivery charge for a shipment that did not arrive on the promised day belongs in the first message, because withholding it creates a negotiation that costs more goodwill than the charge is worth.
Offering something is premature when the loss is not yet known. A gesture attached to an unresolved incident sets the ceiling of what the client will accept before anyone knows what happened, and it converts a service conversation into a commercial one. The sequence that works is to resolve the problem, then ask whether a remedy is appropriate.
Offering something is wrong when it substitutes for the fix. A credit sent in place of the corrected deliverable reads as buying silence, and clients notice.
Making sure the apology is sent exactly once
There is a failure mode that no template addresses, and it is common on teams of more than one person. Two colleagues see the same complaint. Both feel responsible. Both apologise, in slightly different words, with slightly different dates. The client now has two versions of the truth and a reason to doubt both.
The cause is structural rather than careless. When the record of a complaint lives in a shared inbox or a spreadsheet and the reply gets composed in each person's own mail client, there is no place where "answered, by this person, at this time" is visible to everyone. Each colleague is acting on the best information available to them.
Three arrangements prevent it. An explicit owner recorded on the request itself, not agreed verbally. A status that changes when the reply is sent rather than when somebody remembers to update it. A copy of what was actually sent, attached to the record, so the second person to look can read the first person's words instead of guessing at them. That is the same requirement described on this use cases page for complaint and support intake, and it is the reason holding the message and the record in one place matters more than the wording of any single template.
What to change first
Take the last apology email sent and delete every sentence that is not one of the five parts. If the result is under 120 words and still says what happened, what is being done, and by when, the template problem is solved. Then check whether anyone else could have sent that same apology without knowing this one existed, and if the answer is yes, fix that next with Halict.
Q1. How long should an apology email to a client be?
Under 150 words for most situations, and under 250 for an incident affecting the client's own customers. Length reads as anxiety, and anxiety undermines the reassurance the message is supposed to provide. If a draft runs longer, the excess is almost always explanation of cause rather than information the client can act on.
Q2. Should the reason for the mistake be included?
One clause, where the reason changes what the client should do. A late delivery caused by a supplier is worth saying because it tells the client whether to expect a repeat. Internal process detail is not, because the client cannot act on it and it reads as a defence.
Q3. Is it better to apologise by email or by phone?
Phone first for anything with financial exposure or a deadline the client has committed to onward, then email to confirm what was agreed. Email alone is right for small, closed errors. The written record matters either way, because agreements made verbally during an apology are the ones most often remembered differently later.
Q4. Should a discount or credit be offered straight away?
Only when the loss is clear and measurable, such as a delivery charge for a shipment that missed its date. On an unresolved incident, an early offer sets the ceiling of what the client will accept before the scale of the problem is known, and it shifts the conversation from fixing to compensating.
Q5. How do you stop two people apologising for the same thing?
Record an owner on the request itself rather than agreeing it verbally, let the status change when the reply is sent rather than when someone updates it by hand, and keep a copy of the sent message attached to the record. Without those three, a shared inbox will produce duplicate apologies in different words.