Failure Alerts
Alerts that reach you even when the transport is down Free & Pro
Failure Alerts: what it does
Every other alert system has the same fatal flaw: it tells you email is broken by sending you an email. NimblyMail hooks wp_mail_failed and dispatches alerts through a native PHP mail() bypass — an independent transport that works even when your entire SMTP stack is down. Self-rate-limited with a 60-second cool-off, so an outage means one alert, not four hundred.
What you get with Failure Alerts
Independent transport
Alerts bypass your mailer entirely — they reach you even when the SMTP provider is down.
60-second cool-off
Self-rate-limited so a burst of failures doesn't flood your inbox or ticketing system.
CC/BCC for teams
Route alerts to team inboxes, Slack bridges, or ticketing systems with CC and BCC support.
Sandbox-aware
Staging and Log Only environments suppress alerts automatically — no false alarms from CI.
Three steps, zero babysitting
A send fails
wp_mail_failed fires — a provider outage, an auth error, a rejected recipient. NimblyMail catches it.
Cool-off check
If an alert was sent in the last 60 seconds, the failure is logged but no duplicate alert fires.
Alert dispatched independently
The alert leaves through the bypass transport with the error, recipient, and a link to the full log entry.
Failure Alerts questions, answered
NimblyMail's alert transport bypasses your configured mailer and even PHP mail() — it dispatches through an independent channel, so a dead SMTP provider can't take your alerting down with it.
No. A 60-second cool-off self-rate-limits alerts, and repeated identical failures are grouped. You get one actionable alert, not a flood.
Yes — alerts support CC and BCC, so you can fan them out to Slack email bridges, Help Scout, Zendesk, or any address your team watches.
Related features
View all featuresSmart Email Routing Pro
Rule-based per-message dispatch across providers
Transactional and marketing email have opposite needs. Smart Email Routing dispatches each WordPress message through the provider that fits it…
Learn moreBackup Mailer Failover Pro
Automatic retry through a backup provider
Every email provider has bad days. NimblyMail Pro automatically re-sends failed messages through a backup provider once the retry budget…
Learn moreBackground Email Queue Free & Pro
Non-blocking sends with HIGH/NORMAL/BULK priorities
By default, WordPress sends email synchronously, forcing visitors to wait on wp_mail(). NimblyMail moves every send into an Action Scheduler-backed…
Learn more