Escalation chains: how they work and why they matter

Sending an alert is easy. Making sure it gets seen is the hard part — people step away from their desks, mute notifications, or are simply heads-down on something else.

What an escalation chain looks like

An escalation chain is an ordered list of steps attached to a rule. Each step names a teammate, a timeout in minutes, and optionally a different delivery channel. If the alert from one step isn't acknowledged within its timeout, the next step fires automatically.

For example: an "SLA about to breach" alert might go to the assigned agent first. If they don't acknowledge within 10 minutes, it escalates to their team lead. If that's not acknowledged within another 15 minutes, it posts to a shared #support-urgent channel.

Why "acknowledge" matters

Every alert delivered to Slack includes Acknowledge and Dismiss buttons. Acknowledging an alert stops the escalation chain — it's a signal that a human has seen it and is on it. Without this step, escalation chains would just be a louder way of spamming people.

Designing a good chain

• Start with the person closest to the work — usually the assigned agent.
• Keep early timeouts short for high-severity triggers like SLA breaches.
• End with a shared channel as a safety net, not a first resort.
• Use longer timeouts for lower-severity triggers like conversation idle.

Escalation chains run on a one-minute cron with row-level locking, so even with multiple workers, each step fires exactly once.