Incident response runbook in Slack
When something breaks, run the runbook where the incident is already being handled — in Slack.
During an incident the last thing on-call wants is to leave Slack for another tool. But ad-hoc response means missed steps: who paged comms, did anyone start the post-mortem, is the status page updated?
Tovo runs your incident runbook as a checklist in the incident channel. Each step has an owner, relay can drive the sequence, and the thread becomes a timeline of exactly what happened and when.
🚨 Incident — checkout 5xx spike
revert v2.4.0; watch error rate
No tool-switching mid-incident
Response runs in the incident channel — no second app to open while things are on fire.
Claim and own
Responders react 👀 to claim a step instantly, so nothing is left unowned.
Built-in timeline
The thread logs every action with a timestamp — your post-mortem timeline writes itself.
One runbook, every incident
Save the runbook as a template so severity-1s always follow the same steps.
How to set it up
From install to running it — step by step.
- 1
Launch the runbook
In the incident channel, run /tovo start and pick your incident template — or mention @tovo with the steps to spin one up fast.
- 2
Assign owners
Set owners for each step — on-call, comms, lead — or let responders claim a task by reacting 👀 to take it.
- 3
Work the steps live
Tap ✅ as each step completes; relay mode keeps the response moving in order and pings the next owner.
- 4
Keep a timeline
The run’s thread records each action with a timestamp, so you have an accurate incident timeline for the review.
- 5
Close out
Mark recovery confirmed, schedule the post-mortem as the final step, and export the run with /tovo export for the write-up.
Incident runbook — FAQ
- Can responders grab tasks without being pre-assigned?
- Yes. Any responder can react 👀 to claim an unassigned step and start it in one tap — useful when you don’t know up front who’ll take what.
- Does Tovo give me an incident timeline?
- The run’s thread records each action with a timestamp, so you get an accurate timeline. Export the full run and tasks to CSV with /tovo export for the post-mortem.
- Is it fast enough to launch during an outage?
- Yes — start from a saved template with /tovo start, or mention @tovo with the steps. Either way the runbook is live in the channel in seconds.
More use cases
Bring your checklists into the conversation.
Set it up once, run it forever. Your team already lives in Slack — your process should too.
Free for 25 runs / month · No per-seat pricing · Live in two minutes