Train Your Techs to Ask for Reviews Every Time

Your techs won't ask for reviews because it feels like begging, they forget by the third job of the day, or nobody's ever told them it's actually part of the job. Fix those three things and the reviews follow. This post covers the fifteen-minute training to run at your Monday meeting, the one sentence a tech says at the truck, the card or text trigger that does the rest of the work, what to pay (and not pay) for it, and what to do with the one guy who still won't say it.

This isn't the review system itself. If you haven't built the actual ask-and-text sequence yet, the script, the same-day text, the direct Google link, start with the review system post and come back here once it exists. This post is about getting the people who run that system to actually use it, on every job, not just the ones where they happen to remember.

None of this requires a personality transplant for your quietest tech. It requires one sentence, one card in the truck, and a Monday habit you check for four weeks straight. I've watched owners build the entire review system, the script, the text, the link, and get almost nothing back because nobody ever taught the tech to say the sentence out loud.

Why Your Techs Don't Ask for Reviews

Ask a tech why he doesn't request reviews and you'll get some version of three answers: it feels like begging, he forgets, or nobody's ever told him it's worth the ten seconds. None of the three is a character flaw. All three are fixable with training and a system, which is the rest of this post.

It Feels Like Begging

To a tech, asking for a review can feel like asking a stranger for a favor. It isn't. According to BrightLocal's 2025 Local Consumer Review Survey, 96% of consumers are open to writing a business a review. Your tech isn't imposing on a reluctant stranger. He's failing to ask someone who was already willing, at the exact moment they had the best reason to say yes.

He Forgets

Between the drainfield, the invoice, the next address on the route, and the customer's questions, remembering to mention a review is easy to drop. There's usually nothing in the truck reminding him, nothing on a checklist requiring it, and no consequence when it doesn't happen. Forgetting isn't a discipline problem. It's a missing trigger, which is what the QR card and checklist further down fix.

Nobody's Told Him It's His Job

If asking for reviews lives only in your head as something you wish happened, it competes with everything else on a tech's mind and loses. Put it on the job completion checklist next to "area cleaned" and "payment collected" and it stops being a nice-to-have. It becomes one more box that has to be checked before the truck leaves the driveway.

The One-Sentence Ask That Doesn't Feel Like Begging

Here's the line: "If you were happy with the work today, would you leave us a quick Google review? I'll have the office text you the link right now so you're not stuck searching for us."

Four things make it work, and none of them require confidence a shy tech doesn't have. It's conditional, "if you were happy," so he's never asking someone who isn't. It names the specific platform, Google, instead of the vague "a review," so the customer isn't left guessing where. It hands the mechanics to the office, so the tech's job ends the moment he stops talking. And it takes under ten seconds, which matters more than any of the wording.

That conditional word is doing real work. A tech who asks an unhappy customer anyway isn't just wasting the ask, he's inviting the exact negative review a satisfied customer would never have left. If one slips through despite the conditional, don't panic and don't argue with it in public; how to handle a negative review covers the response that actually protects the account.

Some techs will say it exactly as written. Others will soften it: "If you have a minute later, a Google review would help us out a lot. We'll text you the link." Both work as long as the four elements survive: conditional, specific platform, hands-off mechanics, short. Let a confident tech assume the yes and a quieter one ask more gently. The exact phrasing matters less than the shape of it.

The 15-Minute Monday Training

Fifteen minutes at your Monday meeting turns that sentence from words on a whiteboard into something a tech says without flinching. Run this block every Monday for a month, then drop to monthly once ask rates hold steady on the tracking sheet below.

The role-play is the part owners are tempted to skip, and it's the part that actually changes behavior. Reading a script silently and saying it out loud in front of a coworker are two different skills. The awkwardness lives in saying it, not in knowing it, so that's the rep you have to run.

The QR Card or Text Trigger

The sentence is the tech's whole job. Everything after it should happen without him.

Two setups do this. A laminated card with a QR code that opens the Google review link directly, kept on the dash or handed to the customer at the truck. Or a text keyword the tech flags, or the office fires automatically off the completed job, so the same-day link goes out without the tech typing a URL or explaining anything technical. Either way, the tech's only actions are saying the line and pointing at, or tapping, the trigger. He never manages a link, a code, or a follow-up.

Keep the card and the checklist step in the same place a tech already looks, the dash, the clipboard, the job app, so it survives being new and becomes just part of the truck.

Pay for the Ask, Not the Review

You can pay your tech for asking. You can't pay a customer for what the review says. Those are two different rules, and mixing them up is where owners get nervous over nothing or, worse, walk into the one that actually carries risk.

A flat bonus to your own employee for doing part of his job, asking every customer, isn't a review incentive at all. It's payroll, tied to a behavior he fully controls. Where it gets risky is rewarding only the outcome: paying per review received, paying only for 5-star results, or discounting a customer specifically for leaving glowing feedback. That's the territory the FTC actually polices.

In practice, keep it simple: a small flat amount, something like a few dollars a day, for full checklist compliance on the review-request line. No per-review math, no sentiment attached, nothing a lawyer would need to look at twice. If you also run a customer-facing incentive, a discount for referrals rather than reviews is the safer lane; see how a referral program is structured to keep that one clean too.

Track Asks vs. Reviews, Per Tech

One sheet, updated weekly, tells you everything you need to know: who's asking, who isn't, and whether asking is actually turning into reviews.

Tech B is the sheet doing its job. Nineteen jobs and only six asks logged means thirteen customers who never heard the sentence, not thirteen customers who said no. That's a training conversation this week, not a mystery to puzzle over next quarter. The office can pull "asks logged" straight from the checklist box or a CRM tag; matching reviews to techs works off the date a job closed or a customer naming the tech directly in the review text.

The sheet also tells you something local search rankings care about: total review volume and how fast it grows. A crew asking on 90% of jobs instead of 30% doesn't just make individual techs look better on this sheet, it changes how fast your review count climbs relative to the two or three competitors you're actually ranked against.

The Tech Who Still Won't Ask

If a tech has sat through the training, run the role-play, has the card in his truck, and his ask rate still sits near zero after a month, that's not a training gap anymore. That's a performance conversation.

Start by ruling out legitimate friction: a route with mostly non-English-speaking customers, dead cell zones where the text trigger won't fire, or jobs that consistently end with an unhappy customer through no fault of the tech. If none of that explains it, have a direct one-on-one. Ask what's actually stopping him rather than guessing. Set a written expectation with a specific ask-rate target and a date to check it again, the same way you'd handle any other missed part of the job.

If the number still doesn't move, treat it like you would treat someone skipping the site cleanup or the payment collection step: a documented conversation, then your normal performance process if nothing changes. Don't let one holdout talk you into dropping the standard for the rest of the crew, and don't claw back a team bonus over one person's numbers. Address him individually and let everyone else keep the reward they earned.