For IT operations and ITSM
IT on-call and escalation that speaks ITSM.
Some alerts only arrive as e-mail, and some come from a service desk. CallHeim takes both.
Your systems
Service desks, monitoring and the mail gateway.
Each alert source has a payload mapping for that tool’s webhook format and its own setup guide.
All incident and ITSM sources →
ServiceNow, Freshservice, Zendesk and similar tools connect as inbound alert sources. Connections are inbound: an event in your ITSM tool raises a CallHeim alert.
The IT-shaped parts
Ownership that maps to how you are organized.
Business services
Roll technical services up into the thing the business actually names — “payroll”, “the warehouse system” — with owners and tiers. Dependency views show downstream impact for each business service.
Maintenance windows
Maintenance windows suppress new alerts for a service, a team or the whole organization, and recovery events are exempt.
Status pages
Every organization has a public status page on app.callheim.com, and your team posts the updates.
Escalation that reaches people
Alerts route through your escalation policy to the on-call for that service. 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.
Access
Roles, two-factor and an audit trail.
- Five built-in roles with granular permissions, plus per-organization permission overrides and custom roles.
- E-mail and password sign-in with optional authenticator-app (TOTP) two-factor authentication.
- The audit log is append-only: no client can modify or delete an entry.
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.