No. 13 · Jul 31, 2026 · Routing
Severity alone isn't enough to route incidents.
You need one more signal.
A webhook delivery failure for one customer is a low-severity incident. Your routing setup probably sends a Slack message and moves on.
But what if that customer is your largest enterprise account?
The severity (aka blast radius) is still low, but the priority is high. Just a Slack message isn't enough. You need an immediate phone call.
But if your routing only looks at severity, you don't get that phone call. By morning, the customer has been affected for hours, and that delay can cost you the account.
That's why you need to build priority into your routing setup alongside severity. It's not just about how many users are affected, but how fast you need to respond.
We built the severity-priority matrix exactly for that. Every combination maps to a defined response, so nothing slips through.