Alerts that reach the right person.

Send incidents to Slack, Discord or any webhook, and page whoever is on call by email, SMS or phone. One acknowledgement stops the noise.

Sentivel on-call schedules showing rotations across timezones with who holds the pager right now

Destinations and people

Integrations are where alerts go. People are who gets paged. Sentivel keeps the two straight, the way on-call should work.

Slack and Discord

Post incidents to a channel with a guided, type-first setup. Real brand formatting, a mute toggle, and a send-test button before you rely on it.

Webhooks

Point a generic webhook at anything you run and receive a clean, structured payload on every open and resolve.

Slack commands

Run an incident from Slack with a slash command, then acknowledge or resolve it right from the message.

Escalation policies

Build a ladder of steps that page channels, people or an on-call schedule, escalating until someone acknowledges.

On-call schedules

Rotations and one-off overrides on a calendar, with an iCal feed and two-way Google Calendar sync so nobody misses a handoff.

Phone, SMS and email

Page a person by email, text or a call-to-acknowledge phone call. All first-party and included, no bring-your-own account.

One-click acknowledge

A signed link or a button stops the escalation and records who responded, so a resolved page stops paging the rest of the team.

Severity routing

Route by impact, keep a noisy monitor silent, and promote a real one to a full policy when it matters.

Runbooks in the page

Attach a runbook to a policy and it shows to whoever gets paged, right on the incident and the acknowledge screen.

Quiet by default, loud when it counts

Flap thresholds and per-incident deduplication mean one incident is one alert, not a stream of them. A brief blip never reaches a phone, and a screening policy can record a noisy monitor without paging anyone until a human decides it matters.

Paid paging is the target for runaway cost, so every text and call passes durable per-number and per-org limits before it sends. You get reliable paging without an open-ended bill, and a heads-up if a cap is ever hit.

The best time to set up a status page is before you need one.