Alerting & escalation

Stage in the incident loop: INGEST · DECIDE · PAGE

On-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.

Ingest

Alerts from the tools you already run

Send alerts to your CallHeim integration URL over HTTPS, in CallHeim’s alert format or through a field mapping you define. CallHeim queues each accepted alert durably and processes it asynchronously; acceptance is an HTTP 202.

An accepted alert is normalized to one record with five severity levels (P1 to P5) and a stable fingerprint.

A repeat of the same alert attaches to the incident that is still open for it in the same service, triggered or acknowledged, with no new incident and no new page. When the sender supplies its own dedup key (a PagerDuty dedup_key, an Opsgenie alias, a Datadog alert id, an Alertmanager fingerprint, or a dedupKey that is more than the alert title), this holds however late the repeat arrives. When the identity comes from the e-mail subject or the alert title, the repeat attaches only if the incident was triggered in the last 24 hours; after that it opens a new incident and pages.

A repeat at P1 or P2 is not folded into an open P3, P4 or P5 incident: it opens a new incident and pages. Once an incident is resolved or closed, the next repeat opens a new incident.

Where your tool sends a recovery, CallHeim resolves the incident; an incident that grouped several alerts resolves when the last one clears.

PagerDuty Events API v1 and v2 request bodies are also accepted, for a parallel run during a move off PagerDuty. Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused. Migrate from PagerDuty →

Browse all 135 alert integrations →

How alerts are accepted

address
Your integration URL, one per source.
accept
An HTTP 202 once the alert is queued durably. It is processed asynchronously, not handled inline.
format
CallHeim’s own alert format, or a field mapping you define for whatever your tool sends.
signing
CallHeim verifies an HMAC-SHA256 signature on each source’s requests once you enable signing on that integration (the sending tool must be able to sign).

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.

See how on-call scheduling works →

Example escalation policy
T+0:00

Tier 1

The responder on call right now, paged on their own notification order.

  1. T+0:00

    Tier 1

  2. T+5:00

    No acknowledgment → tier 2

  3. T+10:00

    Still nothing → the tier chain repeats

  4. Repeats exhausted

    One fallback target, once

  5. Acknowledged

    The walk stops

A list of escalation policies showing their tiers, fallback target and repeat count
Escalation policy

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.
CallHeim

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.