First look: behind the scenes building an AI incident responder.
First look: behind the scenes building an AI incident responder.
January 28, 2025
We’ve been working hard on some smaller improvements and polish across our On-call product this week. You can now drag-and-drop to override a schedule in the dashboard, use workflows to notify people and teams when a shift changes over, manage pending schedule changes, export escalation paths directly to Terraform with a new visual editor, and more!
Back in July we added “drag to override” in our mobile app: now you can do the same from the dashboard! In the timeline view, drag across a rota to select the times to override for, tell us who’s taking the shift and you’re done ✨
While you’ve been able to manage escalation paths in Terraform for a while now, writing the configuration can be tricky to get right. Now you can build an escalation path in our visual editor and we’ll write the Terraform code for you in one click.
You can now run a workflow when the person on-call changes. This lets you post handover reminders in the right channel, or DM the person going on- or off-call 👇
Sometimes you know an alert always indicates there’s an incident, without needing to triage it first. In alert routes, you can now choose whether to create a triage incident, or dive right in — or choose based on an attribute of the alert!
If your team only handles issues in-hours, or issues above a certain priority, you can now ignore escalations that don’t match those conditions with a ‘do nothing’ node in your escalation path.
Escalations that reach this will be cancelled as soon as they reach the node.
When you’re making changes to a schedule, like onboarding a new on-caller, you’ll probably want to leave your current rotation undisturbed: this is why we shipped upcoming changes to schedules last year.
You’ll now be able to view the configuration for those changes, edit them, or cancel them, straight from the schedule editor.