Escalation policies

If the first responder misses it, the next one hears it

Ordered levels, per-level targets, and timeouts that respect business hours. An incident keeps climbing the ladder until someone acknowledges it.

Ordered levels

Level 0 fires the moment an incident opens. No acknowledgement in time, and the next level fires. Repeat until someone responds.

Channels or schedules

Each level targets channels directly, or an on-call schedule that resolves to whoever is on call right now.

Business-hours aware

Give a level a time window. Outside it, the level is skipped and the next one fires immediately.

Acknowledge stops the chain

The moment an incident is acknowledged, every pending escalation cancels itself.

Routing

Climbs until
someone answers.

Define your levels, point each one at a channel or a schedule, and set how long to wait before escalating. Acknowledgement stops it cold.

  1. Define your levels

    An ordered list of levels. Level 0 fires the instant an incident opens.

  2. Point each level somewhere

    Target a channel directly, or a schedule that always resolves to the current on-call person.

  3. Set a timeout

    No acknowledgement within the window, and the next level fires automatically.

  4. Make it time-aware

    Scope a level to business hours so a 2am page skips straight to whoever is actually awake.