On-call & incident response
When production breaks, CallHeim gets the right person on it.
CallHeim is on-call and incident response software for engineering, IT and security teams. Alerts from your monitoring tools become incidents, repeats attach instead of paging again, and the owning service’s escalation policy pages whoever is on call, tier by tier, until someone acknowledges.
14-day trial · up to 5 seats · no card required
From $9 per user per month.
Moving off Opsgenie before it ends on 5 April 2027, or off PagerDuty? Run CallHeim next to your current tool first, then import your setup after a dry run. From Opsgenie · From PagerDuty
Incident pages go out by e-mail, push, text message and phone call, with a signed acknowledge link. See how paging works.
Signals
- Datadog
- Prometheus Alertmanager
- Sentry
- AWS CloudWatch Alarm (via SNS)
- Grafana
- Pingdom
+ 129 more sources
- fingerprint
- a91f…3c
- collapsed
- 11 duplicates
- title match
- 0.67 ≥ 0.6
- severity suggested
- P1
One incident
[P1] checkout-api: payment authorization timeout
service checkout-api · 12 alerts · 1 page
Maya Chen
tier 1 · email · 02:14:06
Illustrative example · twelve alerts, one incident, one page
Start where you are
Built for teams responsible for critical systems
It already speaks to what you run.
SRE and platform teams
You own the pager for services other teams depend on, and your monitoring already knows before you do.
On-call for SRE and platform teams →IT operations
Your alerts arrive from an ITSM tool and an inbox as often as from a monitoring agent, and on-call still has to work.
On-call for IT operations →Security operations
Detections need routing and escalation without their contents being sent anywhere to be scored.
On-call for security operations →
The problem
A storm of alerts is not the same as a storm of problems.
Duplicates from the same monitor. A threshold flapping either side of its boundary. Nobody sure who owns it, because ownership never made it onto the alert. The pager stops meaning anything long before the failure is fixed — and the fix was never to send fewer alerts, it was to collapse the ones describing the same thing.
- P1payment authorization timeout
checkout-api · 12 alerts · one incident · one page
- P2elevated 504 rate
psp-gateway · 5 alerts · one incident · one page
- P3retry queue depth rising
checkout-web · 3 alerts · one incident · one page
How CallHeim works
One loop, seven stages, and a rule you can read at every one.
Ingest, reduce, decide, page, respond, resolve, learn: each stage does one job and follows a rule you can read.
- 01
INGEST
Alerts arrive over HTTPS from your monitoring, CI and cloud tools.
- 02
REDUCE
Repeats attach to their open incident; flapping and related alerts group by published rules.
- 03
DECIDE
The source’s service picks the escalation policy. CallHeim suggests a severity; a person applies it.
- 04
PAGE
Tiers and timeouts advance to a mandatory fallback until someone acknowledges. Pages go out by e-mail, push, text message and phone call.
- 05
RESPOND
Acknowledge, comment and work the incident on a timeline with no edit or delete.
- 06
RESOLVE
Triggered → Acknowledged → Resolved → Closed, with a public status page your team updates.
- 07
LEARN
MTTA and MTTR from each incident’s own timestamps, plus a published on-call fatigue score.
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.
Why it's different
Built so every decision can be checked.
Explainable alert handling
CallHeim’s alert handling is rule-based and deterministic: given the same alert, settings and state, it makes the same decision.
The rules behind the noise handling are published. A repeat attaches to its open incident, within 24 hours of the incident opening unless the sender supplies its own dedup key. A series that changes state 4 times in 600 seconds is treated as flapping. Near-identical titles from the same source and service group together at a similarity of 0.6. Title grouping can be switched off for your organization.
Suggestions from rules, not an outside model
No incident data is sent to an external language model, and CallHeim does not train any model on your incidents. Severity suggestions and related-incident insights are rule-based code running inside CallHeim’s own AWS environment.
Escalation that keeps going
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.
An incident record that stays accurate
Lifecycle changes (acknowledge, resolve, close), comments, escalation steps and suppressions are written to the incident timeline as they happen, and the timeline has no edit or delete in the product.
Responders act on incidents; managers and stakeholders have read-only access.
How an escalation policy walks its tiers
Incident opens
#2041 · P1 suggested · checkout-api
The service’s escalation policy, "Payments — Business Hours", starts paging.
Tier 1 · Maya Chen
email · 5m to answer
The person this tier pages. A tier can also target a team or a schedule.
↓ wait 5 minutes · no answer
Tier 2 · Daniel Okafor
email · 5m to answer
The person this tier pages. A tier can also target a team or a schedule.
↓ wait 5 minutes · no answer
Tier 3 · Fallback: Engineering manager
email · no timeout, this is the last tier
The mandatory fallback: one target, paged once the last tier times out.
Acknowledged by Maya Chen
at 02:16:20 · MTTA 2m 14s
Acknowledgment stops the escalation, so tiers 2 and 3 are never paged.
What runs on its own, and what waits for a person
Inside your CallHeim organization
Severity classification
Suggests — a person applies it
Suggests a severity from the alert’s wording and your own resolved incidents, and shows the terms that matched. A person decides whether to apply it.
Related-incident insights
Suggests — a person applies it
Lists open incidents that look related to the one you are working on, so a responder can spot a shared cause sooner. Pro and above.
On-call fatigue
Suggests — a person applies it
Shows who has carried the most pages, night interruptions and off-hours work over the last 14 days, so you can rebalance before it wears people down.
Rotation assist
Suggests — a person applies it
Proposes a fairer rotation from each person’s recent paging load. Nothing changes until you approve it.
Noise reduction
Acts automatically
Attaches repeats to the incident that is already open, collapses flapping alerts and groups similar titles, so a burst of alerts does not become a burst of pages.
Inside the console
What your team works with.

