How to Get Technicians to Ask for Reviews (Scripts + a Leaderboard That Works)

The way to get technicians to ask for Google reviews is to stop treating the ask as a personality trait and start treating it as a job step. In ProsperQR's home-service data (part of 816,307 reviews across 3,739 US local businesses), the median field-service business collects just 2 new reviews a month while the busiest 10% collect 8, and the gap isn't charm. It's whether the ask happens on every job or only on the jobs where somebody remembered. By the end of this post you'll have five scripts your techs can say at the door, a way to make asking automatic, and a leaderboard format that keeps it going without you nagging anyone.

Why technicians don't ask (it's not a personality problem)

Your techs skip the ask for two reasons, and neither is laziness. First, it feels like begging — a tech who just crawled through an attic doesn't want to end the job sounding like a telemarketer. Second, nothing requires it: the close-out has payment, photos, and a signature, and the review ask lives in nobody's workflow. So it happens when a tech feels bold and vanishes when the day runs long.

There's a third problem that sits with you, not them. Most owners have no idea which techs ask and which don't. Reviews trickle in, someone gets a nice mention, and that's the whole picture. You can't coach a behavior you can't see, and you can't celebrate the tech who asks on every single job if the data never makes it back to you. The scripts fix the awkwardness. The checklist fixes the forgetting. Attribution fixes the blindness. Take them in that order.

5 scripts technicians can say at the door

The words matter less than having words. Every script below is short, plain, and ends with something physical to do — tap a card, scan a code, watch for a text. Have each tech pick the one that sounds like them and say it the same way every time.

1. The default. For the last minute of any normal job:

"Glad we got that sorted. If you've got 20 seconds, a quick Google review really helps a small crew like ours. You can tap my card right here."

2. The name ask. Best one on this list, because it gives the customer a reason that's about the tech, not the company:

"If you're happy with the work, a quick Google review would mean a lot. Mention my name — it's Marcus — so my boss knows I took care of you."

Customers like doing a specific person a specific favor. And every review that names a tech is attribution you didn't have to build.

3. The boss deflection. For techs who hate asking. It moves the awkwardness onto you, where it belongs:

"Last thing on my checklist — my boss asks me to offer every customer a quick way to leave us a Google review. Here it is if you've got a minute."

Nobody resents a tech following a checklist. This one turns your most reluctant asker into an asker.

4. The invoice tie. For techs who'd rather point at a screen than make a speech:

"I'm sending your invoice over now. There's a review link right under the total — if we did right by you, it takes about 20 seconds."

Pair it with a same-day text; the review request text templates cover that half of the play.

5. The repeat customer. For maintenance plans and second visits:

"You've had us out a few times now. If you've never left us a Google review, one from a long-time customer counts for a lot."

Repeat customers are your happiest and your least asked, because everyone assumes someone else already did.

Make the ask a job step, not a favor

Put the ask on the job-completion checklist, in writing, between "collect payment" and "leave the work area clean." If you run Jobber, Housecall Pro, or ServiceTitan, add it as a required close-out item so a job literally isn't done until the tech marks the ask made. That checkbox is also your data: asks per tech per week, straight from software you already pay for.

Then keep it visible. Mention the count at the Monday meeting the same way you'd mention callbacks — not as a scolding, as a scoreboard. The mechanism here is boring and it's the whole point: what gets checked gets done, and what gets mentioned weekly stays checked. The HVAC playbook covers the two moments in a job where the ask converts best; the checklist is what makes those moments happen on every job instead of some.

One rule as the manager: never punish a low review count. Punish nothing, actually — the whole system runs on the ask, and the ask is the only part a tech controls. A customer who says "sure" and never opens their phone is not your tech's failure.

How to track which technician got the review

Here's the honest mechanical problem: Google gives your business exactly one review link. Every tech shares it, so the link alone can never tell you who earned the review. You have three real options, in rising order of effort-saved.

Count name-mentions. Use the name-ask script above, then tally reviews that mention each tech in a spreadsheet once a week. Free, and it doubles as reply material — respond to the review and name the tech again. The catch: plenty of happy customers forget the name, so you'll undercount your best askers.

Give each tech their own link. Point separate short links or printed QR codes at the same Google review form, one per tech, and check each link's scan count. Now you can see who's generating taps, though a free shortener still can't connect a specific scan to the review that followed.

Use per-tech cards built for this. This is the part ProsperQR was built for, so read this paragraph knowing we sell it: every tech carries their own named tap card, every scan logs to that tech automatically, and the field-teams dashboard shows asks and the reviews that follow per technician, no spreadsheet. If you'd rather assemble it yourself, our free review QR generator gets you the one-tap link and you can run the tracking manually. Both work. One costs time, one costs money.

How to run a review leaderboard for employees

A leaderboard works when techs believe it's fair. Four rules keep it that way.

Score the ask, not the review. The main number is asks per completed job — checklist completions or card scans, whichever you track. Reviews and name-mentions are the bonus column, not the headline. A tech can control asking on 100% of jobs; they can't control whether a tired homeowner follows through that night. Score what they control and the leaderboard reads as effort, not luck.

Normalize by job count. Raw totals rig the game for whoever runs the most calls. An installer doing two jobs a day can't out-ask a maintenance tech doing eight, so rank on rate: asks divided by jobs. Your FSM already has the denominator.

Reset monthly. A month is long enough to smooth out a bad week and short enough that a slow starter re-enters the race twelve times a year. Do a lightweight shout-out weekly and settle the prize monthly. A yearly contest crowns your best asker once and demotivates everyone else by March.

Keep prizes modest and frequent. I won't invent a magic dollar figure, because there isn't one — the sizing rule is simpler than that. The prize should be worth winning and not worth cheating for: a gift card, a paid half-day, first pick of the schedule, the good parking spot. If a prize is big enough that faking a review starts to look rational, it's too big. Small, monthly, and public beats large, annual, and forgettable.

For variety across the year: run rookies against veterans in separate divisions, pair crews into teams for a quarter, or give a bonus point when the customer mentions the tech by name. The name-mention bonus is the sneaky-good one — it rewards the exact script that also solves your attribution problem.

Never incentivize the customer

One bright line holds all of this up. Google's review policy bans offering "incentives – such as payment, discounts, free goods and/or services – in exchange for posting any review," and separately bans selectively soliciting positive reviews — that's the policy text as of July 2026, on Google's prohibited-content policy. Asking is explicitly fine. Paying the reviewer, in any form, is not.

Notice what that means for your leaderboard: paying your own technician for making the ask is a payroll decision, and it's entirely yours. The customer gets nothing either way, so the review stays genuine and the policy stays satisfied. The line gets crossed the moment a tech, chasing a prize, tells a homeowner "leave us five stars and I'll knock ten bucks off" — which is one more reason to score asks instead of review counts. The full breakdown of what's banned and what happens when businesses try it is in our post on review incentives and Google's rules.

Your techs already earn the ratings — home-service businesses average 4.8 stars in our review data, the second-highest of any industry. What they don't do yet is ask on every job, and everything above exists to change exactly that. Script, checklist, scoreboard. The reviews follow.