How to detect a transactional email failure before your client (or their customers) do
Transactional emails – order confirmations, password resets, membership receipts – are often the most business-critical emails a WordPress site sends. They’re also the ones you’ll never hear about until they’ve been broken for a while.
ToggleWP’s Email Health Monitor gives you the tools to catch failures early, understand the cause, and fix them before anyone complains.
The problem with silent failures
WordPress doesn’t tell you when an email fails to send. A misconfigured SMTP plugin, a hosting provider blocking port 25, or a plugin update changing the From address – any of these can silently kill your outgoing mail. The first sign is usually an angry customer or a client asking why nobody’s been getting password reset emails for a week.
How Email Health Monitor catches failures
The module logs every outgoing WordPress email and runs anomaly detection every 15 minutes. It compares current send volume against a 14-day rolling baseline for each email category.
If transactional emails stop – or drop significantly – an alert fires.
Alert types:
- Critical: sudden drop to zero or near-zero
- Warning: unexpected volume change outside normal range
SMTP deliverability diagnostics
Beyond volume, the module actively checks for common deliverability problems:
- No SMTP plugin installed
- Generic or unbranded From addresses (e.g.
wordpress@yourdomain.com) - Known SMTP plugins detected but potentially misconfigured
These are flagged in a dedicated SMTP Deliverability Panel so you know what to fix.
Alert deduplication
To avoid inbox flooding, alerts are deduplicated – critical alerts are suppressed for 4 hours after the first fire, warnings for 12 hours. You get notified once, not every 15 minutes.
Quiet hours
If your client’s site sends very few emails at night, you can set quiet hours to suppress non-critical alerts during those windows – avoiding false alarms from low overnight volume.
Webhook integration
Route alerts to wherever your team actually monitors things – Slack, Discord, PagerDuty via Zapier, or any webhook endpoint. You can set a separate webhook for critical-only alerts if you want a distinct high-priority channel.
Catching a broken transactional email on day one is a minor fix. Catching it after three weeks of failed order confirmations is a much bigger conversation. Email Health Monitor makes sure it’s the former.