Customer Comms During Active Incidents
Customers want updates more than fixes. The comms cadence and tone that holds trust.
First update
The first customer-facing update goes out within 15 minutes of detection. Even an “investigating” post counts. Silence is the worst signal a status page can send during an incident; customers fill silence with worst-case assumptions and start escalating to support.
- Within 15 minutes of detection. Fast-acknowledge target. Customers want confirmation they were noticed before they reach for support.
- “Investigating” is enough. No need for a complete picture; acknowledge first, refine later.
- Silence is the worst signal. Customers fill quiet with worst-case assumptions. The status page must speak.
- Named comms author per incident. One person owns the writing thread. Without ownership, first updates fall through cracks.
Middle updates
Middle updates ship every 30 minutes regardless of progress. Predictable cadence is itself trust-preserving; customers learn to wait the 30 minutes instead of paging support every 5.
- Every 30 minutes. Strict cadence. Even with nothing to report, the cadence holds.
- “Still investigating” is fine. Honest no-progress reporting beats radio silence every time.
- Current hypothesis included. The working theory. Customers value transparency on direction even before the fix lands.
- Workaround if known. Customer-actionable mitigation surfaced as soon as it exists. Restores customer agency.
End
Resolution communications close the loop. Honest, specific, and with a public commitment to a follow-up postmortem within a defined window.
- Resolution plus cause summary. Closing post is honest, specific, and free of spin. Customers detect hedging instantly.
- Postmortem follow-up promised. Published-by-when commitment. Customers value follow-through more than the absence of incidents.
- SLA-credit acknowledgement where applicable. Per-customer contractual credits proactively confirmed. Honest accounting builds trust.
- Customer thanks. Brief acknowledgement of patience. Closes the comms thread on a human note.