We plan to extend the current single fallback address into more flexible assurance routing.
Possible capabilities include:
multiple fallback recipients;
different recipients for operations, reporting, or departments;
recipient and domain-based rules;
clearer duplicate-prevention reporting;
safe defaults that keep BCC as the normal private-copy method.
The goal is to support agencies and larger organisations without turning Always Alert into a CRM or general email automation tool.
Additional recipients can expose form content to more people, so routing controls will be designed with explicit access, privacy, and volume warnings. Always Alert will continue to operate before the existing WordPress mail transport and will not replace SMTP or determine final inbox delivery.
Please authenticate to join the conversation.
In Review
Feature Request
About 1 month ago

Kelsey
Get notified by email when there are changes.
In Review
Feature Request
About 1 month ago

Kelsey
Get notified by email when there are changes.