This simulator runs a complete incident in your browser, on a sample scenario, with no account and no data sent anywhere. You choose the alert, the service, the escalation policy and what time it is, and IncidentBot shows what happens next: who gets paged and how, when escalation kicks in, which Slack channel opens, what the status page says and how the postmortem starts.
| Time | Actor | Event |
|---|---|---|
No events yet. Run the incident to build the timeline.
| Time | Actor | Event |
|---|---|---|
Affected component
Postmortem skeleton sections
Results of this run
Time to acknowledge
People woken up
Escalations used
Policy check
Policy hints
Like what the simulator produced? The same engine runs on your alerts and schedules.
Every step of the incident with computed timestamps: alert received, duplicates grouped, incident opened at the chosen severity, each person paged and on which channel (push first, then SMS, then voice depending on severity and time of day), each escalation, the acknowledgement, the Slack channel created and the roles assigned.
A draft update your customers would see: the affected component, a status derived from severity and a short customer-facing message.
Publish update
The skeleton of the review: a timeline table, the impact window, time to acknowledge and time to resolve from the run, and the sections your team completes.
When the policy is weak, the metrics strip says why. Typical hints: a single tier with no fallback at night, a timeout longer than the severity allows, or a policy that wakes the whole team before a lead has seen the alert.
Evaluating incident response software from a feature list is hard, because the value is in the sequence: what happens in minute one, minute five and minute fifteen. The simulator makes the sequence visible and lets you break it on purpose.
The same rules drive real paging in your workspace, with your schedules from on call scheduling software and your tiers from on call management.
In your account the alert comes from your monitoring, the people are your engineers and the channel opens in your Slack. Everything else behaves the way you saw here.
No. The simulator runs entirely in your browser on a sample scenario. Nothing is paged, nothing is posted to Slack and nothing is stored.
No. It is a simulator, not a plan. IncidentBot is sold as a monthly or annual subscription per responder seat, starting at 49 USD per user per month, or 24 USD billed annually. See pricing.
Yes. Paste a payload from your own monitoring into the payload field. The parser reads the fields each source uses, so a real payload shows you how routing would read it.
Create your account, connect one monitoring source and page your team for real. The how it works page shows the four setup steps.
Your work email and your team size. That is all we need to set up the account.
One price per seat for alerts, on-call, Slack incidents, status page and postmortems.