The short answer
Make the ask part of the job, not a favor. Give staff one moment (right after payment), one sentence to say, and a one-tap way to send your review link. Then track how often reviews mention them by name. Reward employees for asking every time, never per review collected. Best of all, remove the remembering. Start the request from the payment itself.
Why 'remember to ask' always fails
Every owner has given the "we need to ask for reviews" speech, and every crew nods along. Then Tuesday gets busy. The customer is on the phone during checkout. The tech feels weird asking a favor right after handing over a big invoice. The ask quietly stops. Nobody disagrees with it. Remembering is just the worst way to make something happen on every job.
There’s also no feedback. When a review arrives three days after the visit, nobody ties it to the tech who did the work. So the people asking never see the result. A rule with no moment, no script, and no scoreboard isn’t a rule. It’s a hope.
A team policy that actually sticks
Pick one moment and use it everywhere. The ask happens when the job wraps or the payment lands. Every time, for every customer, not just the clearly delighted ones. Picking who gets asked is review gating, which breaks FTC rules and Google policy. Tie the ask to a moment that already exists in your day. Then 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 you would like to share an honest review, the link is there." That does the hard part for the employee. They aren’t asking a favor on the spot. They’re pointing out a message that’s about to arrive. Pair it with a one-tap way to send the link. A quick-send page saved to each phone beats anyone typing numbers into anything.
Then build the scoreboard. Customers often name the person who did the work. Read new reviews aloud at the weekly meeting and credit the named tech. The asking then feeds itself. Recognition for name-mentions is the cheapest reward in this business, and it’s fully within the rules.
Incentives: what is safe and what backfires
Paying for the behavior is safe. Think a bonus for asking every time, for keeping a streak, or for name-mentions as a sign of service worth reviewing. The employee controls whether they ask. Reward them for what they control.
Paying per review collected is where trouble starts. An employee paid per review has a reason to steer only happy customers to the link. That’s review gating. They may pressure customers on the spot. Worse, they may post reviews themselves or get friends to, which gets listings penalized. A bonus per five-star review is worse still. You’ve now put a price on a rating. Somewhere between the employee and the customer, that pressure turns into filtering, scripting, or faking. Google bans all of it, and the FTC's consumer-review rule carries real penalties. The employee gets the bonus, but the listing carries the risk.
The better fix: remove the human step
The best version of this rule needs no willpower at all. ReviewNudger connects to where you get paid: Jobber, Square, QuickBooks, Stripe, Housecall Pro, or thousands of apps through Zapier. After each paid job, it can send one review request by text, with a follow-up if there’s no response. For cash jobs no software saw, staff open a quick-send link on their phone and type a name and number. 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.
