On-call

On-call is the practice of always having a designated responder reachable to handle incidents. A rotation shares this duty across a team over time — daily or weekly shifts — so no single person carries the pager indefinitely. Paired with an escalation policy, it guarantees that an alert always reaches someone able to act, at any hour.

Why it matters: detection is worthless if no one responds. On-call is the human half of incident response, and it is what keeps a 3 a.m. outage from waiting until morning. A well-run rotation also distributes the burden fairly, which protects the team from burnout and keeps response quality high over the long term.

A common misconception is that on-call is just a phone number to call. In practice it depends on an escalation policy — automatically paging a backup if the primary doesn't acknowledge within a set time — and on alert quality. On-call only works when alerts are fast and trustworthy; flood responders with false positives and they tune out, which lengthens acknowledgement time and defeats the entire purpose.

Sustainable on-call is as much an organizational design problem as a technical one: reasonable rotation length, clear handoffs, follow-the-sun coverage where possible, compensation or time-off for shifts, and ruthless reduction of noisy alerts so every page genuinely deserves a response.