On-call scheduling
Quick answer
Rotas, escalation, notification devices and testing an on call setup before it is needed at 3am.
Key takeaways
- Rotations live on groups and respect schedules for holidays
- Escalation only works when acknowledgement is mandatory
- Gaps appear at handover boundaries, check the calendar
- Users with no notification device are a silent failure mode
Building a rota
On call scheduling sits on groups. Define a rotation with shifts, add members in order, and set the time zone deliberately. Rotations can repeat daily, weekly or on a custom pattern, and holidays come from a schedule.
Escalation
An escalation path defines what happens when nobody acknowledges: notify primary, wait, notify secondary, wait, notify the manager. Set the wait long enough to be realistic and short enough to matter.
Testing
Every on call setup should be proven before it is relied on.
- Use the on call calendar to confirm coverage has no gaps at handover times
- Send a test notification to each device type in use
- Confirm the escalation path with a deliberate unacknowledged test
- Check that a user with no device configured triggers a fallback, not silence
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What triggers the next step in an escalation path?
- A. A closed incident
- B. No acknowledgement within the wait time
- C. A manager approval
- D. A new shift
Show answer
B. No acknowledgement within the wait time
Escalation is driven by lack of acknowledgement.
Where do holidays come from?
- A. sys_user
- B. A schedule record
- C. The rota name
- D. System properties
Show answer
B. A schedule record
Schedules define working time and holidays and are reused across the platform.