One catalogue of thirteen customer-facing messages covering estimates, intake, form reminders, contracts, project start, stage and checkpoint updates, photo updates, completion and missed-call text-back. Each entry states when it fires, which channels it supports, and whether it is live. Each can be switched off per account, and its wording replaced.
Also called: turn off automatic emails · what does the system send my customers · notification settings · too many emails to customers
Thirteen automatic customer messages, listed, each with its own switch
Estimate ready, contract to sign, project starting, stage complete, photo update, completion — every message the platform can send a customer is in one list that states when it fires. Turn one off without turning off the rest. Software that messages your clients on your behalf and will not show you the list is a black box bolted to your reputation.
Change what any of it says, and it still comes out looking like your business
Title, body and button label are yours to replace, and custom copy rides the branded layout so nothing looks like it came from somebody else's software. View email shows the real thing with sample values rather than a cramped preview, and the original wording is restorable at any point.
A new kind of message never surprises a customer base that is already live
The chatty classes — one per checkpoint, one per photo — default to off, and the account turns them on deliberately. If the preferences cannot be read for a moment, a send falls back to the default rather than going silent on customer mail.
Send the same update as a text, written as a text
Any message in the catalogue can also go out as an SMS, composed from its own wording instead of a shortened email — a text has no subject line and no layout to lean on, and gets read on a lock screen. Texting stays off until you say yes per message, because a text costs money and lands on a personal phone the customer never agreed to give you.
A text with a blank where a value should be is not sent at all
If any placeholder cannot be filled the text is cancelled and the missing value is logged for you instead. ‘Your estimate for is ready’ just looks broken to the customer, and there is no unsending a text.
- 1One registry so the notifications grid, the composer and the send paths agree on what exists
- 2A send naming its message key is gated on the account's switch, and skips quietly when it is off
- 3Absent preference row = the registry's own per-key default; noisy new classes (per-checkpoint, per-photo) ship OFF so they never surprise a live customer base
- 4Preferences are cached 60 seconds per account, and a prefs outage fails to the default rather than silencing customer mail
- 5Statuses are honest: 'elsewhere' entries say which other screen controls them
The messages this platform sends on a builder's behalf go out under the builder's name, so "what exactly does this thing say to my customers" has to have a complete answer in one place. Without one, the settings screen and what actually gets sent drift apart, and the builder finds out from a customer. Every customer-facing message — estimate ready, contract to sign, stage complete, photo update and the rest — is listed with its own switch and editable wording, and any new noisy class arrives switched off so a live customer base is never surprised by it.
- Automated customer messaging as a black box
- All-or-nothing notification control
- New message types appearing without warning
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 →