One switch per channel for customer messages

Every customer-facing message carries independent Email and Text switches, so you can text them about the estimate and email them the contract.

What it is

A granular on/off per message key, with texting held apart from email and off until the builder says otherwise. Each row states when it fires. Messages managed elsewhere (like missed-call text-back) say so rather than pretending to be switchable here.

Also called: text the customer · email the customer · turn off customer texts · stop the progress emails

See it
One switch per channel for customer messages
Prepared for
Gideon Alt
1140 Ridge Line Rd · Fair Play
Shell package$33,616
Concrete & site$9,760
Doors & windows$6,506
Trim & finish$4,338
Total
$54,220
Signature
A customer message row with labelled Email and Text switches side by side. NotificationsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1Email preference rows live in the customer-message preference table; absent means on.
  2. 2Text preferences are a separate set, absent meaning OFF, because texting is opt-in per message.
  3. 3Both channels compose from the same tokens, so switching texting on does not require rewriting the facts.
Why we built it

The comment states the correction: “A single toggle asked 'should the customer hear about this', when the real question is 'how'. Email and text are independent.” Migration 198 records the original ask: 'some customers may feel annoyed by the frequency… they should be able to opt out'. Migration 224 split the text switch out from the email one.

The problem
  • One switch conflating two channels
  • Texting on by default
Sound familiar?
What you get
Per-message, per-channel control of what the homeowner receives
Texting never happens unless chosen

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 →