Pages don't get lost.
People get woken up.
Set timeouts per level, per severity. If nobody responds, the next person gets paged. Simple as that.
Build chains, not hope
Each level is its own config block. Who gets paged, how (Slack DM, email, or both), how long to wait, and what message they see. The person at L2 knows they're L2. Per-service policies mean your checkout service gets a 5-minute timeout with an aggressive path to the engineering lead, while your internal dashboard sits at 30 minutes.
Retry and backup notifications
Ack retry keeps pinging the assigned responder if they haven't acknowledged. Secondary on-call alerts the backup before the formal escalation kicks in. Toggle either one per policy.
Works with your on-call schedule
Escalation policies aren't static contact lists. L1 resolves to whoever is on-call right now, not a hardcoded name. Weekly handoff happens, the chain updates. Someone sets a vacation override, the next page goes to their replacement. You never touch the escalation policy to account for schedule changes.
Frequently asked questions
Stop losing pages at 3 AM.
Free plan includes escalation policies. No credit card.