Most staff don't avoid asking for reviews because they're lazy. They avoid it because nobody gave them the words, and improvising a request on the spot feels like begging. Fix the words and the timing, and asking stops being the awkward part of the shift.
Give them a line, not a philosophy
"Please ask happy customers for reviews" is a policy, not a script. Nobody can act on it mid-shift. What works is a specific line staff can say without thinking: "Glad that worked out. If you have a second, a Google review helps other people find us; here's the code." Fifteen words, said the same way every time, handed to a customer who is already standing there.
Write two or three versions for different moments (checkout, end of service, handing back a repaired item) and have the team pick whichever fits their own voice. A script that sounds robotic gets skipped; one a person can say naturally gets used.
Ask everyone, not just the customers who seem happy
Here's where a lot of "review training" advice quietly crosses a line: it tells staff to watch for compliments, then only ask the customers who gave one. That's selective solicitation, and Google's policies treat asking only satisfied customers for public reviews as review gating, whether or not anyone intends it that way. See our breakdown of the gating policy for exactly where that line sits.
The fix isn't complicated: ask every customer, the same way, every time. The customer decides what to do with the ask, not your staff. That's also the reason a rating-first flow works better than a verbal filter: the star tap happens before anyone chooses where the feedback goes, so the same code goes out to everyone regardless of how the visit seemed to the person handing it over.
Timing beats wording
The best-worded request at the wrong moment gets ignored. Ask while the customer is mid-transaction, wallet or keys already out, not as they're halfway out the door. At a counter, the natural window is the payment moment. For a service call, it's the handoff, right after the job is explained and before the technician leaves. Waiting until later, an email the next day, a text that evening, always converts worse than asking in person while the interaction is still live.
Make asking easy to remember, not easy to skip
Telling staff to "remember to ask" competes with everything else on their mind during a shift. Put a physical or printed cue where the ask naturally happens: a small card by the register, a line on the receipt, a code taped near where the transaction happens. The prompt for the staff member matters as much as the prompt for the customer.
Role-play the script once during onboarding and again after a slow week when habits slip. Two minutes of practice, out loud, with a coworker playing the customer, works better than a written policy nobody rereads.
What a "no" should look like
Train the response to a decline as carefully as the ask itself. "No problem, thanks for coming in" and moving on is the entire required reaction. Staff who feel like a refusal reflects on them personally will either stop asking altogether or start pushing a second time, and a second ask reads as pressure to the customer and as pestering to anyone standing nearby. Normalize the no in training: most customers will skip it, and that's fine, because the ones who do respond are the ones worth having.
Attribution changes behavior more than instruction does
Telling someone to ask for reviews is a rule. Showing them their own name next to their own review count is a reason. When each staff member has their own code and can see how many ratings and how many five-stars trace back to them specifically, asking stops being a chore imposed from above and starts being something they track themselves. We've written about why naming the person behind every rating changes the dynamic more than any script does.
That's the part a generic "ask for reviews" policy can't replicate on its own, and it's the piece Starboard's staff leaderboard is built around: one QR code per person, so every ask is traceable and every result is visible to the person who earned it.
Give the team a script, a moment to use it, and a reason to keep using it. The wording matters less than making sure every customer gets asked the same way.