Communicate during an incident without freezing up
When something is down, the hardest part is often writing the update while under pressure. Vague or absent communication erodes trust faster than the outage itself. This builder gives you calm, customer-appropriate templates for each stage of an incident — initial notice, ongoing update, and resolution — in both status-page and email form, so you can fill in the facts and send.
How it works
You enter the incident facts: affected product or feature, the customer impact in plain words, severity, and a timestamp. You choose the stage, and the template adapts:
- Initial notice — acknowledges the issue, states impact, confirms investigation, and commits to a next-update time. No cause speculation, no premature fix promise.
- Ongoing update — reports progress honestly (including “still investigating”), restates impact, and renews the next-update time.
- Resolution — confirms restoration, gives the fix time, apologizes, and points to a follow-up review if planned.
For each stage the tool produces a short status-page version and a slightly fuller email version, since the two channels need different lengths. Everything is generated in your browser.
Tips and example
Lead with impact, not internals. “Some users cannot log in” tells customers what they need; “the auth pod is crash-looping” does not. Keep the tone calm and human — no blame, no jargon, no over-promising.
Always end an active-incident message with a concrete next-update time and then honor it. A 30-minute cadence that says “still investigating, next update by 14:30” beats an hour of silence followed by a fix. Customers tolerate problems; they do not tolerate feeling ignored.
Save the detailed root cause for the post-incident review, published after you genuinely understand what happened. During the incident, the resolution message just needs to confirm service is back, acknowledge the disruption, apologize once and sincerely, and promise the deeper write-up if one is coming.