Skip to content

On-call runs on the same queue as the service desk.

On-call is the rotation and paging module of Service in The One Stack, the platform MSPs run their whole business on. It schedules who is on call, pages them through escalation tiers when an alert or an urgent ticket arrives, and keeps the incident on the service desk ticket. Service managers build the rotations, and technicians answer the pages.

On-call is part of Service, one of the six systems of The One Stack.

Illustration, sample data. Who is on call right now for each schedule, how to reach them, and when the shift hands over.

What it does.

Rotations and overrides

Build daily, weekly or custom rotations, add overrides for time off, and see who is on call now. Coverage checks flag gaps in the schedule.

Escalation tiers

An escalation policy pages the first responder, then moves to the next tier when the page is not acknowledged.

Paging by push, text, call and email

Each responder sets how they are reached. Paging rules decide which alerts page a person and which only open a ticket.

Shift trades

Technicians offer and claim shifts, and the schedule owner approves the trade.

Post-incident reviews

After an incident, record the cause, the fix and the follow-up actions, and publish the review.

Inside on-call.

More of the product, screen by screen.

Coverage by day

The coverage calendar shows who holds the rotation on each day. An override shows as its own mark, and a day with nobody scheduled is flagged so it can be filled ahead of time.

Illustration, sample data. The rotation laid out by day, with an override and a gap in coverage marked before they happen.

An escalation policy

A policy is a list of steps. Each step names a schedule, a person or a team, the ways to reach them and how long to wait before the next step takes over.

Illustration, sample data. An escalation policy as ordered steps: who is paged, by which methods, and how long each step waits.

How it connects.

On-call reads and writes the same record as the rest of the platform.

A device alert pages on-call

A critical alert from monitoring starts the escalation policy with the device on the incident.

Monitoring and alerting

A breached SLA escalates

A high-priority ticket that breaches its SLA, or a ticket a technician escalates, is handed to on-call.

Service desk

Page calls go out from your phone system

A page call routes through your phone system, so the responder sees your number.

Phone system

On-call work reaches the timesheet

A technician logs time against a shift or an incident. An admin approves it and pushes it to the timesheet.

Time and approvals

What THEO does here.

THEO writes the incident brief from the incident’s own record, so the responder starts with the context. Paging people stays with the escalation policy you set.

THEO

Questions

Questions about on-call

Does On-call replace my paging tool?

Yes. Rotations, escalation policies, paging and incident reviews are part of Service, on the same tickets as the service desk.

What can page the on-call technician?

Device alerts, security detections, backup failures, phone system outages and urgent tickets can all reach on-call. The paging rules you set decide which ones page a person and which only open a ticket.

Is on-call time billable?

The technician logs on-call time against the shift or the incident and marks it billable or not. An admin approves it before it reaches the timesheet.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.