On-Call
On-Call is Autoheal's native paging system. It covers who is on duty right now, who gets woken when an alert fires, and how that page escalates until someone acknowledges it. It replaces a standalone paging tool, and because it runs inside Autoheal, a page arrives with the investigation already underway.
On-Call is a separate add-on module. If you don't see On-Call in the sidebar, it isn't enabled for your organization, so contact support@autoheal.ai.
Everything below lives under On-Call in the sidebar, which has five tabs: My On-Call, Active Pages, All Schedules, All Escalation Rules, and Status Pages.
The four building blocks
| Object | What it is |
|---|---|
| Team | A group of people who own services and share schedules. Members have roles. Teams and people are the same entities as in the Context Graph. |
| Schedule | Who is on-call for a team, over time. Owns a timezone. |
| Rotation | A layer within a schedule: an ordered list of people and a shift length. |
| Escalation rule | Which alerts page, whom to page, and what happens when nobody answers. |
A schedule answers who is on duty. An escalation rule answers who gets paged and in what order. They are separate on purpose, so one escalation rule can page a schedule, a specific person, or a Slack channel.
Schedules and rotations
A schedule is built from one or more rotations, each a layer with its own participants and shift length.
- Participants are ordered. The rotation cycles through them in order, one shift each.
- Shift length is arbitrary: a week, a day, or twelve hours.
- Layers stack by priority. Each rotation has a layer order, and the lowest-numbered active layer wins at any instant. Higher-numbered layers act as fallback coverage. Layer
0is the top layer.
This is how you express "primary and secondary": a weekday-business-hours rotation on layer 0, and a broader always-on rotation on layer 1 to catch nights and weekends.
Each schedule carries a timezone, so shift boundaries land at sensible local hours for the people on it.
Overrides
An override replaces whoever the rotation would have picked, for a fixed window such as a doctor's appointment or a swapped weekend. You give it a person, a start and end time, and optionally a reason. Overrides win over rotations, and the timeline shows whether the current on-call came from a rotation or an override.
Previewing before you commit
Rotation changes are easy to get wrong, so you can preview a timeline before saving. Autoheal renders the resulting shift-by-shift schedule from a proposed configuration. It does not persist anything. You can then check that the handoffs land where you expect.
Escalation rules
An escalation rule has two halves: which alerts it applies to (matchers), and who it pages (nodes).