Pager-Not-On-Phone Incidents

Paged but didn't get the page. The failure modes and the safeguards.

Failure modes

Pager not on phone is the operational risk that the on-call cannot receive their pages. The discipline includes redundancy and testing; the page must reach the on-call reliably or the rotation is theatre.

• Phone DND. Do Not Disturb silences notifications. The on-call's page produces no sound; the paging tool must override DND or other channels must reach the engineer.
• Phone dead or in another room. Battery dies overnight, or the on-call sleeps in a different room. The page rings unanswered; redundancy is the only mitigation that works.
• App not running. The pager app crashed or was force-closed. The page does not reach the app; SMS or phone-call backups handle this case.
• All real, all happen. Each failure mode shows up regularly across teams. The discipline accommodates them rather than hoping they do not occur during the next page.

Safeguards

Multiple notification channels and timed escalation handle the failure modes. The discipline produces redundancy that does not depend on any single device, app, or channel working.

• Multiple notification channels. Phone call, app push, SMS, and email together. If one fails, others succeed; the page reaches the engineer through whichever channel happens to be working.
• Acknowledgement-timeout escalation. If the primary on-call does not acknowledge within the timeout, the page escalates. The backup on-call receives it; coverage is preserved without relying on the primary's vigilance.
• Multiple devices per person. Some teams register multiple devices per engineer (phone, tablet, secondary phone). Redundancy at the device layer in addition to the channel layer.
• Documented escalation. The escalation policy is written down. New on-calls understand the path; the discipline is consistent across rotations.

Test

Testing verifies the safeguards actually work. Without testing, the team's confidence is theoretical; the first time a real page is missed is a bad time to discover the gap.

• Quarterly self-page. The on-call generates a test page each quarter. The team verifies the page reaches them; the safeguards produce the expected behaviour rather than the assumed behaviour.
• Verify every channel. The test exercises phone, app, SMS, and email. Each channel is confirmed independently rather than tested by the path that happens to work first.
• Pager tools support test pages. PagerDuty, OpsGenie, and others ship test functionality. The team uses it; the discipline is supported by the tooling rather than fighting it.
• Test escalation; document failures. Deliberately ignore the test page; verify the backup receives it. Document and remediate when tests fail; the discipline produces continuous improvement rather than annual surprise.

Pager not on phone is one of those operational disciplines that prevents missed pages. Nova AI Ops integrates with paging platforms, surfaces patterns, and supports the team's escalation discipline.