The work's done, the truck's back at the shop, and the invoice goes out four hundred dollars over the quote. You know exactly why. Your tech had the unit open, found a blower motor seized solid, swapped it so the job wouldn't drag into a second trip, and kept moving. Good instinct.
Three weeks later, the customer doesn't see it that way. They're staring at a number nobody warned them about, and now it's a phone call, or worse, a short-pay where they cut a check for the original quote and dare you to chase the rest. You either eat the difference or you spend a week fighting for money you already earned.
There's a better spot to have this conversation, and it isn't the invoice. It's the moment your tech first sees the extra work, while everyone still agrees the unit's broken and something has to happen. Settle the change order right then, in one line, before the wrench turns.
The invoice is the worst place to explain yourself
By the time an invoice lands, the work is finished and the money is spent. The customer can't say no to something that's already done, so instead they feel cornered, and cornered people go looking for a reason not to pay. That "misc. repair, $400" line hands them one.
Approval works the other way around. Ask before the work happens and you're offering a choice, not presenting a bill. Most customers say yes, because the alternative is a unit that still doesn't cool. The few who say no just saved you from doing unpaid work you'd never have collected on.
The whole game is moving the yes earlier. From weeks after, when it's a fight, to minutes before, when it's a favor.
The text that settles it: one line, one price
Your tech doesn't need to write a proposal from the field. He needs to send one text the customer can read between meetings and answer with a thumbs up. Scope, price, reason, done.
Something like: "Found a seized blower motor on your rooftop unit, that's why it's not cooling. Replace it for $420 today while I'm here, or I close up and we quote a return trip. Want me to go ahead?"
That's the whole thing. It names the problem, gives one number, offers the real choice, and asks a question they can answer in one word. A good field approval text has:
- A plain-English scope. "Seized blower motor," not "amperage draw exceeding nameplate." Say what broke and what you'll do about it.
- One price, all in. Parts and labor together. Don't make them do math on their phone.
- The reason it matters now. Tie it to what they care about: cooling, downtime, a second truck roll in July.
- A clear question. End with "go ahead?" so the reply is one word instead of a paragraph.
Get the yes you can point to later
A text back that says "yes, go" is gold. It's dated, it's in their own words, and it settles any argument before it starts. That's what "in writing" really buys you: not formality, just a record nobody can wave off three weeks later.
Phone approvals happen too, especially with customers who'd rather talk. That's fine, take the call. Right after, send a quick confirming text: "Thanks, confirming you approved the $420 blower motor we just talked about. Starting now." The verbal yes now has a paper trail, and you gave them a chance to correct it if you heard wrong.
Skip the approval and you're back to guessing later whose memory is right. Yours usually is. Doesn't matter, if you can't prove it.
Log it to the job before the wrench turns
An approval sitting in a tech's phone does nothing for the person cutting the invoice. If the office can't see the yes, they can't bill it with confidence, and it becomes "did the customer actually okay this?" every single time.
The move is to attach the scope and the approval to the job ticket the moment they come in, before the work starts. Office sees the change order, the invoice matches what the customer agreed to, and the whole thing is closed out before your tech touches a tool.
This is where a simple setup earns its keep. When the tech sends that approval text, the reply gets captured, timestamped, and dropped onto the job, so nobody's forwarding screenshots at 6 PM or retyping a price into the invoice by hand.
Where AI helps, and where it doesn't
A small automation can carry the boring parts of this flow. From a few taps in the field, it can draft the approval text in your standard format, send it, watch for the reply, and log the yes to the job with a timestamp. It can also nudge a tech who's closing out a ticket with extra parts on it and no approval attached.
Here's the honest limit: none of that decides whether the work is actually needed. Reading the unit, judging the fix, and setting a fair price is your tech's job, and it stays his job. Software can misfire, too, when a customer replies with something fuzzy like "how much again?" It should flag that a real answer is needed, not guess that a question mark means yes.
So let it handle the format, the sending, the capture, and the filing. Keep a person on the judgment call and on any reply that isn't a clean yes.
Worth doing this week
You don't need software to start. You need a habit your crew actually follows, and you can wire up the automation once the habit sticks.
- Write your one-line template. Scope, price, reason, question. Print it on a card for the trucks so nobody's composing from scratch on a hot roof.
- Set the rule: no extra work without a yes in writing. Text or a confirmed phone call, every time, no exception for the "small" ones. Those are the short-pays.
- Pick where the yes lives. One place the office checks, whether that's the job ticket in your software or a shared thread. Not a personal phone.
- Do a dry run on the next real find. Have a tech send the text, confirm the reply, and log it before starting. See where it snags.
- Then automate the capture. Once the flow works by hand, a setup like the ones we build at AI Agency Houston can send, timestamp, and file the approval for you, so it runs the same way on a quiet Tuesday or during a storm-season scramble.
Do this and the change order stops being a fight you have after the fact. It turns into a thirty-second exchange you have while everybody still agrees on what's broken.