CommsCrisis
CommsCrisis
Everything you need to use CommsCrisis — the incident communication drafting tool that turns your outage facts into four audience-ready drafts.
Using CommsCrisis takes less than a minute:
That is it. No account, no login, no setup. Refresh the page and your facts are gone — nothing is stored.
No. CommsCrisis runs entirely in your browser. The incident facts you enter — severity, affected component, user experience, and any internal notes — exist only in your browser's memory for the duration of your session. Nothing is sent to any server, stored in a database, or retained after you close the page.
No. CommsCrisis uses deterministic templating — every sentence is produced by rules, not by a language model. A draft can only say what your facts support. There are no model calls, no invented causes, no plausible-sounding guesses. If a field is empty, the draft shows a clearly marked gap, never a fill-in.
Yes. Each draft is plain text displayed in your browser. Select any portion, copy it, paste it into your editor of choice, and edit freely. The tool does not lock or protect any text. If you change your facts, click "Generate drafts" again to get updated versions.
No. CommsCrisis produces drafts — it does not send email, post to a status page, create a Slack message, update PagerDuty, or communicate with any external system. A human always reviews, edits if needed, and decides when and how to publish. This is deliberate: during an incident, the person who sends should be the person who decides.
There is a checkbox labelled "Root cause is confirmed" on the input form. If the checkbox is unchecked (the default), every draft says "We are investigating" and never asserts a cause. The checkbox can only be ticked by the person using the tool — the software never assumes confirmation. This is the single most important safety feature in CommsCrisis.
No account or login is required. There are no usage limits, no rate limiting, and no caps on how many drafts you can generate. CommsCrisis is currently free — £0, no subscription, no paid tier. If a paid tier is ever introduced, users will be notified in advance.
CommsCrisis is a focused tool with deliberate boundaries. The following are not bugs — they are honest limits of what the tool does and does not do:
Each session is standalone. There is no login, no user profile, and no audit trail. If you refresh the page or navigate away, your incident facts are gone. The tool does not store your work — if you need a record, copy the drafts before leaving.
CommsCrisis does not send email, post to a status page, create Slack messages, update PagerDuty, send SMS, push notifications, or integrate with any external system. It produces text for a human to review and publish. There is no email sender, no API integration, and no webhook configured in this fleet.
CommsCrisis does not connect to any third-party service. It cannot pull incident data from monitoring tools, post to incident management platforms, or synchronise with a CRM. All information must be entered manually in the form.
The drafts are produced deterministically from the facts you enter. They are not reviewed for legal accuracy, regulatory compliance, contractual obligations, or SLAs. You are solely responsible for approving any communication before publishing it.
The tool never generates language offering compensation, admitting fault, or committing to financial remedies. If your incident requires SLA credit language, legal review, or liability statements, those must be added by your team after the draft is produced.
Support is not yet reachable by email — no mailbox has been set up for this tool. This is a known gap and has been recorded as an owner action item.
If you have a question the Help Centre does not answer, please direct it to the tool's operator. For bug reports or feature requests, the same applies: describe what you were doing, what you expected, and what happened instead.
Support email: Not yet available — this is a known gap.
Response time: Not yet defined.
Escalation: The tool's owner handles all escalated requests.
Page last updated: 7 September 2026