Everything your on-call team needs, in one plan

Oncallz schedules turn a rotation rule and an ordered list of people into concrete on-call shifts, so every incident goes to whoever is on call at that moment. Rotations hand off daily, weekly, every N days or several times a day, and overrides let people swap cover without touching the rotation.

Oncallz pages the on-call engineer by phone call, SMS, push notification and email, choosing the channels by incident severity. A phone call reads the incident aloud and lets the engineer acknowledge, escalate or resolve it from the keypad.

SMS and calls go through your own Twilio or Vonage account, so you pay carrier rates directly with no markup.

An escalation policy tells Oncallz who to page when the on-call engineer does not acknowledge an incident.

Each step waits a set number of minutes, then pages a schedule’s current on-call, everyone in a team role, or a specific person — and the whole ladder can repeat until someone takes the incident.

When an alert arrives, Oncallz can ask an AI model to read it and write a short summary, a probable cause and a suggested first step, attached to the incident before the on-call engineer is paged.

It runs on your own AI provider key, fails open when the provider is slow, and never silences anyone unless you explicitly let it skip the phone call for clear noise.

Oncallz gives each organization a public status page: components with 90-day uptime, incident statements with updates, and email or Slack subscriptions. An alert can prepare a draft for you, but nothing reaches customers until a person reviews and publishes it.

Oncallz turns an incident into a post-mortem draft: title, severity, a timeline built from the incident’s own events and any root cause already recorded.

Your team adds impact and action items with owners and due dates, publishes it internally, and can publish a separate plain-language statement for customers.

Oncallz is available in the Claude connector directory. Connect from Claude, Claude Code, Cursor or any MCP client with OAuth sign-in or a personal token and ask what is on fire, who is on call, or to acknowledge an incident and leave a note — with exactly the permissions you already have.