A master safety switch on customer messaging

Per-account live / redirect / off modes that can stop or divert automated customer messaging, checked on every single send and failing closed.

What it is

An interlock in front of every automated customer email and text. In redirect mode email is rewritten to a safe mailbox with the intended recipient stamped into the subject and a red banner injected at the top of the body; SMS is suppressed entirely because there is no verified-safe phone number to divert to. In off mode nothing dispatches.

Also called: stop messages going to customers · test mode · redirect emails to me · pause customer emails

See it
A master safety switch on customer messaging
Area
Platform & Admin
Group
Sending
System
Customer Communications
Solves
3 named problems
01NO CACHE — every send re-reads the account's mode, because a cached mode means a flip to redirect can still leak live customer mail for the life of the cache
02FAILS CLOSED — an unreadable account blocks the send rather than assuming live
03The INTENDED recipient is logged in every mode, so you can prove what would have gone out
A redirected email in a mailbox: subject prefixed '[REDIRECTED → customer@example.com]' with the dark-red warning banner at the top of the body. commsGate.ts. Sample data — no customer information appears here.
How it works
  1. 1NO CACHE — every send re-reads the account's mode, because a cached mode means a flip to redirect can still leak live customer mail for the life of the cache
  2. 2FAILS CLOSED — an unreadable account blocks the send rather than assuming live
  3. 3The INTENDED recipient is logged in every mode, so you can prove what would have gone out
  4. 4A redirected message does not resolve or create the real customer's CRM contact
  5. 5Human-initiated sends — a builder typing to a customer and pressing send — are deliberately NOT swallowed
Why we built it

Automated messaging aimed at real customers needs one switch that can stop it, and that switch has to be checked on every single send rather than cached, or turning it off does not take effect when it matters most. Per-account live, redirect and off modes can halt or divert automated customer messaging, and it fails closed. A message a person typed and pressed send on is exempt on purpose: silently swallowing that would leave a builder believing they had replied to a customer when they had not, which is worse than the risk being defended against.

The problem
  • Test traffic reaching live customers
  • No way to pause automation during setup or an incident
  • Silent suppression of a message a human believed they sent
Sound familiar?
What you get
Onboard and test against real data safely
Proof of what would have been sent
A manual reply is never swallowed

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →