The reason most owners haven't automated anything customer-facing is not that they doubt the value. It's that they can picture, exactly, the message that goes out wrong — a price quoted a thousand dollars low, a refund promised to the wrong person, a warranty answer that turns into a claim. That picture is accurate. Every system we design starts from the assumption that it is.
A gate is a list, not a feeling
The design pattern is old and unglamorous, which is why it holds up. The system carries an explicit list of actions it is allowed to take on its own — confirm an appointment, answer a question about business hours, send directions to the shop. Everything not on that list gets drafted and held. The draft appears on a phone a person already checks — the office manager's, usually — showing the message, the customer it's addressed to, and the source it was built from. One tap approves it. One tap opens it for editing. Nothing customer-facing leaves the building without a human deciding it should.
"Drafted and held" is doing the real work in that paragraph. The machine does the part it's good at: pulling the price from the price book, finding the clause in the warranty document, writing a clean first draft at nine on a Tuesday night. The person does the part only a person should do — deciding that this specific message goes to this specific customer.
The actions that stay gated, by name
Gates are only useful if they're specific, so here is the default list we would start any engagement with:
- Any message that quotes a price. Not just large prices — any price.
- Any refund, credit, or discount, at any amount.
- Anything sent to a customer above a dollar threshold the owner sets. A $79 diagnostic confirmation might flow automatically while a $7,400 replacement quote never will.
- Anything addressed to an insurance adjuster.
- Appointment changes that touch another customer's slot.
The adjuster line deserves a sentence of its own. After a hailstorm, a roofing company's supplement letter is a negotiating document. The system can assemble a draft from the scope notes and the Xactimate line items, and that draft saves an hour of writing — but it is read, edited, and sent by a human, every single time, because the counterparty is a professional whose job is to find the weak sentence.
The distinction worth noticing across the whole list: the after-hours system can confirm a Tuesday 9am slot on its own, because the failure mode of a wrong confirmation is an apologetic phone call. The failure mode of a wrong price is a customer holding you to it.
"I don't know" is designed behavior
When the system answers questions from your documents — warranty terms, service policies, the price book — it answers only from what it actually finds there. If a homeowner asks whether the 30-year shingle warranty covers wind damage on a low-slope tear-off, and the retrieval step comes back with nothing that addresses that specific combination, the correct output is not a plausible guess. It is: "I want to get you an exact answer on that — I'm flagging it for the office, and someone will confirm with you today."
We treat that abstention as a success, and we count it as one. A general-purpose model asked the same question would produce a confident paragraph assembled from what roofing warranties usually say — which is precisely the behavior that makes owners distrust this entire category of software. The threshold deciding "answer" versus "abstain and route to a person" is set conservatively on day one, and for questions involving money or coverage, it never comes down.
The audit log
Every draft, sent or not, is stored with the same fields: what it said, which document or price-book line it drew from, who approved it, when, and whether they edited it first. It is a small table, and it earns its keep two ways.
First, disputes. When a customer says in October that "your text in August said the repair was covered," you don't reconstruct anything from memory. You pull the entry, and it shows the exact wording and the clause it cited. Second, tuning. The office manager's edits are a running record of everywhere the drafts fall short of how your shop actually talks to people. Three weeks of edits will tell us more about your voice than any onboarding questionnaire could.
Gates loosen on evidence, not optimism
Everything starts gated. That is slow, on purpose. After a few weeks, the log will show which categories the approver waves through untouched — routine confirmations, hours, and service-area answers are the obvious candidates to graduate first. A category moves to automatic only when the log justifies the move, one category at a time. Quoted prices and refunds don't graduate. Some things stay gated for the life of the system, and the point of the architecture is that this is a per-category dial the owner controls, not a philosophy the vendor imposes.
What this does not solve
Approval gates add latency. If the office manager is at lunch, the draft waits, and a held reply at 12:40 is slower than an instant wrong one. For most messages that trade is obviously right. For a burst-pipe caller it isn't — which is why emergency paths bypass drafting entirely and bridge straight to a phone.
Approval fatigue is real. Forty drafts a day turns approval into rubber-stamping, and a rubber stamp is worse than no gate, because it looks like oversight without being any. The fix is graduation: automate the routine categories so the human's attention is spent on the handful that involve money.
And a gate cannot fix bad source data. If the price book is eight months stale, the system will draft confidently wrong quotes from it, and the gate only helps if the approver catches the number. Keeping the documents current remains the owner's job. The gate is a checkpoint, not a substitute for one.
Where to start
Write down the messages you would never let a new hire send in their first week without showing you first. Most owners can produce that list in five minutes, and it is, almost verbatim, the gate configuration. Bring it to a first conversation and we'll walk through what runs automatically in your shop, what gets held, and what the approval screen looks like on the phone you already carry.