Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

← All emails

No. 6 · May 7, 2026 · Escalation

Default escalation policy isn't built for critical incidents

There's a faster, better setup for these.

For low-priority incidents, a default escalation policy works fine.

Something like:

Incident triggers ↓ After 5 mins, alert on-call responder ↓ After 30 mins, alert backup responder ↓ After 60 mins, alert engineering manager

But critical incidents are different. They can't wait that long.

Also, they need a different first step: a single phone call to the entire engineering team, all at once.

This way, everyone gets paged at the same time and the whole team is on the line immediately after the incident triggers.

That's the fundamental idea behind an escalation policy for critical incidents.

Our guide covers the full setup: wait times, when to trigger it, and more.

See how to set it up →

Get the next one in your inbox

A weekly email for engineers who carry the pager.

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh