Escalation Policies
Route incidents to the right people in timed escalation levels.
Alertum escalation policies define exactly who gets notified, through which channel, and in what sequence — so critical incidents never stall on a single responder path.
How it works
Escalation policies define who gets notified, through which channel, and in what sequence. This ensures critical incidents do not stall on a single responder path.
Core capabilities
- ·Multi-level escalation sequencing
- ·User and schedule-based targets
- ·Channel routing across chat, webhook, and fallback
- ·Signal-to-policy scope controls
Typical use cases
- ·Critical outage paging with timed fallback
- ·Tiered response for severity levels
- ·Cross-team handoff automation
Frequently asked questions
How many escalation levels can I configure?
Alertum supports multiple escalation levels per policy, each with its own delay, target (user or on-call schedule), and notification channel.
What happens if the first responder doesn't acknowledge?
If the incident isn't acknowledged within the configured delay, Alertum automatically escalates to the next level in the policy.
Can escalation policies target Slack channels?
Yes — Alertum escalation policies can route notifications to Slack channels, email addresses, webhooks, and on-call schedule targets.
Can I have different escalation policies for different monitors?
Yes — you can assign different escalation policies to different monitors, check groups, or incident types.
Related features