The short version
WHAWIT manages on-call itself. Schedules, rotating shift layers, coverage restrictions, overrides and escalation policies are built-in features of the platform, and WHAWIT pages responders directly over WhatsApp, SMS, Slack, Microsoft Teams, Discord and email. WHAWIT does not depend on PagerDuty, Opsgenie or any other paging tool. It can be the only on-call system a team runs. This page exists because the opposite is sometimes assumed — that WHAWIT is a layer that enriches incidents while a separate tool does the paging. It is not. The paging is ours.What is built in
See Schedules and rotations and
Escalation policies for how each of these
behaves in practice.
What is genuinely different
The scheduling is not the interesting part — plenty of tools rotate a list of names correctly. What WHAWIT does that a paging tool does not is investigate before it pages. By the time the notification is sent, WHAWIT has correlated the alerts, read the logs and metrics around the failure, looked at recent deploys, and formed a root-cause hypothesis. That hypothesis, the evidence behind it and a suggested fix travel in the message body. The responder’s first decision is whether the conclusion is right — not where to start looking.This is why the on-call and the investigation live in the same product. A
paging tool that hands off to a separate analysis tool cannot put the analysis
inside the page, because at the moment it pages, the analysis does not exist
yet.
On coexistence
WHAWIT can ingest alerts from PagerDuty and Opsgenie, and that capability is real and useful: it lets a team evaluate WHAWIT against live incidents without changing anything for the people carrying the phone. It is a migration path, not a dependency. See Migrating from PagerDuty or Opsgenie.Related
On-call overview
How a page happens, end to end.
On-call FAQ
The questions as people actually ask them.