What is Always Alert?

Learn what Always Alert protects, how it works with WordPress email, and where its responsibility ends.

Written By Kelsey

Last updated About 1 month ago

Always Alert is form notification assurance for WordPress. It adds a fallback recipient to eligible outgoing form notifications before WordPress hands each message to the site’s existing mail system.

It gives agencies, freelancers, maintainers, and site owners a second path for important enquiries and a way to notice when a site has gone unexpectedly quiet.

The problem it solves

Form notification problems are often silent. A recipient address changes, a form setting drifts, or an update changes behaviour. The form may still appear to submit successfully while nobody notices that expected enquiries are missing.

Always Alert provides two layers of assurance:

  1. Fallback copies: a configured address is added to eligible notifications, using BCC by default.

  2. Activity monitoring: the plugin records notification metadata and can report when eligible activity was last observed, alert when a site goes quiet, and send weekly summaries.

How it fits into your email setup

Always Alert works before the mail transport stage:

  1. A supported form or other WordPress process prepares an email.

  2. Always Alert decides whether that message is eligible.

  3. It adds the fallback recipient when appropriate and records a metadata-only activity event.

  4. WordPress passes the message to the site’s existing mail setup.

That existing setup may be native WordPress mail, an SMTP plugin, hosting mail, or a transactional email provider.

What Always Alert does not do

Always Alert does not:

  • send mail independently;

  • replace an SMTP or transactional email provider;

  • repair DNS, SPF, DKIM, or DMARC configuration;

  • control mailbox spam filtering or inbox rules;

  • prove that a message arrived in an inbox;

  • discover and audit every form configuration;

  • store form submissions or attachments by default.

A successful handoff means WordPress accepted the message for sending. Final delivery still depends on the rest of the mail chain.

Main features

  • A global fallback recipient.

  • Form Notification Mode for targeted coverage.

  • Universal wp_mail Mode for broader oversight.

  • BCC, CC, or To copy methods with duplicate prevention.

  • Source attribution for common form plugins and selected page builders.

  • A health dashboard, admin-bar status, and WordPress dashboard widget.

  • No-activity alerts and weekly digest reports.

  • Temporary post-launch monitoring with per-notification heartbeats.

  • Temporary emergency oversight.

  • A metadata-only activity log with configurable retention.

  • Privacy information and WordPress personal-data export and erasure support.

Recommended next step

Install the plugin, configure one monitored fallback inbox, keep Form Notification Mode and BCC selected, and run a Mail Handoff Test. Then submit each important public form once and confirm both the normal notification and the fallback copy behave as expected.

Related articles

/