Priority Routing
Approvals and alerts can break quiet hours. Everything else can’t.
Inside Priority Routing
Priority routing lets policy — not guesswork — decide what’s urgent enough to interrupt. Typed alert and approval messages can be configured to break quiet hours; routine updates never do.
Policy decides, not the sender
Whether a message can interrupt you is a type-and-policy rule, not left to whoever is writing it.
Real urgency gets through
A genuine sev-1 alert or a pending approval reaches you even during quiet hours, by design.
Working-hours defaults
Non-urgent messages default to arriving when the recipient is actually working, across timezones.
The detail
What can interrupt quiet hours is a policy decision, not a judgment call left to whoever is sending the message. Typed alert and approval messages can be configured to break through by policy; ordinary updates default to arriving during the recipient’s working hours instead, across timezones.
Keep exploring
Where this connects — in the product and in the rest of the catalog.
See Priority Routing on your own workspace
Bring a real channel. In fifteen minutes we’ll show you priority routing working on your team’s actual conversations, not a demo script.