Skip to main content

Can you ask customers to mention your name in a Google review?

Short answer: you can ask for the review, but you can't tell the customer what to put in it. In April 2026, Google tightened exactly this line, calling out requests to include a specific employee's name. A customer who names your tech on their own is still fine. A review request that says "please mention Dave" is the part that now carries risk. Here's the clean version.

8 min read · Updated June 28, 2026

On this page

You can ask for the review. You can't write it for them.

Here's the honest answer most owners are looking for. Yes, you can ask a happy customer for a Google review. No, you should not tell them to mention a specific person by name.

The difference is who chose the words. A customer who writes "Dave was fantastic" because Dave actually helped them is leaving a real review. A customer who writes "Dave was fantastic" because your text told them to is repeating a script. Google's policy is built to tell those two things apart.

If your ask works whether or not the customer remembers a name, you're on clean ground. If your ask only works when the customer inserts the name you handed them, that's the part to fix.

In April 2026, Google named this exact practice.

Google's review rules have always said don't request specific content. The 2026 update made it concrete. In April 2026, Google added language under its rating-manipulation rules aimed at businesses that solicit reviews mentioning a specific employee by name.

This was a direct response to a common tactic. Service businesses had started coaching customers to drop a salesperson or technician's full name into the review, often to feed internal contests or bonus programs. Google now treats that as manipulating the content of the review.

The enforcement side changed too. Google's automated systems now look for patterns, including clusters of reviews that name the same employee with a first and last name. Those reviews can be removed quietly, and repeated violations can put restrictions on the Business Profile itself.

  • Don't instruct customers to include an employee's name in the review.
  • Don't run review contests that reward staff for getting named in reviews.
  • Don't pre-write or script the wording a customer is supposed to copy.
  • Don't put "be sure to mention [name]" on a card, kiosk, or follow-up text.

Scripted names make real reviews look planted.

From Google's side, a wave of reviews naming the same employee looks engineered, because it often is. Real customers don't coordinate. They mention what stuck with them, in their own words, at their own pace.

When fifteen reviews in a row credit "Mike Thompson" by full name, that pattern reads as a campaign, not a coincidence. The irony is that the tactic meant to help your best tech can end up getting genuine reviews filtered out.

And the risk doesn't land on whatever tool or agency suggested the tactic. It lands on your Business Profile. That's the listing your next customer reads before they call.

A customer naming your tech on their own is still a good review.

This is the part that gets lost in the panic. Google did not ban employee names in reviews. People can still write "Sarah at the front desk made this easy" or "ask for Luis, he knew exactly what was wrong." That's a genuine, specific, helpful review, and it's completely allowed.

The rule is about the request, not the result. You can't engineer the name in. You can absolutely earn it.

So the goal isn't to scrub names out of your reviews. It's to stop putting names into your customers' mouths. Let the people who genuinely impressed someone get credited the natural way.

  • Allowed: a customer who chooses to name the person who helped them.
  • Allowed: asking for a review and letting the customer decide what to say.
  • Not allowed: telling the customer which name to include.
  • Not allowed: rewarding staff or customers for name-drop reviews.

"But my customer wants to credit my guy."

Owners ask this one a lot, and it's fair. Sometimes the customer really does want to thank the specific person who saved their weekend. Nothing about the policy stops them.

The line is whether you steered it. If you handed them a card that says "mention Dave for a discount," you scripted it. If Dave did great work and the customer brings up Dave on their own, that's just a good review doing what good reviews do.

The safe move is to make the person memorable through the work, not through the ask. Have your tech introduce themselves. Do the kind of job people want to talk about. Then ask for the review without dictating a single word of it.

Ask for the review. Seed the topics. Leave the words alone.

There's a version of this that gets you specific, detailed reviews without touching scripted content. Instead of telling the customer what to write, help them remember what happened.

A good review request points them at the experience, not at a sentence. What stood out about the visit? Was the timing good? Did the work hold up? Those prompts pull real detail without putting any words in anyone's mouth. The review still belongs to the customer.

That's the whole idea behind how small Talk works. It guides the customer through their own experience with a few quick taps, drafts a review from their real answers, and lets them edit and approve every word before it posts. It never tells them to insert a name to satisfy a contest. The specificity comes from the customer's experience, which is exactly where Google wants it to come from.

Would the review survive without your instructions?

Here's the test to run on your own process. If you removed every instruction you give customers, would the reviews still read the same way? If yes, you're asking cleanly. If the reviews fall apart without your script, the script was the problem.

Real reviews are a little uneven. Different words, different details, different names, or no names at all. That unevenness is what makes them believable, and it's what keeps your profile out of trouble.

Next step

Get specific reviews without scripting a word.

small Talk helps customers write from what actually happened, in their own words, and keeps the final review in their hands. No scripts, no name-drop contests, nothing for Google to flag.

Start freeNo credit card required
See the $79 plan

Common questions

Can I ask a customer to mention my name in a Google review?

You can ask for the review, but you should not tell the customer to include a specific name. As of its 2026 update, Google treats requests to mention an employee by name as requested content, which falls under rating manipulation. A customer who names the person on their own is fine. A customer following your instruction is the part that carries risk.

Can customers mention employees in Google reviews at all?

Yes. Google did not ban employee names in reviews. A genuine review like "ask for Luis, he was great" is completely allowed when the customer chose to write it. The rule is about businesses requesting or scripting those mentions, not about the mentions themselves.

Will Google remove a review that names an employee?

A single natural mention is usually fine. The risk is a pattern. When many reviews name the same employee with a full first and last name, Google's automated systems can read that as a coordinated campaign and remove the reviews, sometimes including the genuine ones caught in the same batch.

Is it against Google's policy to ask for a five-star review?

Yes. Asking specifically for five stars, or for any particular rating, is rating manipulation under Google's policy. Ask for an honest review and let the customer decide the rating. The same logic applies to scripting the words or the names a customer should use.

Can I put my technician's name on a review request card?

Putting "please mention [name]" on a card, kiosk, or text message is the kind of scripted, requested content Google's 2026 update targets. You can introduce your technician and do memorable work so customers credit them naturally, but you should not instruct customers to include the name.

Related guides