Incident response

Stage in the incident loop: RESPOND · RESOLVE · LEARN

Incident response workflow: run the incident, then measure what happened.

Four incident states, a timeline with no edit or delete, and MTTA and MTTR calculated from each incident’s own timestamps.

How it works

Four incident states.

Four incident states (Triggered, Acknowledged, Resolved, Closed) and five severities (P1 to P5). A resolved incident can be reopened; a closed incident is final.

  1. 01Triggered

    Created by the alert pipeline, or declared by a person. Escalation starts here.

  2. 02Acknowledged

    Somebody has it. Every remaining escalation tier and timer stops.

  3. 03Resolved

    The problem is over. It can still be reopened, back to Triggered.

  4. 04Closed

    Final. A closed incident cannot be reopened.

Severities are P1 through P5. An incident opened by an alert takes the source’s own severity. CallHeim adds a suggested severity for a person to apply.

Incidents opened by an alert get a sequential per-organization number, shown as #N.

Roles

Role-gated, not a free-for-all.

Responders act on incidents; managers and stakeholders have read-only access.

Managers and stakeholders can follow every incident and read its timeline.

Timeline & audit

Two different records, both append-only.

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.

The audit log records incident acknowledge and resolve, user invitations and deactivations, role changes, forced sign-out and organization settings changes. Configuration changes to schedules, escalation policies, services, teams and integrations are recorded with before and after values.

Respond

Run the response from the incident.

Roles and status updates

Assign incident roles and post templated status updates on each incident.

Runbooks

Attach runbooks with checklists to services; responders see them on the incident and tick items off as they go.

Response plays

Run a prepared response play from the incident page.

Postmortems

Write postmortems with owned action items on the incident, and keep them in a shared library.

Read the incident response process guide →

Keeping people outside the incident informed

A public status page for your organization.

Every organization has a public status page on app.callheim.com, and your team posts the updates.

Publish additional status pages for different audiences. Each page shows only the services you add to it, with their posts and scheduled maintenance, so a page made for one customer never shows another customer’s updates. Visitors can subscribe by e-mail or with a Slack webhook.

Learn

Then measure what happened, on every plan.

Core analytics (MTTA, MTTR, alert volume by source, escalation rate and period-over-period comparison, over windows of 7 to 365 days) are not gated by plan; related-incident and responder insights start at Pro.

MTTA and MTTR (mean, p50, p90) are computed from the incident’s own timestamps; reopened incidents are measured per response, merged duplicates are excluded and still-open incidents are flagged.

Alert-volume heatmaps and on-call load and fairness reports sit alongside MTTA and MTTR, and any report exports as CSV or JSON.

See how MTTA and MTTR are calculated →

Example incident

Triggered → Acknowledged
2m 14s

MTTA

Triggered → Resolved
29m 32s

MTTR

  1. 02:14:06Incident created from 12 alerts · P1 · Triggered
  2. 02:14:08Paged the on-call responder by e-mail
  3. 02:16:20Acknowledged
  4. 02:20:48Comment · connection pool at its limit
  5. 02:43:38Resolved
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.