Skip to main content
Every email the engine sends passes one gate before it leaves. The gate has a short list of addresses that may receive mail. Anything else is not sent to the customer: it is sent to the owner instead, with the intended address written into the subject. This page is the one home for that rule; Resend and Emails we send point here.

​
The three outcomes

There is no fourth outcome. A mistake in a record, a typo, an old customer email: none of them can reach a person outside the company. The comparison ignores case and surrounding spaces, and an address at the test domain counts only when it is shaped like a real one.

​
A redirected copy is not the customer’s email

The engine keeps a ledger of every email it sends, so nothing goes out twice. A copy the gate redirected to the owner is written in that ledger as redirected, not as sent: the customer has not had it, and the send is still owed. What happens next depends on the kind of email.
  • Reminders (the day-before appointment reminder, the two invoice reminders) are found again by their daily sweep while the redirected copy stands. The sweep marks the earlier copy superseded and sends again under a fresh ledger entry, and the owner gets another TEST copy, once a day, until the gate lets the real one through.
  • Everything else (a booking confirmation, an invoice, a receipt, a quote, an invite) is sent once. A redirected copy counts as done for these, and asking for the same send again sends nothing.

​
Turning it on for real

Widening the allowed list is a decision, not a setting. The list and the test domain live in the engine’s code, and changing either is a code change that goes through review, so nobody can flip it in a hurry. The monitor treats a redirected send as delivered, so the redirect never shows as a delivery problem.