Get alerts to the right person.
Build on-call schedules, handle shift swaps and time off, and escalate an alert to the next level when nobody acknowledges it.
- L1Priya R.ack within 5 min
- L2Lena K.after 5 min unacked
- L3Engineering managersafter 15 min
Page the on-call responder, then escalate
Paging follows the schedule and the escalation policy attached to the service. Here is one alert, from the first page to the shift handover.
Manage schedules and shift changes
Rotations, layers, overrides, time off and escalation levels, set per team and attached per service.
Daily, weekly or custom rotation length, per team, in the time zone the responder actually lives in.
schedulesStack a business-hours layer over a follow-the-sun layer. The top layer covering a moment wins it.
layersCover a single evening without rebuilding the rotation, with the change visible to everyone it affects.
overridesDeclare the hours a rotation is meant to cover and see which of them currently have nobody on call.
coverageRegional holiday calendars and booked time off, resolved against the schedule automatically.
time-offLevels with their own delay and their own channels, attached per service rather than per organisation.
escalationHours actually on call and pages actually taken, per person and per period, exportable.
reportsEscalate on the schedule you set.
Each level of an escalation policy has its own delay and its own channels. If a level does not acknowledge in time, the next one is paged, and the timeline records both.
- Per-level delays and channels. Push first, voice at level two, the whole team at level three.
- Acknowledge from anywhere. From the phone, Slack, the dashboard or an SMS reply.
- Catch an exhausted policy. When no level acknowledges, a fallback channel is notified.
- See every hop. Who was paged, on which device, and how long they had to respond.
Set up your first rotation.
Build a schedule, attach an escalation policy, and point your alerts at it. On-Call is available on eligible plans.