On-call schedules and escalation policies
Noci AI runs on-call schedules with layered rotations, restrictions, handoffs and overrides, and shows who is on call right now. Escalation policies keep running through restarts and outages, across Slack, phone and SMS. A backtest replays a policy against your real incident history, and a dry run shows who it would page.
What does Noci AI’s on-call cover?
On-call is the part of an incident platform that decides who gets woken, and how. Noci AI keeps schedules and policies in the same product as triage, the incident room and the investigation, so a page arrives with the context behind it.
| What | What it does |
|---|---|
| Schedules | Layered rotations, with restrictions |
| Handoffs and overrides | Handoffs between shifts, and overrides for a swap or a day off |
| Who is on call | Shown right now, for every schedule |
| Escalation policies | Steps that reach people in order, across Slack, phone, SMS and Teams |
| Backtest and dry run | A policy checked against real history before it pages anyone |
How does an escalation policy run?
A policy is a list of steps. Each step says who is reached and how, and what happens if nobody answers. Policies keep running through restarts and outages.
- Paging goes out at once. AI triage runs alongside it from the first alert, and the person paged sees the score and the reasons. If you choose, paging waits for triage instead. See AI SRE.
- Noisy alerts can stay off a policy. You can keep alerts above a flakiness score off it, and each one still shows its score and reasons.
- A call is a step. The AI voice agent can phone the engineer as a step in a policy or a workflow. See the AI call.
How a good policy is built, and how they go wrong, is in what an escalation policy is and escalation policy anti-patterns.
How do you check a policy before it pages anyone?
Two checks, both before a real page. A backtest replays the policy against your incident history, so you see how it would have behaved on the nights that mattered. A dry run shows who it would page now, without paging them. Together they turn a change to a rotation or an escalation policy from a guess into something you can read first.
What about the tool you use now?
Noci AI imports your existing schedules and escalation policies, and you choose what moves. The importer moves them for you. The steps are on the migrate page. For a small team, on-call for a team of five shows a rota that holds up.
Questions
Where does Noci AI page people?
By phone, SMS, Slack channel and Microsoft Teams, as your escalation policy says. Each step of a policy names who is reached and how, and the next step starts when nobody answers.
Does AI triage hold up the page?
Not by default. The page goes out at once and AI triage runs alongside it from the first alert. If you choose, paging waits for triage, so the person paged starts with a score and the reasons.
Can a policy be tested before it pages anyone?
Yes. A backtest replays the policy against your real incident history and shows what would have happened. A dry run shows who it would page right now, without paging anyone.
Can we bring our schedules and policies from the tool we use now?
Yes. Noci AI imports your existing on-call setup, and you choose what moves. The migrate page walks through it.