On-call that respects manual overrides.
The rotation engine is a pure projector — it generates 28 days of shifts ahead of time, with a clear engine vs manual source tag so re-projection never wipes a human override.
On-call schedules
Weekly or daily handoffs, follow-the-sun, restricted business hours — the full matrix without escape-hatch hacks.
- Weekly handoffs with custom day-of-week starts
- Daily rotations for high-volume teams
- Follow-the-sun across timezone-grouped responders
- Per-schedule timezone configuration
- Visual shift calendar with at-a-glance gaps
Multi-period rotations
Build complex rotations — primary + secondary, alternating weeks, shadow shifts — without leaving the UI.
- 1–52 rotation periods per schedule
- Primary + secondary + shadow tiers
- Alternating rotations (e.g. odd-week / even-week responders)
- Per-period responder lists with auto-balance
- Re-projection preserves the engine vs manual provenance
Business-hours restrictions
Limit a rotation to specific weekday × time-window slices — so the night/weekend rotation routes elsewhere.
- Weekday × time-window matrix per rotation
- Multiple restriction blocks per schedule (e.g. mornings + evenings)
- Visualised on the calendar with shaded off-hours bands
- Off-hours automatically route to the secondary schedule
Manual shift overrides
Swap a shift, take vacation, cover a colleague — the override survives every re-projection.
- Drag-to-override on the shift calendar
- Source tag distinguishes engine-generated vs manual shifts
- Override audit trail with timestamps and actor
- Bulk-override interface for known vacation blocks
Escalation policies
Multi-level escalation with timeout-based hand-off and per-step channel routing. No 'forgot to acknowledge → page no one' edge cases.
- Unlimited escalation levels per policy
- Per-step timeout before bumping to the next level
- Per-step channel mix (e.g. mobile push first, then SMS, then voice)
- Voice call escalation via TwilioRoadmap
- Final-resort fallback to a service group
Runbooks & postmortems
Linked to the services they cover; surfaced on every page, every alert and every postmortem.
- Markdown runbooks attached to services
- Runbook link appears on every alert email, Slack message and push
- Postmortem authoring linked to the originating incident
- Timeline import from the incident into the postmortem draft
- Per-postmortem action-item tracking
Incident timeline & audit
Every state change captured — alert fired, ack'd, escalated, resolved — with actor and source so postmortems write themselves.
- Full incident lifecycle on a single timeline
- Per-event actor (user, system, escalation engine)
- Acknowledgement source (web, mobile, SMS reply)
- Export to Markdown for postmortem documents
How we stack up on incident response
Only rows relevant to this capability. See the full comparison →
| Feature | AlertifyPro | Datadog | UptimeRobot | Pingdom |
|---|---|---|---|---|
| On-call rotation engine (multi-period, restrictions) | ||||
| Manual shift overrides preserved across re-projection | ||||
| Multi-level escalation policies | ||||
| Postmortems linked to incidents | ||||
| Runbooks attached to services |
Frequently asked
Continue exploring
Alerting
Structured suppression, dependency-aware routing, flapping detection — built in, not bolted on.
Read moreNotifications
Nine first-class delivery channels, HMAC-signed webhooks, templated payloads and a failed-delivery viewer.
Read moreTeams & Access
Multi-org, RBAC, SSO (SAML + OIDC), SCIM, TOTP MFA, social login and per-tenant data scoping carried on every query.
Read moreReady to see incident response on your stack?
Spin up your first monitor in under a minute. Free forever for the first 5 services.