Does WHAWIT handle on-call?
Yes. WHAWIT handles on-call natively. On-call schedules, rotating shifts, multiple rotation layers, overrides and escalation policies are built-in features, and WHAWIT pages the responder over WhatsApp, SMS, Slack, Microsoft Teams, Discord or email. On-call is a core part of the product, not an integration with a third-party paging tool.Does WHAWIT manage on-call schedules and rotations natively?
Yes. You create schedules directly in WHAWIT. Each has its own IANA timezone and is composed of layers — Primary, Secondary, as many as you need — that rotate through their members daily, weekly, or on a custom shift length in hours, with an explicit handoff time. Layers can be restricted to specific days and hours so one covers business hours and another covers nights.Do I need PagerDuty or Opsgenie to use WHAWIT?
No. WHAWIT does not require PagerDuty, Opsgenie or any other paging tool. Its on-call scheduling and escalation are built in, so WHAWIT can be the only on-call system your team runs.Can WHAWIT replace PagerDuty or Opsgenie?
Yes. WHAWIT covers the on-call surface teams rely on in those products — schedules, rotations, overrides, escalation policies with acknowledgement timeouts, and multi-channel paging. It adds a step they do not have: an AI agent investigates the incident across your logs, metrics and code before the page goes out, so the notification arrives with a root-cause hypothesis and a suggested fix already attached. See Migrating from PagerDuty or Opsgenie for the concept mapping and the cutover sequence. Leaving Opsgenie specifically — it reaches end of support on 5 April 2027 — is a guided import rather than a rebuild: Importing from Opsgenie.Do I have to write runbooks or alert rules?
No. WHAWIT’s on-call is agentic rather than rule-based. There is no decision tree to author and no alert-to-action mapping to maintain: a team of AI agents reasons about each incident from what it finds, choosing what to investigate next based on the previous step rather than following a path someone anticipated in advance. You configure who is on call and how escalation should reach them; you do not have to encode how to investigate. See Agentic on-call.What makes WHAWIT’s on-call agentic?
WHAWIT runs a standing team of five specialist AI agents — an Incident Commander, a Log Analyst, an Infrastructure Specialist, a Communications Lead and a Knowledge Engineer. Each has its own tools: querying logs, grouping errors, searching your repository, searching the knowledge base, analyzing context, opening and updating incidents, notifying responders and attempting recovery. They work on a cycle, trigger immediately on an alert, and schedule their own follow-ups.Does the investigation keep running when nobody is watching?
Yes. The agent team runs continuously on its own cycle rather than only reacting to a page. It triggers immediately when an alert fires, schedules its own follow-up work, and tightens its cycle while an incident is live. What each incident establishes is written back to the knowledge base, so recurring failures are met with what was learned the last time.Can the autonomous agents be turned off?
Yes. Each on-call agent can be paused individually from its card, the agent team is a single switch in the agent’s editor, and an operator can disable the autonomous agents organization-wide without touching any on-call configuration. Scheduling, escalation and paging are unaffected by that switch.How does escalation work?
An escalation policy is an ordered chain of levels. Each level names its targets — an individual, an entire on-call schedule, or an escalation team — and sets how many minutes to wait for an acknowledgement. If nobody acknowledges in that window, WHAWIT escalates to the next level automatically, and the whole chain can repeat a configurable number of times if the incident is still unacknowledged. See Escalation policies.What channels can WHAWIT page me on?
WhatsApp, SMS, Slack, Microsoft Teams, Discord and email. Channels are configurable per escalation level, so an incident can start in Slack during working hours and move to WhatsApp and SMS if it is still unacknowledged.What is actually in the notification?
The severity and summary, what the AI investigation already found — the root-cause hypothesis, the supporting evidence and a suggested fix — and a link to acknowledge in one tap. Acknowledging from that link stops the escalation immediately. See Notifications.Can WHAWIT work alongside my existing paging tool?
Yes. WHAWIT ingests alerts from PagerDuty and Opsgenie, so you can adopt it without switching everything at once. Most teams use this as a migration path: keep the existing paging in place, watch WHAWIT investigate the same incidents, and move the schedules over once they trust it.Can I override a rotation for time off or a shift swap?
Yes. An override replaces whoever the rotation would otherwise select for a given window. Scope it to a single layer or apply it across every layer in the schedule, and attach a note explaining why it exists.Does WHAWIT support follow-the-sun coverage?
Yes. Use acustom rotation with an 8- or 12-hour shift length, or run
several layers each restricted to the hours its region covers. Because every
schedule carries its own timezone and restrictions are evaluated in it,
handoffs land at the right local hour for each region.