Alerting & escalation
Stage in the incident loop: INGEST · DECIDE · PAGEOn-call alerting and escalation policies that reach the right person.
Alerts arrive over HTTPS, bind to a service, and escalate through a timed policy with a mandatory fallback until someone acknowledges.
- Security25
- Metrics & monitoring24
- Incident & ITSM18
- CI/CD & deployment16
- Uptime & synthetics14
- Logging10
- Cloud platforms9
- APM & tracing7
- Error tracking7
- Email ingest3
- Generic webhook2
135 sources across 11 categories. Security is the largest, which is why security operations gets its own page.
Decide
Who owns this alert?
Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged.
Orchestration rules (organization-wide first, then per service) can reroute an alert, change its severity or priority, suppress it or pause paging before ownership is applied.
CallHeim suggests a severity from a fixed keyword ruleset plus your own resolved incidents, shows the matched terms, and a person applies it. Suggestions never change severity or page anyone. The incident itself keeps the severity its source reported.
See how severity suggestions work →How incident severity levels work →
Page
Escalation that reaches the right person.
An unanswered tier times out and the escalation moves to the next tier, ending at the fallback.
- Escalation policies have up to 8 tiers, each paging a person, a team or a schedule, with per-tier timeouts from 1 to 240 minutes, optional repeats and a mandatory fallback. The whole chain must fit within 24 hours.
- Acknowledging an incident stops the escalation.
- Teams own schedules and link them to escalation policies. Schedules work in any IANA time zone.
Tier 1
The responder on call right now, paged on their own notification order.
- T+0:00
Tier 1
- T+5:00
No acknowledgment → tier 2
- T+10:00
Still nothing → the tier chain repeats
- Repeats exhausted
One fallback target, once
- Acknowledged
The walk stops

Escalation policies: tiers, per-tier timeouts and a mandatory fallback.
Paging
How pages reach your team
Incident pages go out by e-mail on every plan, each with a signed acknowledge link, and sent, delivered and bounced status is recorded on the incident. Pages can also go out by push, text message and phone call.
Acknowledge an incident from the page e-mail or text through a signed, single-use link. It opens a confirmation page that names the incident, and it expires within 24 hours.
- A text page carries the incident severity and title and a signed, single-use acknowledge link.
- A phone call reads out the incident severity and title, and the responder uses the phone keypad to acknowledge, resolve or escalate.
- An organization admin turns SMS and voice on, and each person verifies their own phone number first. Texts and calls go to numbers in the United States and Canada.
- Each person chooses how and when they are paged: ordered steps with delays, quiet hours for lower severities, a low-urgency digest instead of a page, and an organization-wide default for anyone who has not set their own.
- Anyone without paging steps of their own gets the built-in steps. For P1 and P2 incidents, e-mail goes first with push alongside it, a text follows after 5 minutes if nobody has acknowledged, and for P1 a call follows after 10 minutes. Where SMS and voice are off, those steps are sent as e-mail.
- Responders can turn on push notifications on devices where CallHeim is open or installed; a push arrives alongside their other paging steps and opens the incident.
- CallHeim installs on a phone from the browser (Add to Home Screen) and opens full screen, with a phone layout for incidents, on-call and alerts. There is no App Store or Google Play app.
Put a rule you can read between your alerts and your on-call.
Start a 14-day trial, connect one alert source and send yourself a test page.