On-Call Management

On-call management

An on-call schedule belongs to one workspace and one team. It has an IANA time zone and one to five ordered layers. Each active layer requires at least one verified member of that same team.

Schedules express responsibility; they do not guarantee that a person is reachable. Test the resolved participant, time-zone handoff, override, escalation target, and configured delivery destination before production use.

Schedules and overrides

Create or update a team schedule with PUT https://api.monoduty.com/api/organizations/:organization_id/on-call/schedule. Layers support hourly, daily, weekly, or custom handoff intervals from 60 minutes to 525,600 minutes, with explicit UTC instants or values interpreted in the schedule time zone.

Participants must be verified workspace members assigned to the owning team. Temporary overrides use the authenticated /on-call/overrides routes. Verify boundary times and daylight-saving transitions with the people carrying the rota.

Escalation policies

A policy belongs to one team and contains one to ten ordered steps. Each step has a delay, a team-scoped user, team, schedule, or Account Admin target, and one or more of the release-gated channels: email, SMS, or phone call.

Custom policies are available within Pro and Business plan limits. Repeat counts greater than zero are rejected because repeated execution is not currently implemented. If a submitted policy omits an Account Admin fallback, the backend appends an email fallback after ten minutes.

Run a controlled incident through every configured step. Do not describe a policy as proof that a destination was delivered or noticed.