阅读中文版本

Incident Customer Communication Workflow

Publish clear, regular status updates during an incident that state impact and next update time without speculation.

Overview

Keep customers informed during incidents with accurate, regularly scheduled updates.

This workflow is reusable across teams and environments; adapt the commands to your tooling while keeping the sequence and checkpoints intact.

Environment and prerequisites

• A status page or channel
• An approved message template
• An update cadence

Procedure

1. Acknowledge the incident

Post an initial update stating what is affected and that investigation is underway.

Expected state: Customers know the issue is being handled.

2. State impact precisely

Describe affected functions and scope without guessing at causes.

Expected state: Updates describe impact, not speculation.

3. Commit to an update cadence

Set and keep a regular interval for the next update.

Expected state: Customers know when to expect news.

4. Close with a resolution note

Post a final update with the outcome and any follow-up.

Expected state: Customers have closure and next steps.

# status update template
# Impact: checkout is failing for some users
# Next update: 15:30 UTC

Verification

Confirm updates met the committed cadence, described impact without speculation, and a resolution note closed the incident.

Decision points

Speculate on causes publicly?

• State impact only
• Share probable cause

Recommendation: State confirmed impact; share cause only when verified to avoid misleading customers.

Update cadence?

• Fixed short interval
• Only when something changes

Recommendation: Use a fixed interval so silence is not read as resolution.

Common failures

• Speculative causes erode trust when they are wrong.
• Missing cadence makes customers assume the worst.
• No closing note leaves customers unsure.