One set of incident facts. Four audiences. Write once.

Enter the incident facts once. Copy the draft you need.

Screenshot of CommsCrisis showing the incident fact entry form at the top and four generated communication drafts — Status Page, Customer Email, Engineering Note, and Exec Summary — displayed side by side in a two-by-two grid below.

Enter incident facts Deterministic templates Status Page Customer Email Engineering Note Exec Summary

The same facts, rewritten four times under pressure.

CommsCrisis is for the engineering lead or CS manager who is thirty minutes into a P1 incident and has three people asking for a different version of the same sentence. A status page post says what users see. A customer email commits only to what is already true. An engineering note may name the component and the suspected cause. An exec summary leads with business impact and a time. Each is the same incident, written for a different reader.

Enter the facts once. Four drafts appear side by side. Copy the one you need.

How it works — no integration, no setup, no account.

Enter the facts. Fill in severity, affected component, what users experience, when it started, current state, what is being done, and the next update time.
Four drafts appear. Each is a deterministic template — no AI, no API call, no data leaves your browser. The wording rules are hard-coded: a status page never names an internal service; a customer email leads with apology, not architecture.
Copy and send. Each draft panel has a copy button. Paste into your status page editor, your email client, your Slack thread, or your exec brief. A human reviews and sends every message — CommsCrisis drafts, it does not deliver.

Free, because the tool has no server to run.

Everything runs in your browser. There is no backend, no database, no accounts, no API usage to meter. The free tier is the full product: unlimited drafts, unlimited use, no signup required.

See the pricing page for a breakdown of what exists today and what would need infrastructure that does not yet exist.

What a draft actually looks like.

Suppose the API gateway returned 503s for 14 minutes, starting at 14:32 UTC. The severity is SEV1, the component is "API Gateway", users see "Service Unavailable" errors, engineers are routing around a bad deployment, and the root cause is not yet confirmed.

The status page draft says: "We are currently investigating an issue with the API Gateway. Some users may see 'Service Unavailable' errors. Next update: 15:15 UTC."

The customer email draft says: "We apologise for the disruption. Some services are currently unavailable. Our team is investigating and will provide an update within 30 minutes."

The engineering note says: "API Gateway — 503 errors since 14:32 UTC. Suspected: recent deployment (unconfirmed). Team routing traffic around ASG-3. ETA: TBD."

The exec summary says: "Impact: API Gateway unavailable since 14:32 UTC. Business impact: all customer-facing API calls failing. Status: investigating (root cause not yet confirmed). Next report: 15:15 UTC."

Try it with your incident facts

What this tool does not do — stated plainly.

Does not send anything. There is no email sender, no webhook, no Slack integration, no posting to a status page. CommsCrisis drafts text for a human to review and send. This is deliberate — during an incident, a tool that auto-publishes can publish a fact you have not yet verified.

Does not store incidents. Nothing survives a page close. There is no account, no login, no history, no audit trail. An incident record that silently disappears is worse than one that was never promised.

Does not integrate with other tools. No PagerDuty, Statuspage, Slack, Jira, or any external system. The tool is a text box and four templates.

Does not invent facts. The drafts never state a root cause as settled unless you mark it confirmed. They never supply a customer count, an ETA, a number of affected users, or a cause that is not your own input. If a field is empty the draft leaves a clearly marked gap.

Does not offer SLA credits, legal language, or admission of liability. The generated text is operational communication only. Consult your legal team before making commitments to customers.

"Could I just paste a template into a doc and never return?"

You could, and if your incident format never changes, that would work. But four templates for four audiences means managing four separate files — and when the facts change mid-incident (the component turns out to be the database, not the API), you make the same edit in four places. This tool shows all four drafts at once, so you see the effect of an edit on every audience before you copy anything.

More importantly: the templates encode the *wording rules* that are easy to forget under pressure — a status page never names an internal service, a customer email never states an unconfirmed cause as settled, and an exec summary leads with business impact rather than architecture. That is the value this tool adds, and a template file does not enforce it.