What it is (plain English)
Schedules, rotations, and escalation rules that answer one question reliably: who gets contacted right now when a critical system breaks? When an incident lands, ServiceNow works out who is on shift, notifies them, and automatically escalates to the next person if nobody acknowledges.
Problems it solves
- After-hours outages sitting untouched until morning because "the ticket was assigned to the team."
- On-call rotations managed in a spreadsheet nobody keeps current.
- No escalation path — if the first person doesn't answer, nothing happens.
- No record of who was contacted, when, and whether they responded.
What must exist first
Incident Management — on-call exists to route incidents; the groups it schedules are the same groups incidents are assigned to.
What the customer needs to provide
- Which teams actually need on-call coverage (usually the ones supporting business-critical systems, not everyone).
- Real rotation details per team: shift hours, rotation frequency, and how time-off gets covered.
- Escalation expectations: how long before it goes to the next person, and who is the last resort.
- How people want to be woken up: push notification, SMS, phone call (SMS/voice needs the Notify capability and a provisioned phone number).
- A group manager per team to own the schedule day-to-day.
Where it can go next
Pairs naturally with Major Incident Management for crisis response staffing, and with monitoring integrations via Integration Foundation so automated alerts page the on-call directly. Escalation logs feed reporting on response performance.