Page one person. Escalate if they don’t answer.
Incidents go to Slack, Discord or a webhook. Whoever is on call gets an email, a text or a phone call, and the moment they acknowledge, nobody else is paged.
- Right awayMaya, on callText and Slack
- After 5 minutesMayaPhone call
- After 10 minutesSam, backupText and phone call
Maya acknowledged at 14:05. Nobody else was paged.
One incident, one alert.
An incident opens after a run of failed checks, so a flapping endpoint sends one alert.
Every text and call is checked against per-number and per-workspace limits before it’s sent.
Where alerts go
- Slack and Discord
- Post incidents to a channel. Each integration can be muted and has a test button.
- Webhooks
- A structured payload to any URL when an incident opens or resolves.
- Slack commands
- Open an incident with a slash command, then acknowledge or resolve it from the message.
- On-call schedules
- Rotations and overrides on a calendar, with an iCal feed and Google Calendar sync.
- Text and phone calls
- On Pro and above, with no telephony account of your own to set up.
- Acknowledge in one tap
- A signed link or a button stops the escalation and records who answered.
- Severity routing
- Keep a noisy monitor quiet, or send it to a full escalation policy.
- Runbooks
- Attach one to a policy. Whoever is paged sees it on the incident.