Escalation policies: tiers, per-tier timeouts and a mandatory fallback.

On-call schedule: rotation layers and the final schedule they produce.
Incident response
Understand it, own it, coordinate it, close it.
An incident is a record with a timeline, an owner and a state, written as it happens — not a notification that disappears once it is dismissed.
Triggered → Acknowledged
2m 14sMTTA
Paged, and somebody took it.
Acknowledged → Resolved
29m 32sMTTR
Comments, timeline, and the fix.
- 02:14:06
Incident created from 12 alerts · P1 · Triggered
What happened, assembled from every alert that described it
- 02:14:07
Escalation started · policy "Payments — Business Hours" tier 1
Who owns it, set by the Service rather than by whoever is watching
- 02:14:08
Paged Maya Chen · email
The page itself, on the channel that reaches them
- 02:16:20
Acknowledged by Maya Chen
Acknowledged — the escalation stops here
- 02:20:48
Comment · psp-gateway connection pool at its limit
Coordination: comments written to the timeline as they happen
- 02:43:38
Resolved · psp-gateway connection pool raised
Resolved: MTTA and MTTR come from these timestamps
The rest of the platform
Alerting & escalation
Alerts arrive over HTTPS from your monitoring tools and route to the owning service’s escalation policy: up to 8 tiers, per-tier timeouts and a mandatory fallback.
Alerting & escalation →Noise reduction
Repeats attach to the open incident, flapping checks stop re-paging, and near-identical alerts group, by rules you can read.
Noise reduction →Incident intelligence
A severity suggestion with the matched terms shown, and related-incident insights on Pro and above. A person applies every suggestion.
Incident intelligence →On-call scheduling
Layers, overrides, time off, approved shift swaps, coverage gaps flagged ahead of time and a calendar feed, in any time zone.
On-call scheduling →Incident response
A timeline with no edit or delete, runbooks, response plays and postmortems, a public status page and MTTA/MTTR analytics.
Incident response →
Integrations
Everything you monitor with, arriving at one place.
135 alert sources on every plan, from metrics and APM to security, ITSM, CI and e-mail.
Switching from PagerDuty or Opsgenie
A way off, on your own schedule.
Atlassian stopped selling Opsgenie on 4 June 2025. Opsgenie reaches end of support on 5 April 2027: access is shut off and customer data that has not been moved is deleted, so move or export what you need before then. Atlassian’s Opsgenie licensing page, checked 2026-10-19.
Run in parallel during a move: CallHeim receives PagerDuty Events API v1 and v2 requests and Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast (now SolarWinds Incident Response), Zenduty (now Xurrent IMR) and Grafana OnCall.
The importer reads your PagerDuty or Opsgenie configuration from a US or EU account, and a dry run shows you the result before anything is written to your organization.
Security
Organization isolation, audit and recovery, built in.
- Reads and writes are scoped by the API authorization rule to the caller’s organization, or to the caller’s own user for personal records, and custom operations enforce the organization in server-side code. CallHeim is multi-tenant on a shared database.
- The audit log is append-only: no client can modify or delete an entry.
- Point-in-time recovery (35-day window) and deletion protection are enabled on CallHeim’s production data tables.
- Data is encrypted at rest with AWS encryption (DynamoDB, S3 and SQS) and in transit with TLS.
Pricing
Priced per seat, from $9 a month.
Starter, Pro and Business scale by seat count; Enterprise is negotiated. A 14-day trial, no card required.
Starter
$9per user / month
list price · up to 10 seats
For a small team that owns its own pager.
Pro
$15per user / month
list price · up to 50 seats
For teams that want API access and related-incident insights.
Business
$29per user / month
list price · up to 200 seats
For a growing organization: email-to-alert, audit-log export, an IP allowlist for administrative changes and private status pages.
Paid plans are invoiced and activated directly by the CallHeim team; ask from Billing in the app.
Put a rule you can read between your alerts and your on-call.
Start a 14-day trial, connect one source, and watch it collapse into one page — no card required.
14-day trial · up to 5 seats · no card required