Who's on call, answered in chat. You confirm each action first.
Ask who's on call right now, when your next on-call shift starts, or which incidents fired overnight. Acknowledge, respond to or resolve an incident once you confirm it.
Ask who's on call right now, when your next on-call shift starts, or which incidents fired overnight. Acknowledge, respond to or resolve an incident once you confirm it.
Trusted by frontline employers everywhere
Who's on call, live across every pool
Every active pool you can see, with the people on call right now, answered without opening another tool.
-
Primary or backup, and until when
So you know who to try next and whether the answer changes in an hour.
-
Filter to one pool
Partial-match on pool name, so "sre" returns both Primary and Secondary.
-
Permission-aware
Anyone in the business can ask; pools at locations they can't see are left out.
Know when you're next on call
Ask "when am I next on?" or "am I on this weekend?" and plan around the answer.
-
Today, this week, this month
Today, the next 7 days or the next 30, with the next 7 by default.
-
Pool and role
The pool, the start and end, and whether you're primary or backup.
-
Your day, your time zone
Shifts from the start of today, asked about your day in your own time zone, not the server's.
Every incident, ready for Monday's review
Pull the incidents for a window, filtered by status, severity and date, for reviews and the Monday catch-up.
-
Status and severity filters
Active, acknowledged, resolved or cancelled; low, medium, high or critical.
-
Date filters
Raised or updated before or after a date you name.
-
Each incident's answers
Who raised it, when, and how many paged people answered and said they could respond.
Take the page in chat, once you confirm
Acknowledge an incident, record your response and ETA, or resolve it; each one shows a preview first.
-
Three writes, each confirmed
Acknowledge, respond and resolve show a preview and wait for you; nothing is written on the model's say-so.
-
Resolve is permission-gated
Only someone who already holds the On-Call resolve capability is offered the tool at all.
-
No paging, no rotation changes
The agent never starts a cascade; who covers which shift is changed in the On-Call app.
On-Call Management Agent at a glance
On-Call AI
Who's on call, your next shift, the open incidents — and the page, taken in chat.
Healthcare
“We wanted to drive people into MangoApps, and we wanted to make our Assistants useful immediately. Petauri Ask was trained on resource guides we’d already uploaded, so employees could ask things like ‘How do I submit an expense report?’ or ‘Where do I find the holiday calendar?’”
Retail
“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.”
“MangoApps’ search capability has been critical. It brings back so much information that would have been lost on our old intranet. The content is fresh and current. It’s been really, really nice to have.”
Results from teams like yours
Part of one app your people already use
The agent reads the same on-call shifts and incidents the On-Call Management app runs on, with no parallel store.
Questions on-call teams ask
It reads four things — who's on call right now across every pool you can see (or one pool you name), each person's role and when their shift ends; the pools with how many people are on now, their rotations and open incidents; your own on-call shifts for today, the next 7 days or the next 30; and incidents filtered by status, severity and date. It can also acknowledge an incident, record your response and ETA, and — if you may resolve incidents — resolve one, each after you confirm.
It can acknowledge, and it cannot page. Acknowledging an incident, recording your response and ETA, and resolving an incident are the agent's three write tools, and each one shows you a preview of the change and waits for you to confirm before it happens — resolving also requires the On-Call resolve permission. The agent never starts a paging cascade and never changes a rotation; those stay in the On-Call app.
Not through the agent. get_my_on_call_shifts is self-scoped — it returns the requesting user's own shifts. who_is_on_call shows who is on call right now and until when; for a pool's upcoming shifts, open the pool in the On-Call app.
list_activations accepts status (active, acknowledged, resolved, cancelled) and severity (low, medium, high, critical) filters, dates the incident was raised or updated before or after, plus a limit (default 20, max 50). Useful for post-shift reviews and weekly reliability reports.
Time to answer "who's on call?", time to acknowledge from chat, post-shift review prep time, incidents left open, and agent adoption versus scheduling-tool opens. Compare against your pre-agent baseline.
See what MangoApps can do for your frontline
Every team. Every employee. Every workflow. One AI platform — built for the frontline. Since 2008, trusted by 2 million+ users with an NPS of 78.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Prefer to explore first? Ask AI about On-Call AI Agent →
- Within one business day: a solutions consultant asks about your workforce and what you run today.
- The demo shows your use case: your sites, your frontline roles, your systems.
- It ends with your price: the package and the price for your employee count, not a generic quote.
