Overview
Coordinate responders, track actions, and mirror announcements to your site/app.
Problem
Scattered incident comms slow recovery and confuse customers.
Solution
One channel per incident with a pinned Canvas runbook, SLA timers, and LiveConnect mirroring of approved announcements.
How it works
Spawn a channel from an incident template (FlowForge), assign roles, enable “needs reply” for action items, and publish approved updates externally via LiveConnect. Chronicle captures the full timeline.
Who is this for
SRE / Ops
Support & Comms
On-call Leads
Expected outcomes
- Faster MTTR with clear ownership
- Transparent, consistent external updates
Key metrics
Mean time to resolve (MTTR)
Baseline
8 hours
Target
3 hours
Announcement latency to site
Baseline
120 seconds
Target
10 seconds
Gallery
Downloads & templates
Security impact
- Incident chat, shared files, announcement text · PII: none; operational data only
Compliance
- SOC2
- Post-mortem retention policy
Availability & next steps
Pro
Enterprise