The short answer
Make the ask part of the job, not a favor: give staff one specific moment (right after payment), one sentence to say, and a one-tap way to send the customer your review link — then measure by the name-mentions in the reviews that come in. Reward employees for asking consistently, never per review collected, and remove the remembering entirely by triggering the request from the payment itself.
Why 'remember to ask' always fails
Every owner has given the speech — we need to ask for reviews — and every crew nods along. Then Tuesday gets busy, the customer is on the phone during checkout, the tech feels weird asking for a favor after handing over a big invoice, and the ask quietly stops happening. Not because anyone disagrees; because remembering is the worst possible mechanism for something that has to happen on every job.
There is also no feedback loop. When a review arrives three days after the visit, nobody connects it to the tech who did the work, so the people doing the asking never see the result. A policy with no moment, no script, and no scoreboard is not a policy — it is a hope.
A team policy that actually sticks
Pick one moment and make it universal: the ask happens when the job wraps or the payment lands, every time, for every customer — not just the visibly delighted ones (cherry-picking who gets asked is review gating, which violates FTC rules and Google policy). Tie the ask to a moment that already exists in the workflow and it stops depending on mood or memory.
Give them one sentence, not a pitch: "You'll get a text from us with a review link — if we did a good job, it means a lot if you tap it." That framing does the hard part for the employee: they are not asking for a favor on the spot, they are flagging a message the system is about to send. Pair it with a one-tap way to actually send the link — a quick-send page saved to each phone beats anyone typing numbers into anything.
Then build the scoreboard. Customers routinely name the person who did the work — read new reviews aloud at the weekly meeting, credit the named tech, and the asking reinforces itself. Recognition for name-mentions is the cheapest incentive in this business, and it is entirely within the rules.
Incentives: what is safe and what backfires
Paying for the behavior is safe: a bonus for consistently asking, for keeping the streak, for name-mentions as a sign of service worth reviewing. The employee controls whether they ask; they should be rewarded for what they control.
Paying per review collected is where trouble starts. An employee paid per review has a direct incentive to steer only happy customers toward the link (that is review gating), to pressure customers on the spot, or — the version that gets listings penalized — to post reviews themselves or recruit friends to. A per-five-star bonus makes it worse: you have now priced a specific rating, and somewhere between the employee and the customer that pressure becomes filtering, scripting, or faking. Google prohibits all of it, the FTC's consumer-review rule carries real penalties, and the employee bearing the incentive is not the one who bears the risk — the listing is.
The better fix: remove the human step
The strongest version of this policy needs no willpower at all. ReviewNudger connects to the software where you get paid — Jobber, Square, QuickBooks, Stripe, Housecall Pro, or thousands of apps via Zapier — and can send one neutral review request by text after each completed payment, with a follow-up if there is no response. For cash jobs no software saw, staff open a quick-send link on their phone, type a name and number, and the same request goes out. The employee's job shrinks to one friendly sentence; the system does the asking, every time, for $29 a month flat.
Frequently asked questions
Should employees ask in person, or should the text do it?
Both, in that order. The in-person sentence primes the customer ("you'll get a text from us"), and the text delivers the actual one-tap link. In-person alone loses people who agree politely and forget; text alone converts fine but converts better with the human heads-up.
Can I pay my employees for each review they bring in?
Pay for asking, not for reviews. A per-review or per-five-star bonus gives the employee a reason to filter out unhappy customers, pressure people, or fake reviews — and those violations land on your listing, not on them. Bonus the behavior they control: asking every customer, every time.
How do I know which employee is generating reviews?
Read the reviews — customers name the person who did the work more often than not. Name-mentions per tech is a fair, gaming-resistant scoreboard, and reading them aloud at the weekly meeting doubles as the recognition that keeps the asking habit alive.
What if my staff hate asking?
Shrink the ask until it stops feeling like one. Nobody has to request a favor — they mention that a text is coming and let the message do the work. Techs who would never say "please review us" will happily say "you'll get a text from us shortly."