On-call

One page, to the person actually on call.

Rotations that generate themselves, escalation that stops when someone acknowledges, and a delivery log that answers “did the page go out?” with a record instead of a shrug.

Request early access

Escalation policy · payments

Level 0On-call engineer · from the payments rotationemail · push

+5 minLevel 1 · platform-oncall groupemail · push · phone

+15 minLevel 2 · engineering leadsphone · Slack channel

Publicstatus.yourdomain.com · degraded, updatingauto

Schedules and rotations

Built around the fact that a rota on paper and who is genuinely reachable right now are two different things.

Generated rotations: Give it the people and an interval in days and it produces the assignments, rather than making someone fill a calendar by hand.
Handoff time and timezone: Each schedule carries its own timezone and a handoff time, so a rotation changes hands at a sensible local hour instead of at UTC midnight.
Who is on call: Queryable for a schedule, for a group, or for yourself — so the answer is one lookup rather than an archaeology exercise in a spreadsheet.
My schedule: Every engineer can see their own upcoming shifts without needing access to everyone else's.

Escalation

Levels with their own delays and their own channels. Acknowledgement is what stops it — not a timeout.

Multi-level policies: Numbered levels, each with its own delay before it fires and its own set of targets.
Per-level channels: Email, mobile push and phone are chosen per level, so level 0 can be quiet and level 2 can be loud.
Groups as targets: A level can escalate to a group rather than an individual, which is what you want at two in the morning.
Stops on acknowledge: Acknowledging the incident halts the ladder. Nothing further fires.

Real life

The features that exist because rotas meet holidays, illness and timezones.

Overrides: Cover someone else's shift for a defined window without editing the underlying rotation.
Shift swaps: Request a swap, and have it approved or rejected by the other party — with pending requests visible to both sides rather than negotiated in a DM.
Pending queue: Outstanding swap requests are listed, so nothing sits unanswered until the shift starts.

Proof of delivery

The part most on-call tools leave you guessing about.

Delivery log: Every notification sent, with its channel, its escalation level and its delivery status.
Channel coverage: Email, SMS, phone, mobile push, Slack, Discord, Telegram, PagerDuty and webhooks.
Keep PagerDuty if you want: It is a supported alert channel. On-call here is included rather than billed separately, so running both costs you nothing extra.

Find out how much of your paging was noise.

Connect one cluster and watch a week of alerts sort themselves into the handful that actually mattered.

Request early access