SLA alerts and anomaly detection for notification health

The worst way to find out your password-reset emails are bouncing is from a customer phone call. The second-worst is from a chart you happen to look at the next morning. SLA alerts watch the health signals that matter and page the right person the moment they shift.

Deliverability & Observability
·
Available in the United States · English documentation

Capabilities you don't have to build, monitor, or babysit

Each capability ships on the standard plan. Nothing in this list is an upsell or a separate product line.

01

Per-channel SLAs with sensible defaults

Each channel ships with a baseline SLA: email median delivery under 30 seconds, transactional SMS under 5 seconds, webhook end-to-end under 2 minutes. Override per workspace if your platform commits something stricter.

02

Statistical anomaly detection, not just thresholds

A static 'alert if bounce rate > 3%' rule fires too often for low-volume senders and too rarely for high-volume ones. We baseline each metric against its own history and alert on standard-deviation-based deviations.

03

On-call routing via PagerDuty, Opsgenie, and Slack

Critical alerts route to on-call; warnings go to Slack; informational signals go into a daily digest. Acknowledgement and resolution flow back into the platform so post-mortems include the alert timeline.

04

Customer-facing status feed (optional)

Publish the subset of incidents that affected real recipient delivery to a status page or in-app banner — preserving trust during the rare incident instead of leaving customers to guess.

Where US customers actually use this

  • Page on-call when MFA SMS delivery time crosses 10 seconds
  • Alert when a single template starts generating spam complaints
  • Notify the platform team when webhook P95 latency degrades for a specific customer
  • Catch a DNS misconfiguration that breaks DKIM signing within minutes
  • Detect a runaway flow that's about to blow through a customer's notification budget

All anomaly history is part of the same audit log, so the timeline of 'when did we know about this' is always recoverable — there's no separate observability product to license or piece together.

More in Deliverability & Observability

The rest of this product family

Explore the rest of the platform

Other 4notify product areas

Messaging APIs

Reach customers on the channel they actually open — email, US-native SMS, WhatsApp Business, and any system you can point a webhook at.

Lifecycle & Automation

Move beyond one-off sends. Trigger flows from product events, sequence messages across channels, and adapt copy to who is reading it.