Major service outage: keep customers informed while recovery continues
During an outage, customers first need to know whether they are affected, what alternatives exist and when they will hear more. Communications must reflect the actual condition of the service.
Keep updates outside the failed dependency
Prepare a status channel with checked dependencies and a fallback. Operations and communications maintain the same account of affected services, regions, users and functions. A reachable website does not mean every transaction works. Avoid declaring global availability based on a single successful test.
Commit to the next update, not an invented fix time
State confirmed facts, operationally validated workarounds and the next update. Distinguish technical estimates from public commitments. Sales must not promise something different from support. When the cause is unknown, describe verified observations and the work underway without speculating about an attack.
Illustrative scenario: a technology company
A platform stops processing some transactions. It explains affected functions, whether requests are retained and what customers should do. It does not recommend repeating a transaction before checking duplication risk. Teams distinguish partial restoration, controlled restart and normal operation. This is an illustrative preparedness scenario.
Explain recovery and prevention
After recovery, provide a verified chronology and useful findings. Avoid promising that an incident can never recur. Follow up on corrective work, dependencies, fallback capacity and notification quality. International customers need clear time zones, local contacts and market-specific service status. Any commercial remedies are assessed by responsible teams and explained separately from technical conclusions.
Sources and further reading
Explore further
Crisis communications: ten situations, ten responses
Practical analysis for initial decisions, information for affected people and follow-through on commitments.
Reputation & crisis
Build a coherent response when facts, expectations and decisions move quickly.
Prepare for our first conversation
A short introduction is enough to start: your organisation, the decision at hand, the audiences involved and your deadline. Confidential documents can follow through an agreed channel.
From insight to action
Reputation & crisis management
Build a coherent response when facts, expectations and decisions move quickly.
Technology, AI and cybersecurity
Technology earns credibility when people understand what it can do, what it cannot do and who is accountable.
Sensitive announcement: a readiness checklist
An announcement is ready when the facts, responsibilities and response arrangements are clear.
Prepare your crisis response
A short introduction is enough to start: your organisation, the decision at hand, the audiences involved and your deadline. Confidential documents can follow through an agreed channel.
Email Belief System