The same incident, told to four different readers

Enter your incident facts once. Get four audience-specific drafts — status page, customer email, engineering note, exec summary — side by side. Copy the one you need. No account, no login, no storage.

Open the tool Pricing

How it works

Fill the facts

Severity, affected component, what users experience, start time, current state, actions taken, next update time, internal notes. That is everything the tool needs.

Check what is confirmed

If the root cause is not yet confirmed, every draft says "We are investigating." No draft invents a cause you have not marked as settled.

See four drafts at once

The status page post avoids internal names. The customer email commits only to what is true. The engineering note may name the component. The exec summary leads with business impact.

Copy and send

Each draft panel is selectable. Copy the one you need and paste it into your status page, email client, Slack thread, or incident report. The tool does not send anything — a human always decides what to publish.

No AI, no model calls, no invented facts. Every word is deterministic from what you enter.

What each draft does

S
Status-page post — Tells users what they experience. Omits internal component names and unconfirmed causes.
C
Customer email — Explanatory and factual. Commits only to what is already true. No conjecture.
E
Engineering note — May name the component and suspected or confirmed cause. Concise, with internal detail.
X
Exec summary — Leads with business impact. Avoids technical detail. One paragraph with a time.

Drafts, not delivery

CommsCrisis produces text. It does not send email, post to a status page, create a Slack message, or update PagerDuty. A human reviews and sends. This is deliberate — during a P1, the person who sends should be the person who decides.

Start drafting