Overview

What CallHeim includes.

Paging, alert handling, escalation, on-call scheduling and incident response, grouped on one page. Plan-specific features are marked; the full plan comparison is on the pricing page.

Paging channels

  • E-mail paging

    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.

  • Acknowledge from the page e-mail

    A signed, single-use link in the page e-mail opens a confirmation page; one press acknowledges the incident and stops the escalation. The link expires within 24 hours.

  • SMS paging

    Incident pages by text message, with the severity, the title and a signed acknowledge link. An organization admin turns SMS and voice on, and each person verifies their own mobile number first. Texts go to numbers in the United States and Canada.

  • Phone-call paging

    A phone call reads out the incident severity and title, and the responder uses the keypad to acknowledge, resolve or escalate. An organization admin turns SMS and voice on, and each person verifies their own phone number first. Calls go to numbers in the United States and Canada.

  • Push notifications

    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.

  • Installable app

    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.

  • Personal paging rules

    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. Without either, the built-in steps page by e-mail first, then by text and call for urgent incidents.

Alert ingest and noise handling

  • HTTPS alert ingest

    Send alerts to your integration URL over HTTPS, in the CallHeim alert format or through a field mapping you define. Accepted alerts are queued durably and processed asynchronously.

  • Signed requests (HMAC-SHA256)

    Require an HMAC-SHA256 signature on an integration once you enable signing (the sending tool must be able to sign).

  • Duplicate collapse

    A repeat of the same alert attaches to its open incident in the same service with no new page: at any age when the sender supplies its own dedup key, and within 24 hours of the incident being triggered when the identity is only the e-mail subject or alert title. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages, and once an incident is resolved or closed the next repeat opens a new one.

  • Maintenance windows

    One-time maintenance windows suppress new alerts for a service, a team or the whole organization; recovery events are exempt.

  • Noise rules

    Write your own rules to suppress, group or hold alerts until a count is reached. Recoveries and acknowledgments from your tools are never suppressed.

  • Inbound alert e-mail address

    On the Trial, Business and Enterprise plans each organization gets inbound alert e-mail addresses; mail sent to one becomes an alert, and e-mail rules decide what opens or resolves an incident. Starter and Pro do not include it.

Escalation and incident response

  • Escalation policies

    Up to 8 tiers with per-tier timeouts from 1 to 240 minutes and a mandatory fallback. An unanswered tier times out and advances.

  • On-call schedules

    Layers, overrides, weekday and hours restrictions, follow-the-sun templates, time off, approved shift swaps and coverage-gap detection for the next 7 days, in any IANA time zone, with a private calendar feed per schedule.

  • Incident lifecycle and timeline

    Four states and five severities, role-gated actions, and a timeline with no edit or delete in the product.

  • Runbooks, response plays and postmortems

    Assign incident roles and post status updates, attach runbooks with checklists to services, run prepared response plays from the incident, and write postmortems with owned action items.

  • Public status page

    Every organization has a public status page, and your team posts the updates. Additional pages for different audiences show only the services you add to them, with their posts and scheduled maintenance, and visitors can subscribe by e-mail or with a Slack webhook.

  • MTTA and MTTR analytics

    MTTA and MTTR (mean, p50, p90) from each incident’s own timestamps, plus alert-volume heatmaps and on-call load and fairness reports, on every plan. Reports export as CSV or JSON.

  • Severity suggestions

    A suggested severity with the matched terms shown; a person applies it. Suggestions never change severity or page anyone.

Integrations

  • Slack

    Connect your own Slack app: CallHeim posts incident notifications to a channel, people can acknowledge or resolve from the message, and /oncall shows who is on call. Slack is a notification channel, not a paging step.

  • Microsoft Teams

    Post incident notifications to a Microsoft Teams channel as a card with an Acknowledge button.

  • Alert sources

    A catalog of alert sources on every plan, each with a payload mapping for that tool’s webhook format and its own setup page.

Migration

  • PagerDuty and Opsgenie import

    Import from PagerDuty or Opsgenie (a US or EU account): users, teams, services, schedules, escalation policies, maintenance windows and 90 days of incident history. Review a dry run first; Undo removes only what a finished import created and nobody has changed since.

  • Parallel run by alert forwarding

    CallHeim accepts PagerDuty Events API v1 and v2 requests and Opsgenie outgoing webhooks, so alerts can be forwarded to both platforms during a move. Each sender needs a CallHeim URL and key.

Sign-in and access

  • Sign-in and two-factor

    E-mail and password sign-in with optional authenticator-app (TOTP) two-factor authentication.

  • Roles and permissions

    Five built-in roles with permission checks on actions, plus per-organization overrides and custom roles. Read visibility is organization-wide.

  • Directory provisioning (SCIM)

    On the Business and Enterprise plans, your identity provider can create, update and deactivate members through SCIM 2.0. Roles are set in CallHeim, not by the identity provider.

Platform

  • REST incident API

    On the Pro plan and above: REST endpoints to list, get, acknowledge, resolve and close incidents, with scoped API keys and OAuth 2.0 client-credentials tokens.

  • Data region

    Application data is stored in AWS us-east-1.

Trial and billing

  • 14-day trial

    14-day trial with up to 5 seats. No card required.

Next steps

Compare seat limits and what is tied to plan on pricing, or read the full data-handling and access picture on security.

CallHeim

See how it fits your on-call.

Start a 14-day trial, connect one alert source and send yourself a test page.