No more workarounds, no more endless configuration. Rootly On-Call is the reliable routing between your monitoring and your responders—by team, service, and everything else that makes sense, all with zero manual coordination.
AI-powered on-call that’s built for simplifying paging, scheduling, requesting coverage, and more—so you can stay focused on fixing.
We cut our resolution times in half and reduced repeat incidents. Rootly has been our best investment in terms of ROl.
Geoff Powell, Sr. Technical Manager, SRE
Connect all your existing alerting sources—and extend further with our Terraform provider, API, or MCP server.
Build schedules around teams or a dedicated group for peak events like Black Friday, and let Rootly route around PTO automatically so no one gets paged poolside in Barcelona. Need cover for a dentist appointment or a full shift? Request it in one click and Rootly's AI finds and schedules the substitute—all built in plain language, without a million clicks.
The Rootly app for iOS and Android brings real context to every page—what's happening, what's affected, and the action items to start resolving, and with mobile AI, you can ask questions and direct actions right from your fingertips, acknowledge, escalate, or hand off from anywhere in the world.
Multi-region resilient infrastructure backed by a 99.99% uptime that delivers your alerts across voice, SMS, push, Slack, and email with automatic fallbacks and Do Not Disturb overrides, so the page that matters most never gets missed.
Configure on-call through our API and Terraform provider, version-controlled like SREs want it, plus Rootly's MCP server so your AI agents can query and configure on-call directly.
We scoped, planned, and migrated tens of thousands of teams for companies like DoorDash and Brex. You get the full audit and plan upfront before committing.
We get it, there's migration work to do to ensure continuous service. That's why you don't start paying for Rootly until the day your PagerDuty contract ends.
Simple, intuitive, powerful, efficient, and beautiful.
No more using services as a workaround. Page teams, services, and more.
No extra rota, no manual cleanup when shadowing ends.
Ask questions and direct actions right from your finger tips, from anywhere in the world.
Overrides and requesting coverage made easy, including your PTO and holiday schedule.
No more manually calculating who should get paid with spreadsheets.
The basics done right. Setup your first schedule or escalation in minutes.
Sync Slack user groups like @team-infra with on-callschedules.
Never get caught with no one on call.
Automatically rotate on-call responsibilities, so no single team member is overwhelmed.
Consistency matters, ensuring escalation policies have enough levels.
Reporting and metrics from alerts to on-call readiness and everything in between.
Plugged into your IDE and CLI, so you can set config, get answers, and resolve incidents in seconds—right where you work.
Everything you need to know about Rootly On-Call.
What is On-call?
On-call is the routing system between your monitoring tools and your responders. It brings together schedules, escalation policies, notification channels, live call routing, and heartbeats so every critical signal reaches the right person—reliably and with no manual coordination.
How does Rootly decide who gets paged?
Rootly reads the alert's routing target—service, team, or escalation policy—then uses your live schedules and escalation rules to select the responder. If they don't acknowledge in time, it escalates to the next level until someone does.
What channels can Rootly page through?
Voice calls, SMS, push notifications, Slack, and email. Rootly chooses channels by urgency and user preference, handles retries and fallbacks automatically, and overrides Do Not Disturb for critical alerts.
Can Rootly handle complex schedules?
Yes, multi-person rotations, layered primary/secondary coverage, business-hour-only schedules, time-zone-aware planning, overrides, and shadow rotations. Slack usergroups update automatically so teams always know who's on call.
What is live call routing?
Live call routing turns a phone call into a page. It supports live connection to the on-call responder, voicemail-to-page, IVR trees for multi-team routing, and failover — the fastest way for a human caller to reach whoever's on call right now.
What are heartbeats?
Heartbeats detect silent failures. If a system stops checking in within its expected interval, Rootly triggers an alert and routes it to the right team; a recovery ping auto-resolves it. It's a first-party liveness check, no external uptime tool required.
How reliable is Rootly's paging?
Rootly runs on a multi-region redundant architecture with a 99.99% uptime SLA, with multi-channel fallbacks so a critical alert lands even if one channel or provider is degraded.
How long does migration take?
Most teams are live within a week. Rootly imports schedules and escalation policies directly, supports dual-running during the transition, and can be managed via API and Terraform.
.svg)
