FAQ
Straight answers about CallHeim.
How alerting, escalation, paging, migration and pricing work in CallHeim — read straight through, or jump to your topic below.
9 questions
Product
What is CallHeim?
CallHeim is on-call and incident response software. It receives alerts from your monitoring, CI, cloud and security tools, collapses repeats onto one incident, and pages whoever is on call through the owning service’s escalation policy. Your team then works the incident, keeps people informed and reviews it afterward, in one place.
Who is CallHeim for?
SRE and platform teams, IT operations and security teams that run services other people depend on, from a small team sharing one pager up to organizations of 200 seats on the Business plan and larger on Enterprise.
What happens when an alert arrives?
Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. A repeat of an alert that already has an open incident attaches to it instead of paging again; the exact rules, including a 24-hour limit for alerts identified only by their title, are in the next answers. A new incident pages tier 1 of the escalation policy, and acknowledging an incident stops the escalation.
How does on-call escalation work?
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 unanswered tier times out and the escalation moves to the next tier, ending at the fallback. Acknowledging an incident stops the escalation.
How does on-call scheduling work?
Teams with member rosters own schedules and link to escalation policies. Schedules use any IANA time zone. Schedules support layers, an override that sits above the layers, layer restrictions to weekdays, business hours or nights, follow-the-sun templates, time off, shift-swap requests with approval, and coverage-gap detection with suggested fills. Subscribe to any schedule from a calendar app: a private iCal link shows the next 90 days of shifts, including overrides, and a schedule editor can reset the link at any time.
How are alerts grouped and deduplicated?
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. 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.
Does CallHeim use AI?
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. 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. CallHeim ships no generative assistant and no autonomous agents.
How do I get help?
Open a request from Help Center in the app and choose a priority from Low to Urgent. Replies and status changes arrive by e-mail, and you answer in Help Center. Help Center is open during the free trial too, so you can ask questions while you evaluate.
Who runs CallHeim?
CallHeim is a product of Packysnappy, which operates the service. The application runs in Amazon Web Services in us-east-1.
6 questions
Paging & integrations
How does CallHeim notify the person on call?
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. 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.
Can CallHeim page by text message or phone call?
Yes. 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. Message and data rates may apply.
Can I use CallHeim on my phone?
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.
Which monitoring tools does CallHeim integrate with?
CallHeim lists 135 alert sources across 11 categories, including Datadog, Prometheus Alertmanager, Grafana, Sentry, AWS CloudWatch, New Relic and ServiceNow, each with its own setup guide. 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.
Is there an API?
Yes, on the Pro plan and above: REST endpoints list and get incidents and acknowledge, resolve or close them, with scoped API keys and OAuth 2.0 client-credentials tokens.
Does CallHeim work with Slack or Microsoft Teams?
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. Post incident notifications to a Microsoft Teams channel as a card with an Acknowledge button.
2 questions
Migration
Can I migrate from PagerDuty?
Yes. 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. An organization admin runs the importer from the organization settings in the app, with a read-only token from PagerDuty or Opsgenie. CallHeim stores the imported data in AWS us-east-1, whatever the region of the old account. The importer reads users, teams, services, schedules with their layers, restrictions and overrides, escalation policies with every tier target, 90 days of incident history, maintenance windows and PagerDuty e-mail integrations. Notification preferences and integration keys are not carried over: CallHeim’s built-in paging steps apply until each person sets their own, and each sender gets a new CallHeim URL. You can also run both platforms in parallel while you move: CallHeim accepts PagerDuty Events API v1 and v2 requests. Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused.
Can I migrate from Opsgenie?
Yes. Atlassian ends support for Opsgenie on 5 April 2027, so plan the move well before then. 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. CallHeim also accepts Opsgenie outgoing webhooks, so alerts can be forwarded to both platforms during a parallel run.
3 questions
Pricing
How does pricing work?
Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated. Alerts are not metered or billed. Seat caps are the only published plan limits. Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; audit-log export, an IP allowlist for administrative changes, private status pages and SCIM user provisioning on Business and above; email-to-alert (per-organization inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.
Is there a free trial?
Yes. Every new organization starts with a 14-day trial for up to 5 seats, and no card is required. When the trial ends you cannot add users until a paid plan is in place; existing users keep working and webhook alerts keep paging.
How do I buy a paid plan?
Paid plans are invoiced and activated directly by the CallHeim team; ask from Billing in the app. Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated.
6 questions
Security & data
Where is data processed?
Application data is stored in AWS us-east-1. Page e-mail is sent through Resend and contains the recipient address, the incident’s severity, number and title, an acknowledge link and a link to the incident. Phone-number verification codes are sent through Twilio. If your organization turns on SMS and voice, those texts and calls also pass through Twilio: a text carries the incident severity, title and a one-time acknowledge link, and a call reads out the severity and title. If a responder turns on push notifications, a short notification with the incident title and links passes through their browser vendor’s push service. If your organization connects Slack or Microsoft Teams, incident notifications also go to the channels you configure there. The sign-in page at app.callheim.com loads its fonts from Google Fonts. No incident data is sent to an external language model.
Is my data separated from other customers?
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. Your organization and role are assigned server-side and stamped on your token; users cannot edit them.
What security controls are in place?
E-mail and password sign-in with optional authenticator-app (TOTP) two-factor authentication. Data is encrypted at rest with AWS encryption (DynamoDB, S3 and SQS) and in transit with TLS. 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.
Does CallHeim hold SOC 2 or ISO 27001?
CallHeim does not currently hold SOC 2, ISO 27001 or other third-party security certifications. The security page describes the controls that are in place.
How do I send a security questionnaire or request a DPA?
Open a request from Help Center in the app with the Question category, and attach your questionnaire or describe what you need. If you do not have an account yet, start the free trial first; it needs no card. The security page and the list of service providers answer the questions reviewers ask most.
Can I export my data?
Analytics reports export as CSV or JSON on every plan. The audit log exports as CSV or JSON on Business and above, and the file goes straight to your device. The REST incident API lists and gets incidents on Pro and above.
Not answered here? See everything CallHeim includes, the pricing page, the security page or the migration guide.
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.