In Sacramento, CA, Priya S runs a 3-tech hvac operation. The old software fired a review request twenty minutes after a rough job — straight into the lap of an already-irritated customer.
What was actually bleeding
One tune-up went rough. Twenty minutes after the tech closed it out, the old software fired off an automated review request — right into the lap of an already-irritated customer. The one-star it earned took Priya four months to dig out from under.
What Priya asked us to build
“Suppress the automated review request whenever the tech flags a complication or a difficult customer.”
— Priya S, HVAC — Sacramento, CA
What we built
We built a job-close status checklist. If the tech flags any complication, the automated review request is held back — no ask goes out. There's a manual override so the office can still send one later if the situation cools down.
No flags — closing will send the review request.
How the tool works
The job-close screen below holds back the automated review request the moment a tech flags a complication — so the ask only ever goes to the jobs that earned it.
- At job close, the tech marks whether anything went sideways.
- If a complication or a difficult customer is flagged, the automated review request is suppressed.
- Clean jobs trigger the ask automatically, at the right moment.
- The office keeps a manual override to send one later if the situation cools down.
Reputation control is one module of the Service OS we build. It connects to your job records, dispatch, and customer comms so the right message goes out at the right time — automatically.
What came back
Fourteen months and not a single surprise review. The rating climbed because the asks only go to the jobs that earned them.
That’s not a projection — it’s what changed after we shipped the build.
The tool you just used isn’t a mockup — it’s the kind of thing we build inside our Service OS, one module of a system made for your trade and owned by you. If you’re carrying a version of this problem, the fastest way to see what a system would catch in your operation is to run your own numbers.
The takeaways
- Don’t ask every customer for a review — ask the ones who earned it.
- Let the tech flag a complication at close, and hold the ask.
- Asking only after clean jobs raises the rating on its own.
Ex-Microsoft operations and fractional COO for $5M+ field service operations. He writes about the systems that let trade companies scale without the owner holding everything together by hand.
These are the things we build inside our Service OS.
Every tool in this story is one module of a custom operating system we build for trade businesses — built for your trade, owned by you. Spin up a free OpsVault account and run your own operation through it: the Live Bleed Calculator, the Journey Map, the whole Vault. No credit card, no sales call.