Incident management and on-call have been rebuilt from the ground up, with schedules, smart routing, ack-aware escalation, and public status pages all built in.
- On-call schedules:Rotations now support layers, cadence, and time-of-day restrictions, with shift overrides and a "Who's on-call now" widget included.
- Smart routing rules:A visual AND/OR/NOT builder lets you route incidents by condition, with a test panel to confirm behavior before you enable it.
- Real escalation:Ack-aware steps retry or advance automatically, responders can set channel preferences across email, SMS, voice, Slack, MS Teams, webhook, Jira, and SNS, and every attempt is logged on the activity timeline.
- Built-in status pages:Incidents can be published straight to a public page, with support for a custom domain and branding.
- Friendly incident IDs:Incidents now get a per-workspace, prefixed ID (INC-1, INC-2, and so on) instead of a global number, shown everywhere from Slack to voice IVR.
- One routing system:Routing Rules now cover both alerts and incidents, and existing Notification Policies migrate automatically with no day-one change.
This should get incidents to the right person faster, with a real audit trail of what happened.
Check out the Incident Management documentation for full details.