Core capability · Free+
Incidents & alerts
Your customers should never be the first to tell you something broke — every probe transition wakes the right humans on the right channels, the second it happens.
Why you need it
An outage you hear about from a Zendesk ticket is an outage you've already lost the room on. Alerts mean your on-call sees the red pill before the first customer does — and the exec who only wants to hear about resolutions isn't woken up at 3 AM.
- Five channels, all in the box. Email (Free+), Slack, Microsoft Teams, SMS, and outbound webhooks to PagerDuty, Opsgenie, Zapier, or your own receiver — no add-ons, no per-channel pricing surprise.
- Three event types, each independently toggled. Start, Change, Resolution. Your on-call rota gets everything; your CEO gets Resolution only. One workspace, two very different inboxes.
- Persons and Groups, not "watchers". Build a workspace directory once, attach individuals to the probes they own and a Group to the page, swap rota members weekly without touching a single subscription.
- Per-probe and per-page subscriptions, de-duplicated. Someone reachable through four different paths still gets exactly one notification per transition. No "why did I get six emails for the same alert" tickets.
- Audited end-to-end. Every send is logged with recipient identity captured at delivery time — so you can prove who was notified, when, and on which channel, months later.
Where it pays off
The default answer to "how does my team find out something broke":
- Solo on-call rota across the platform. One Group, attached at page level, members swapped weekly. The subscription stays put; the people behind it rotate.
- Owners per probe. Backend lead on the database checks, frontend lead on the HTTP probes, infra lead on DNS — each attached individually only to what they own.
- Exec / stakeholder visibility. Resolution-only toggled on. They learn about outages closing, not opening, and stop forwarding you "is this still happening?" emails.
- External incident routing. Outbound webhook into PagerDuty Events v2 and your existing escalation rules, rotations, and ack tracking take over from there.
Not the right tool when: you want to notify your customers rather than your team — that's what public status page subscribers are for.
Available on Free+. Already on StatusPulse? See the full config in Help →
Related
Try Incidents & alerts in StatusPulse
5 probes, 1 status page, forever. No credit card. US or EU host — you choose.