Getting started, frequently asked questions, and known limitations.
Go to /app. No account or login is required — just open the page and you are ready to go.
Fill in the fields you know: severity, affected component, what users experience, when it started, current state, actions being taken, and next update time. Fields you cannot answer yet can be left blank — the drafts will show an honest gap rather than inventing a value.
Only check "Cause is confirmed" if the root cause is verified by your engineering team. An unconfirmed cause produces "We are investigating" in every draft — the tool never asserts a cause it cannot prove.
PR numbers, load balancer names, or any internal-only detail you want in the engineering note but not in the public or customer-facing drafts. The status page and customer email never expose these.
Click Generate drafts. Four drafts appear side by side: status page post (public), customer email (customer-facing), engineering note (internal), and executive summary (leadership).
Click the Copy button on any draft you need, then paste it into your status page, email client, Slack, or briefing doc. CommsCrisis drafts — a human reviews and sends.
CommsCrisis runs entirely in your browser. No incident facts, drafts, or form inputs are sent to any server. There is no backend, no database, and no API. Every action happens on your device. When you close the page or tab, all data is discarded permanently. The tool makes no network requests except to load the Google Fonts used for typography.
No cookies, tracking pixels, or analytics scripts are used. No data is written to localStorage or sessionStorage.
No — and that is by design. CommsCrisis does not create accounts, maintain sessions, or store any data persistently. All drafts exist only in browser memory for the duration of your session. This is a deliberate privacy and security measure: incident data never leaves your device, and there is nowhere it could be retrieved from after you close the page.
What to do: Copy each draft you need before closing the page. Pasting into a document, an email draft, or your status page tool is the intended workflow.
The tool never invents a fact you did not supply. If you leave the "Cause is confirmed" checkbox unchecked, every draft uses the default language "We are investigating" — which is the honest thing to say during an active incident.
To include a root cause in the drafts, check "Cause is confirmed" and describe the cause in the text field that appears. The tool will then use your confirmed cause wording in the engineering note and exec summary. Even then, the status page and customer email use cautious language that never admits liability.
No. CommsCrisis uses deterministic templates — the same input always produces the same output. There is no LLM call, no model, no AI inference. This is intentional: during a P1, the last thing you want is a draft that varies between runs or invents details.
Because there is no model call, no incident data is sent anywhere for processing, and no data leaves your browser.
No. CommsCrisis generates text drafts that you copy and paste. It does not send email, post to status pages, create tickets, send webhooks, or trigger any external action. A human must review and send each draft.
This is a hard constraint of the product — there is no email sender, no API integration, and no posting capability in the fleet. The tool is designed to make drafting faster, not to automate delivery. Automated sending is not planned.
The current Free tier includes unlimited incident drafts with all four audience templates, requires no account or signup, and stores no data. It is fully functional as described on this site.
A Team plan is in development and will add shared workspaces, incident history, custom branding on exports, and priority support. It is not yet available for purchase. Any checkout form on the pricing page is a demonstration — no payment is processed, no data is saved. Join the waitlist to be notified when the Team plan launches.
These are honest constraints of the current product. Some are intentional by design; others are gaps awaiting an owner decision.
needs.md.Email support is not yet available. The operator has not established a contact mailbox or support address. This is a known gap and has been recorded as an owner action. Until it is resolved, the following resources are the best ways to understand the product:
needs.md for the full list of unresolved owner actions.