During a P1 the same facts get rewritten for the status page, a customer email, an engineering note, and an exec summary — by four different people. Enter them once and get four honest, register-appropriate drafts.
You are thirty minutes into a P1. Three people have asked you for the same sentence in different language — a public status-page post, a customer email, an internal engineering note, and a briefing for your VP. Each gets a different register, a different level of detail, and a different answer to the question "can you say why yet?"
CommsCrisis takes the incident facts you already have and writes all four. One form. Four drafts. No rewriting. No accidental details in the wrong audience.
Severity, affected component, what users experience, when it started, current state, actions taken, next update time, and whether the cause is confirmed.
The status page post (public), the customer email (professional), the engineering note (internal), and the exec summary (leadership) — each written from the same facts.
Each draft is ready to paste into your status page, email client, Slack, or briefing doc. Nothing is sent, stored, or saved — your incident data stays in your browser.
Never names internal services or engineering details. Says what users experience and when the next update is.
Professional, accessible tone. Commits only to what is already true. No legal language, no SLA promises, no unconfirmed assertions.
May name the component, the suspected cause (if confirmed), and the specific mitigation steps. Accepts internal notes and references.
Leads with business impact and timeline. States root-cause investigation status. One screen of reading for a busy VP.
Enter the facts once and get four drafts that are ready to copy. No account needed.
Start drafting now