Email6 min read

How to tell a customer about a delay without vague reassurance

When something is late, the temptation is to write that you are looking into it and will keep them posted. That sentence tells the customer nothing they can act on. A better delay email names the item that is late, separates what is confirmed from what is still unknown, and gives a specific point for the next update, without promising a date you cannot confirm.

Name the late item before you explain it

Customers scan a delay email for one thing: what is affected. If the first sentence is an apology or a general statement about high volumes, the reader has to keep reading to find out whether the problem touches them. Lead with the item, order, or step that is late, then explain.

This also forces you to be precise. "Your order is delayed" is weaker than naming the part of the order that has not moved. If only one item in a multi-item order is late, say so; the customer may not need to change any plans.

Before

Hi Priya, thanks for your patience. We're currently experiencing some delays and wanted to keep you updated. We'll let you know as soon as we have more information.

After

Hi Priya, the replacement screen for your order has not shipped yet. The rest of your order is not affected. We'll let you know as soon as we have more information.
The rewrite names the late item in the first sentence and states that the rest of the order is unaffected. The closing sentence is kept as written because it is the only update commitment the original makes.

Separate what is known from what is not

A delay email usually contains two kinds of information: facts you have confirmed and questions still open. Mixing them in one paragraph makes everything sound equally uncertain, which reads as evasion.

Use plain labels. "What we know" and "What we don't know yet" are enough; you do not need a formal table. Under each, list only what belongs there. If the only confirmed fact is that the item has not left the warehouse, that is the fact to state. Do not pad the known list with restatements of the apology.

Keep hedges where they are doing real work. If a cause is suspected but not confirmed, write that it is suspected. Removing "we think" or "it appears" to sound more decisive turns a guess into a claim you may have to retract.

Before

We think the courier may have missed the pickup on Tuesday, so your parcel is delayed. We're investigating and will update you.

After

Your parcel is delayed. We think the courier may have missed the pickup on Tuesday; that is not confirmed yet. We're investigating and will update you.
The rewrite states the delay as fact and keeps the cause as a suspicion, using the same hedge as the original. The reader can now tell which part is settled and which is still being checked.

Give the next update a time, not a delivery date

The hardest line in a delay email is the one about when things will be fixed. If you cannot confirm a date, do not offer one. What you can usually offer is when you will next contact the customer, even if that contact carries no new answer.

Phrase it as a commitment you control: "I will email you again on Thursday, 12 June, even if there is no change." That sentence is honest about the uncertainty and still gives the reader something to plan around. It is not a promise that the item will arrive on that date, and it should not be read as one, so keep the two ideas in separate sentences.

If you genuinely have no date for the next update either, say what triggers it: "I will email you as soon as the warehouse confirms the dispatch." That is weaker, but it is still more useful than "soon."

Before

We'll keep you posted and hope to have this resolved soon. I'll email you again on Thursday, 12 June even if there is no change. Sorry again for the inconvenience.

After

I will email you again on Thursday, 12 June, even if there is no change. Sorry again for the inconvenience.
The dated commitment already in the draft is moved to the front, and the vague "keep you posted" and the hopeful "resolved soon" are dropped. The date is one the writer controls, so it does not promise that the delay itself will be resolved by then.

Keep apologies short and out of the way

An apology belongs in a delay email, but it should not carry the information. One sentence near the start or end is enough. When an apology is stretched across several sentences, it starts to read as a substitute for the facts the customer is waiting for.

The same applies to explanations of internal process. A sentence about how the team is working on it is fine; a paragraph about staffing or systems usually pushes the useful lines further down the message.

Check the draft against the facts before sending

Before you send, reread the draft with one question per line: is this confirmed, is this a guess, and is this a commitment? Any sentence that mixes the three needs splitting.

Pay particular attention to names, order numbers, dates, and weekday names. A rewrite that tidies the prose but shifts a date by a day is worse than the clumsy original. If you use a rewriting tool such as Lightphrase to retone a draft, compare the output against your original line by line before pasting it into the email; the tool replaces or copies text, but it does not know which details are load-bearing.

Finally, check that you have not added a promise the customer did not ask for and you cannot keep. A clearer delay email is not a more generous one; it is one where every sentence can be defended if the customer quotes it back.

  • Does the first sentence name the late item?
  • Is each cause marked as confirmed or suspected?
  • Is the next update a date you control, or a trigger you can watch?
  • Are all order numbers, names, and dates identical to your source notes?

Take it into your next draft

Before sending a delay email, rewrite the opening so it names the late item, split confirmed facts from open questions, and replace "we'll keep you posted" with a specific date for your next message or a clear trigger for it. Then read the draft once more against your notes to confirm that no date, number, or hedge has shifted. The goal is not a warmer email; it is one where the customer knows exactly what is late, what you know, and when they will hear from you again.