How to Tell a Customer About a Delay

Telling a customer about a delay is uncomfortable, so drafts often drift toward one of two extremes: a vague reassurance that hides the problem, or a long apology that makes the customer search for the new plan.

Neither helps. A useful delay message should answer four questions:

1. What is delayed?
2. How does it affect the customer?
3. What are you doing now?
4. When will they hear from you again?

You may not have a new completion date yet. You should still give the customer a clear next update.

Say What Changed In The First Paragraph

Do not make the customer read background before learning why you wrote.

Before:

We wanted to get in touch with an update regarding the implementation. The team has been working very hard, and we have made a lot of good progress, but we have encountered a few unforeseen challenges along the way that have affected our original plans.

After:

We will not complete the data migration by the planned 18 July date. Validation is taking longer than expected, and the revised target is 22 July.

The second version is harder to write but easier to trust. It names the commitment, the change, the reason, and the new target without unnecessary drama.

Explain Impact In The Customer’s Terms

Internal details matter only when they help the customer understand the outcome.

Internal version:

The deployment failed because the background worker exhausted its connection pool during the final batch.

Customer-focused version:

The final import did not complete, so your team should continue using the current workspace today. No existing records have been removed. We are rerunning the import after correcting the issue.

The customer needs to know what they should do and whether their data or work is affected. The exact infrastructure detail can wait unless it is relevant or they ask for it.

Apologize Once, Then Move To The Plan

A sincere apology can acknowledge the inconvenience. Repeating it does not create a recovery plan.

Instead of:

We are incredibly sorry and sincerely apologize for this unfortunate delay. We completely understand how frustrating this must be, and we are deeply sorry for any inconvenience this may have caused.

Write:

I am sorry we missed the date we committed to. We have assigned an additional engineer to the validation step and will send you a confirmed completion time by 10:00 tomorrow.

The apology is specific. The rest of the message earns confidence through action, not adjectives.

Do Not Invent Certainty

If the cause is still under investigation, say so. If a new date is not confirmed, do not present an optimistic guess as a commitment.

Weak reassurance:

Everything should be back to normal very soon.

Honest update:

We are still investigating the failed exports. I cannot confirm a resolution time yet. I will send the next update by 16:00 today, even if the investigation is still in progress.

A reliable communication time is valuable even when a reliable resolution time is not yet available.

Give The Customer A Clear Option

When possible, include a practical choice or workaround:

• Continue using the current version until migration completes.
• Receive a partial delivery now and the remainder later.
• Move a meeting to the revised completion date.
• Export the needed records manually while a fix is in progress.
• Contact a named person if the delay creates an urgent problem.

Do not offer an option your team cannot support. One real workaround is better than several vague promises.

A Complete Before And After

Before:

Hi, unfortunately we have run into some technical issues with the dashboard, and the team is doing everything possible to get this resolved ASAP. We really apologize for the inconvenience and appreciate your patience. We will let you know when we have more information.

After:

Hi Elena,

The reporting dashboard will not be ready for your Monday review. Two totals are not updating correctly, and we do not want to release results we cannot verify.

We are correcting the calculation and will confirm a revised delivery date by 14:00 Monday. In the meantime, I can send the verified June export as a spreadsheet if that helps with the review.

I am sorry we missed the agreed date. I will send the next update on Monday, even if the fix is still in progress.

Marcus

The rewrite is longer than “there is a delay,” but every sentence answers a customer question. It makes no promise the team cannot yet support.

For more on keeping requests, constraints, and facts intact during editing, read how to rewrite without losing your point.

Create A Customer-Update Context

A reusable Wrivio Context could say:

Rewrite this as a clear customer update. State the changed commitment early. Preserve all dates, facts, uncertainty, impact, and promised actions exactly. Acknowledge the inconvenience once. Explain what the customer should do now and when they will receive the next update. Do not invent a cause, resolution date, workaround, or reassurance.

In your email or support tool, press Ctrl+Shift+Space, paste the draft into Wrivio, choose the Context, and run the rewrite. Review the word-level diff and verify every date, technical fact, and commitment before copying it back.

For customer information that should remain on the device, choose Local mode; after you download the embedded model, the rewrite text is processed on your Windows PC. Cloud mode is also available for teams and messages where cloud processing fits the situation. If a draft includes unnecessary personal or account data, remove it before rewriting in either mode—the customer update usually does not need it.

A Pre-Send Checklist

• Did I name the delayed commitment?
• Did I explain the customer impact in plain language?
• Did I distinguish confirmed facts from estimates?
• Did I give a new date or a time for the next update?
• Did I include only actions we can actually deliver?
• Did I verify every fact after rewriting?

Customers may not like the delay. Clear communication can at least ensure they are not surprised twice.

Download Wrivio for Windows to refine difficult customer messages while reviewing exactly what changed before you send them.