Covered On-Call Escalations
Who's on call right now, your upcoming rotations, every pool's rotation cadence, and the activations (incidents) that fired during a window — all answerable in chat. Four tools; intentionally read-only — paging, scheduling overrides, and acknowledgements stay in the On-Call app.
Where On-Call Coordination Breaks Down
On-Call Management Agent attacks the four specific failures that turn a clean rotation into a hunt for the right person — without changing the paging or escalation rules the On-Call app already enforces.
"Who's On Call Right Now?" Becomes A 5-Minute Hunt
The customer ticket is hot. Support pings the team channel. Three engineers reply "not me — I think it's Jamie?" Jamie was last week. The actual on-call is logged somewhere in a scheduling tool nobody bookmarked. The customer waits while we figure out who to escalate to.
Engineers Forget They're On Call Until The Page Fires
Their shift started Monday 9 AM. By Wednesday afternoon they've forgotten — they've scheduled a late dinner, started a long meeting, gone to the gym. The page wakes them up. A quick "when am I next on?" lookup would have spared the conflict.
Rotation Handoffs Get Missed
Sam's PTO starts Wednesday but his on-call rotation also ends Wednesday at 9 AM. The handoff is supposed to flow to Rina. Without a clear sight of upcoming handoffs, the swap doesn't get arranged until someone notices Tuesday night.
Post-Shift Reviews Lack Activation Context
The on-call rotation ended Friday. The retro is Monday. Nobody remembers exactly which incidents fired, when they were acknowledged, or how long they ran. The activation log is in a different tool that nobody opened over the weekend.
Page Load Across The Team Goes Unmeasured
Two engineers carry 60% of the off-hours pages because their pool has the noisiest service. The on-call distribution report — pages per engineer per quarter — exists, but nobody runs it between attrition postmortems. The fairness conversation happens after one of the two engineers resigns, not before.
"Am I On Call Next Week?" Lives In A Calendar Nobody Cross-Checks
An engineer plans a Thursday night dinner three weeks out, forgets to check the rotation calendar, and discovers Tuesday afternoon that he's primary that night. Without a fast "what are my upcoming rotations?" lookup, life-and-rotation conflicts get caught at the last minute — and trades scramble through three Slack DMs.
On-Call Management Agent At A Glance
On-Call AI
Pager rotations, tier escalations, miss re-routing.
Inside On-Call Management Agent — The Actual Capabilities
Every block below maps to a real tool the agent uses against your On-Call records. All four tools are read-only — the agent never pages, never acks, never overrides a rotation. Those actions stay in the On-Call app.
"Who's On Call Right Now?" — Live, Across Every Pool
The single most common on-call question, answered in chat without opening another tool. The agent surfaces every active on-call rotation with the current on-call person, when their shift ends, and how to reach them.
- who_is_on_call — every active rotation with the current on-call person.
- Filter to a specific pool — partial-match on pool name so "sre" returns both Primary and Secondary.
- Shows the handoff time — when each current shift ends so you know if the answer changes in an hour.
- Permission-aware — anyone in the business can ask; the underlying pool membership rules still apply.
Your Upcoming Shifts — Today, This Week, This Month
Engineers can ask "when am I next on?" or "am I on this weekend?" and get the answer in chat. The tool returns upcoming and recent shifts so the engineer can plan around them — or know which past shift the retro is covering.
- get_my_on_call_shifts — the current user's upcoming and recent on-call shifts.
- Time period filter — today, week, or month (defaults to week).
- Shows pool and pairing — the rotation, the start/end, and who's on the paired pool.
- Self-scoped — returns the requesting user's shifts. Managers use list_on_call_pools to see team-wide rotations.
Pool Rotations — Cadence, Handoffs, And Coverage
Managers and team leads can see every active pool, how the rotation is structured, who's currently on each one, and when the next handoff happens. Surfaces upcoming handoffs that overlap with known absences before they become Wednesday-night scrambles.
- list_on_call_pools — every pool with current on-call person, rotation cadence, and next handoff.
- Active-only filter — default active_only: true, but you can include retired pools when needed.
- Up to 50 results — covers every pool a real engineering org maintains.
- Read-only on rotations — schedule overrides and rotation edits still happen in the On-Call app.
Activations — Incident History During A Window
Pull the activation history for the team or pool — used for post-shift reviews, retro prep, and weekly reliability reports. Filter by status (active, acknowledged, resolved, cancelled) and severity to focus on what matters.
- list_activations — on-call activations (incidents) with optional filters.
- Status filter — active, acknowledged, resolved, or cancelled.
- Severity filter — low, medium, high, critical.
- Audit-ready — every read is logged with the requesting user, the tool, and the parameters.
Outcomes Teams Can Measure
The agent is built to compress "who's on call?" answer time, prevent rotation-handoff surprises, and make activation history queryable for retros. Measure against your pre-agent baseline.
- Time to answer "who's on call?" — seconds from question to definitive answer, replacing channel polling.
- Rotation-handoff conflict catches — share of upcoming handoffs flagged against PTO before they become incidents.
- Post-shift review prep time — minutes to pull the activation log for a specific window.
- Wrong-person escalations — incidents initially paged to someone no longer on rotation, trending against baseline.
- Agent adoption — share of "who's on?" / "when am I on?" questions answered through chat vs scheduling-tool open.
Intentionally Read-Only · Paging Stays In The On-Call App
On-Call Management Agent's RISKY_TOOLS list is empty. The agent does not page, acknowledge, resolve, or override a rotation. Those actions stay in the On-Call app where the escalation rules and audit trail are most stringent. Every tool call is a read.
- Zero write tools — the agent surfaces information; it never pages or acks.
- No rotation overrides through chat — schedule swaps and overrides stay in the On-Call app.
- Permission-aware — pool membership and visibility rules from the On-Call app are respected on every read.
- Audit trail on every action — every tool call logs the requesting user, the tool used, and the parameters.
WHAT TEAMS TRY INSTEAD
The four alternatives — and why none of them know the rotation, the pool, and the visibility rules at once
Most operations and SRE leaders reach for one of these four. None of them stick because none of them combine on-call ledger, escalation chain, and pool-visibility rules in one read-only surface.
ChatGPT or Claude reading a copied schedule
General-purpose AI on a static rotation paste
- Reads the live on-call rotation, escalation chain, and override state — not a snapshot from Monday's standup
- Honors pool membership and visibility rules — never returns rotations the user shouldn't see
- Joins schedule, shift, and leave context so "who can cover Saturday" actually has an answer
PagerDuty AIOps, Opsgenie AI, Splunk On-Call AI, incident.io AI
Vendor-trapped AI inside the paging platform
- Works for the frontline ops, field service, and operations crews who never had a PagerDuty seat
- Cross-references HRIS, leave, training, and credential context — not just the paging ledger
- Same chat surface the rest of the team already uses — no separate ops portal, no extra mobile app
A custom rotation script + Slack reminder bot
Engineering's "let's track on-call ourselves" build
- Already shipped — no cron job to maintain, no Slack bot to keep alive through API deprecations
- Pool-visibility rules enforced at the tool layer — not by hoping the script filters correctly
- Audit trail on every read with the same retention as the rest of the platform
The manual fallback — "who's on call?" Slack message
A Slack ping and a wiki page that's three months stale
- Deflects the routine "who's on this weekend" pings that hit the ops lead a dozen times a day
- Returns the right answer the first time — not the stale wiki everyone forgets to update
- Surfaces escalation chain, coverage gaps, and override state — not just the primary's name
PLATFORM ADVANTAGE
On-Call Agent inherits everything the platform already runs
A standalone on-call vendor has to plumb each of these. The agent gets them for free because the platform already does.
Live rotation ledger
Reads the same rotation records the On-Call Management app enforces — no parallel store, no drift between the bot and the rule of record.
Pool visibility rules
Pool membership and visibility scoping respected on every read — non-members never see rotations they shouldn't.
Zero write tools
The agent surfaces information — it never pages, acks, or moves a rotation. Schedule swaps and overrides stay in the app.
Cross-app schedule context
Joins Schedule, Leave, Training, and credential data so coverage questions have an actual answer — not just a list of names.
Audit trail & retention
Every read lands in AiApiLog with the same retention and eDiscovery posture as the rest of the platform.
RubyLLM-grounded model tiering
Nano / small / medium / standard tier selection routes routine "who's on call" lookups to cheap models and reserves the big ones for coverage reasoning — automatically, per call.
INDUSTRY FIT
Industries where embedded on-call awareness moves the most weight
On-Call Agent matters most where the rotation is the operations backbone and the answer can't be "let me ask Slack."
Healthcare
Tracks hospitalist, charge-nurse, and specialty on-call rotations alongside license and credential context — no paging vendor sees credentials.
Manufacturing
Surfaces plant on-call coverage, safety-officer rotation, and certified-operator availability in one ask.
Field Services
Joins technician on-call rotation with route assignment and skill matrix — the operational levers that determine response SLA.
B2B SaaS & Tech Ops
Tracks SRE and platform-on-call rotation alongside incident history without a separate PagerDuty seat for everyone who needs to know.
Hospitality
Surfaces property-level manager-on-duty rotation and after-hours coverage without a separate ops portal nobody checks.
Public Sector & Utilities
Runs entirely inside FedRAMP-eligible deployment options with full audit logging — no rotation data leaving the tenant boundary.
WHY MANGOAPPS WINS
An embedded on-call agent beats a chatbot, a paging-platform add-on, or a custom build on every axis
The argument ops, SRE, finance, and IT all share — and the one a horizontal AI or single-vendor add-on structurally cannot answer.
Cheaper than the alternatives
No PagerDuty seat for everyone who needs to know, no Opsgenie SKU, no per-seat ChatGPT, no Slack-bot maintenance, no extra ops headcount fielding "who's on call?" pings.
More secure
Zero write tools, pool-visibility enforcement, and AiApiLog audit trail mean rotation data never leaks beyond the people who should see it.
Easier to deploy
Already deployed if On-Call Management is enabled. Turn the agent on, point it at the pools you already configured, and it's running the same day.
Easier to use
Lives in chat next to the team that needs to know — no separate paging portal, no mobile app install, no wiki page to keep current.
Easier to manage
Per-business pool rules, visibility scoping, and audit retention sit in the same admin console as every other app's settings.
Easier to extend
Shares the agentic tool framework with every other MangoApps agent. New rotation dimensions and new coverage signals ship as tools, not rewrites.
AI is actually better
A horizontal or paging-platform AI can name the primary on call. Only On-Call Agent can also see leave, training, and credential context — and prove the answer is current.
At our head office within HR, marketing, and finance, we use ChatGPT quite a bit, and MangoApps AI Helper is a useful tool for us. As I go around to the stores, I’ve been showing them how the AI Intranet Helper can find things and answer plain language questions about our resources, and they’re quite excited about that.
Alison van Zijl
Head of Human Resources
Full House
Customer Success
Related Customer Stories
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Frequently Asked Questions About On-Call Management Agent
4 tools across on-call visibility — see who's currently on call across every pool (or filter to a specific pool), list the active on-call pools with their rotation cadence and next handoff, view the current user's upcoming and recent on-call shifts (today, week, or month), and list activations (incidents) filtered by status and severity.
No. The agent's RISKY_TOOLS list is empty — it does not page, acknowledge, resolve, or override a rotation. Paging and acks stay in the On-Call app where the escalation rules and audit trail are most stringent.
get_my_on_call_shifts is self-scoped — it returns the requesting user's rotations. To see team-wide upcoming coverage, use list_on_call_pools which surfaces the current and next on-call person for every active pool.
list_activations accepts status (active, acknowledged, resolved, cancelled) and severity (low, medium, high, critical) filters, plus a limit (default 20, max 50). Useful for post-shift reviews and weekly reliability reports.
Time to answer "who's on call?", rotation-handoff conflict catches, post-shift review prep time, wrong-person escalations, and agent adoption versus scheduling-tool opens. Compare against your pre-agent baseline.
Let's Talk
Since 2008, we've been building the employee platform for the frontline, earning the trust of 2 million+ users and an NPS of 78.
Why Choose Us?
- AI-Ready Platform: One intelligent place for every employee and workflow.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Trusted by Legendary Companies:
Prefer to explore first? Ask AI about On-Call AI Agent →