On-Call Management Built Into Your Monitoring
Every critical incident should wake exactly one person — the right one. Rotation schedules, one-click overrides, escalation chains that stop on acknowledge, and personal paging methods, all next to the monitors that fire them. No second tool, no webhook glue.
Everything On-Call, in One Place
From “who's on this week?” to “who got paged and when?”
Rotation Schedules
Daily, weekly or every-N-days rotations with layers, time restrictions and per-schedule timezones. Quick-setup presets — weekly, bi-weekly, monthly, weekdays/weekends — build the common patterns in one click.
Live Rotation Preview
The schedule editor shows the next four weeks as you type, so you see every handoff before you save — not after someone got paged.
Month Calendar & Fair Totals
A month view with per-person time on call, percentages and shift counts — shifts are attributed to the period their handoff ends in, so compensation math is fair at month boundaries.
Overrides & Swaps
Click any shift on the calendar to cover it — vacation cover, a swap, an extra pair of hands. Overlap and self-override guards keep the calendar unambiguous, and past overrides can correct the record.
Permanent Replacements
Replace a person in the rotation without reshuffling everyone else's turns — the newcomer takes the same slot, from now or from the next shift.
Escalation Policies
Level 1 pages whoever is on call; if nobody acknowledges in time, level 2 fires, then level 3 — optionally repeating the chain. Acknowledging the incident stops it instantly.
Personal Paging Methods
Escalations reach people through their own methods — email, Telegram, ntfy, Pushover, Gotify or Pushbullet — separate from the team's shared channels.
The Full Notification Flow
One diagram shows the complete path of an incident: which channels fire immediately, how it escalates, who is on call right now and who's next.
Why Run On-Call in WatchFor?
Standalone paging tools mean a second subscription, a second user directory and a webhook bridge that becomes its own point of failure. WatchFor's on-call lives next to the monitors and incidents that trigger it: only multi-location-confirmed critical incidents start an escalation, silenced and maintenance windows never page anyone, and acknowledging in the incident view stops the chain everywhere. One tool, one source of truth.
Only confirmed critical incidents page — warnings never do
Team channels still get every notification alongside escalations
Acknowledge stops the chain — same convention as PagerDuty
Maintenance windows and silences never wake anyone
Escalation survives restarts — the chain is stored, not in memory
Every page, override and change lands in the activity log
Compensation-ready month totals with fair shift attribution
Included with your monitoring — no separate paging bill
How On-Call Works
Four pieces that click together
Build a Rotation
Pick the people and a pattern — weekly, monthly, custom — with a live preview of the next four weeks. The calendar shows who owns every shift.
Define the Escalation
Create a policy: level 1 pages the on-call person, later levels page backups or channels, with wait times between and optional repeats.
Attach It to a Group
Point the policy at a notification group. Every monitor routing alerts through that group now escalates critical incidents through it.
Get Paged, Acknowledge, Done
A confirmed critical incident fires the chain. The on-call engineer is paged on their personal methods, acknowledges, and the escalation stops.
On-Call Use Cases
For teams that put a name on every incident
Small Teams Rotating Fairly
A weekly rotation of 3–6 engineers with month totals and shift counts makes on-call fair — and the compensation math trivial.
Follow-the-Clock Coverage
Weekday/weekend layers and time restrictions split coverage between people or regions without a second schedule.
Escalation Safety Net
When the primary sleeps through a page, the chain moves on — a backup engineer, then a shared channel. Nothing critical dies in a muted phone.
Replacing a Departing Teammate
Swap a person out of the rotation permanently without re-phasing everyone's turns, and cover the transition with a one-click override.
Frequently Asked Questions
Everything you need to know about on-call in WatchFor
From our blog
Guides, deep-dives, and best practices from the WatchFor team
Ready to Put a Name on Every Incident?
Set up a rotation, attach an escalation policy, and let confirmed critical incidents find the right person automatically. Get started in minutes with our free plan — no credit card required.