Why vague outage notices lose trust
When something breaks, customers do not expect perfection. They expect honesty. A notice that hides behind phrases like “we experienced some technical difficulties” when you actually know what happened reads as evasive, and customers notice the gap between what you are saying and what they just experienced. The fastest way to keep trust during an incident is to say plainly what you know, what you do not know yet, and what happens next.
If the incident is still ongoing
An ongoing incident notice has one job: tell people what is known, what is being done right now, and when they will hear from you again. Do not promise a fix time you do not have. If the cause is not confirmed, say so directly rather than guessing at one to sound more in control.
- State what you currently know, even if that is limited.
- Say what your team is doing about it right now, in plain terms.
- Give a concrete commitment for the next update, such as a time, rather than “we will keep you posted.”
If the incident is resolved
Once it is fixed, the notice shifts to three things: confirm it is fixed, explain what happened at a level a non-technical customer can follow, and say clearly what affected customers should do next, if anything. If there is genuinely nothing for them to do, say that instead of inventing a step to seem thorough.
Common mistakes
- Softening a known cause into vague language like “an issue was identified” when you actually know what broke.
- Using filler like “we take this very seriously” instead of stating what you are actually doing about it.
- Promising a fix time before you actually have one.
- Padding a simple update into a long notice when a few sentences would do.