Yes, WHAWIT handles on-call
WHAWIT includes native on-call management. On-call schedules, rotating shift layers, overrides and escalation policies are built-in features of the platform. You do not need PagerDuty, Opsgenie or any other paging tool alongside it — WHAWIT can be the only on-call system your team runs. What makes it different is not the scheduling. It is what arrives with the page. Before anyone is woken up, a standing team of AI agents has already correlated the alerts, read the surrounding logs and metrics, and formed a root-cause hypothesis. That analysis travels with the notification, so the engineer who picks up the phone at 3 AM starts from a finished investigation instead of an empty dashboard. That team is agentic, not rule-based. There is no runbook to write first and no alert-to-action mapping to maintain — the agents reason about each incident from what they find, and they keep working whether or not anyone is watching. See Agentic on-call.WHAWIT can also ingest alerts from PagerDuty and Opsgenie. That is a
migration path for teams who want to evaluate WHAWIT against live incidents
before moving their rotations — not a dependency.
The parts
All the features
The complete capability list in one place — investigation, scheduling,
escalation, paging, coordination and migration.
Guided setup
Describe your team and WHAWIT proposes the teams, schedules and policies for
you to review.
The agents screen
Every on-call agent in the project as a card — status, objective, escalation
wiring and cadence at a glance, with start and pause in place.
Agentic on-call
A team of five specialist AI agents that investigates without pre-written
runbooks, on a cycle that never stops.
Schedules and rotations
Timezone-aware schedules built from layers that rotate daily, weekly or on a
custom shift length. Restrictions, handoff times and overrides included.
Escalation policies
Ordered levels, each with its own acknowledgement timeout. Escalates on its
own when nobody answers, and can repeat the whole chain.
Notifications
WhatsApp, SMS, Slack, Microsoft Teams, Discord and email — configurable per
escalation level, carrying the triage in the message body.
Migrating
Moving off PagerDuty or Opsgenie, and how to run both side by side while you
do it.
How a page happens
1
A signal becomes an incident
Alerts arriving from your connected providers are correlated and
deduplicated, so one underlying failure raises one incident rather than
forty notifications.
2
The agent team investigates first
Before a human is involved, the agents pull the logs, metrics and recent
deploys around the failure and form a root-cause hypothesis with the
supporting evidence attached — deciding what to check next from what they
find, not from a rule written in advance.
3
The schedule resolves who is on call
WHAWIT evaluates the rotation in its own timezone — layers, handoff times,
restricted hours, and any active override — and returns the engineer
actually responsible at that moment.
4
The responder is paged, with the triage
The notification goes out on the channels configured for that escalation
level. It carries the severity, the summary, what WHAWIT found, and a link
to acknowledge in one tap.
5
No acknowledgement, next level
Each level has its own timeout. If nobody acknowledges in time, WHAWIT
escalates to the next level on its own, and can repeat the whole chain until
someone picks it up.
Core concepts
Where to go next
Set up your first schedule
Build a rotation, set the handoff, and check who it puts on call.
On-call FAQ
Direct answers to the questions teams ask before adopting it.