PRACTICAL SPEAKING GUIDE

Give an incident update without speculation

A booking service is failing for some customers.

2026-09-27 · Original teaching notes by SpeakBEC

Start with the situation

A booking service is failing for some customers. The cause has not been confirmed. People need an update now, but a confident guess about the cause could mislead them and create a second problem.

A possible exchange

Some customers are currently unable to complete a booking.

We have confirmed the checkout failure, but not its cause.

The support team is collecting affected booking details while engineering investigates.

We’ll post another update at three, even if the investigation is still ongoing.

Why this works

The update separates impact, confirmed knowledge, current action and the next communication time. It does not invent a repair deadline. Saying when you will communicate again is a commitment you can often make even when you cannot promise when the underlying problem will be solved.

Avoid “Everything is under control” if you cannot explain what is controlled. Also avoid repeating rumours with “apparently” as if that makes them safe to circulate. If an earlier update was wrong, correct it explicitly. Tailor operational details to the audience: customers need to know the impact and available actions, while an internal technical team may need a different level of detail.

Change the condition and try it

A shipping delay affects several orders, but the warehouse has not confirmed which ones. Give an update that states the uncertainty, tells customers how confirmed cases will be contacted and sets a time for the next update. Do not imply all orders are affected.

Try a spoken or written response before checking it. Did you address the changed condition? Could the listener identify the next step? The model is not the only acceptable answer.