Incident Communication Templates: Customers, Status Page, and Slack

During an incident, writing is the second most expensive thing you do — after the actual fixing. Teams without templates freeze on the status page for twenty minutes trying to make a sentence perfect, and customers read silence as "they don't know yet, and it's worse than they say."

These are the four messages a 1–50 person team actually needs. Copy them into your runbook tonight; fill the brackets during the bad day.

1. The first customer ack (send within 15 minutes)

We're aware of an issue affecting [what, in plain words — "sign-in", not "auth service"]. We're on it and will post an update by [time +30 min]. No action needed from you.

Two rules: name the symptom the customer sees, not your internal component, and always promise the next update at a specific time. A promised update keeps you honest; a vague "we're working on it" just postpones the panic.

2. Status page updates (every 30–60 min while degraded)

[HH:MM] Still working on [plain-words issue]. Progress: [one sentence of real progress]. Next update: [time].

Every update has the same three slots: what's still broken, one concrete thing that changed, when to look again. If nothing changed, say so — "no change yet, still on it, next update 10:30" is a good update. Customers forgive slowness; they don't forgive finding out nothing was happening.

3. The exec/leadership update (five lines, no jargon)

Issue: [one line]. Customers affected: [number/group]. Money impact: [orders/logins/sales]. Fix: [what's being done, one line]. Next update: [time].

If your leadership update takes more than five lines, you've stopped informing and started defending. The executive's job is to decide whether to tell the whole company or pause a launch — give them the five facts that feed that decision.

4. The resolution note (post everywhere you posted updates)

Resolved as of [time]. What happened: [plain words]. What we're doing so it doesn't repeat: [one concrete action]. If you still see anything odd, reply here — we're watching until [time].

The resolution note is the only message some customers will ever read, so it can't reference the earlier ones. And the last line — "we're watching until X" — converts a bad day into a story about how you handle bad days.

The one channel rule

Internally, one channel, one incident. If the war room is split across Slack, a Zoom, and two DMs, half your team is reading stale information. Everything worth keeping — decisions, timeline entries, updates — gets pasted into the incident doc, because the doc is what the postmortem reads from.

---

These snippets come pre-built into the Ops Starter Kit Vol. 2 — Advanced Incident Response & Comms, which adds the full customer/status/exec template set with severity-based variants. The original Ops Starter Kit ($14) covers the IR plan, severity matrix, and tabletops — launch week: 30% off any paid kit with code HIVE-LAUNCH30.