When a Google Review Names a Staff Member: What to Do With It Beyond a 'Thanks'

09 October 2026·6 min read

Quick answer: A quick "thanks for the kind words" reply is fine, but a review that names a team member by name deserves more — tell that person directly, loop their manager in, and consider a small recognition moment internally. If you want to reuse it anywhere public (socials, website, a team shout-out post), get explicit written consent from that staff member first, every time. 🤍

A five-star review comes in and it's not just generic praise — it says "Sarah was amazing, she went out of her way to help us and made the whole thing so much easier." You reply with a polite "thank you so much, we'll pass this on!" and move on with your day. 💖 Except you probably won't pass it on, not really, and that review is quietly doing more for your business than a hundred generic five-star ratings ever could. It names a real person your customers trust. That deserves a proper workflow, not a canned reply.

What most businesses get wrong

The most common mistake is treating a named review exactly like every other review — reply, move on, forget. That misses two things. First, it's a genuine morale opportunity: team members rarely hear directly that a customer singled them out, and businesses that build a habit of surfacing this feedback internally tend to see it reflected straight back in how staff treat the next customer. Second, and more importantly, a review naming a staff member is personal information about a real person, and businesses sometimes reuse it — screenshotting it straight to Instagram, pulling the name into a testimonials page — without ever actually asking that person if they're comfortable being named publicly. Just because a customer published the name doesn't mean the business has the right to republish it everywhere. That's the staff member's call, not yours.

The workflow

Step 1 — Reply to the review properly. Thank the reviewer by name if they left one, reference the specific thing they mentioned (not a generic template), and keep it warm and brief.

Step 2 — Tell the staff member directly, the same week. Not in a group Slack channel where it gets buried — a direct message or a quick in-person mention. Read them the actual review. This is the single most impactful, lowest-effort step in the whole workflow.

Step 3 — Loop in their manager or team lead. A quick "heads up, a customer specifically called out [name] for [the thing they did well]" takes thirty seconds and makes sure it shows up somewhere that matters, like a performance conversation or a simple recognition log.

Step 4 — Decide if it's worth a small internal recognition moment. A mention in a team meeting, a shared recognition channel, or even just a handwritten note — doesn't need to be elaborate, just consistent enough that staff know good reviews actually get noticed.

Step 5 — If you want to reuse it publicly, ask first. Send the staff member the exact review, the exact way you'd like to use it (which platform, with their name or just their first name, with or without a photo), and get a clear yes before anything gets posted. No assumptions, no "I'm sure they'd be fine with it."

The retail scenario: A customer leaves a review praising a shop assistant by first name for helping them find the right product after three other stores couldn't. The manager reads it to the assistant directly, mentions it in the next team huddle, and asks the assistant if it's okay to quote (first name only) on the store's Instagram. The assistant says yes to first name only, no photo — and that's exactly what gets posted.

The trades scenario: A review names a tradesperson for turning up on time and explaining the job clearly before starting. The business owner forwards the review to them directly, adds a note of thanks, and asks if they'd like it added to the "our team" page on the website with their photo. They say yes to the quote but no to the photo — both preferences are honoured exactly.

The hospitality scenario: A regular customer leaves a review naming a staff member for remembering their usual order and making them feel welcome. The business shares it in a weekly recognition huddle and asks the staff member if they're comfortable with their first name appearing in a "team spotlight" social post. They agree, and the post goes up with wording they've seen and approved beforehand.

The staff-consent request template

Hi [name], a customer left us a review and specifically mentioned you — here's exactly what they said: "[paste review]." I wanted to say thank you in person for that, and also ask: would you be comfortable with us sharing this publicly (for example on [platform])? You can choose: full name, first name only, or no name at all, and with or without a photo. Totally fine either way — just let me know what you're comfortable with, and we'll only use what you agree to.

Keep a simple record of what each staff member has agreed to (platform, name format, photo yes/no) so you're not re-asking every time, and so nobody accidentally reuses an old "yes" for something they never actually approved.

How to actually do this

Build the first two steps — reply to the review, tell the staff member directly — into your normal review-monitoring routine so it happens every time, not just when someone remembers. If you're already pulling reviews regularly as part of getting more Google reviews or responding to Google reviews, this is simply one extra branch in that same process: does this review name someone? If yes, route it to that person and their manager before you do anything else with it.

💡 Consent isn't a formality, it's the whole point. A staff member's name and likeness belong to them, not to the business, even when a customer published it first. Getting explicit, specific consent before any public reuse protects your team and keeps the recognition feeling like a genuine thank-you rather than something that was done to them.

Don't assume a public review means automatic permission to republish it elsewhere.
Don't post a staff member's full name and photo without asking which parts they're comfortable with.
Don't let a glowing mention sit unread by the actual person it's about.
Don't reuse an old consent for a new platform or format without checking again.
Don't make recognition purely public-facing — the internal thank-you matters more to staff than the social post.

Frequently asked questions

Do I legally need staff consent to repost a review that names them?

Requirements vary depending on where you operate and what exactly you're doing with it, so this isn't a blanket legal rule — but as a matter of good practice, treating a name and photo as something that needs clear consent before public reuse is the safer and more respectful default regardless of the letter of the law.

What if the staff member says no?

Respect it, fully, and don't push or ask again a few weeks later hoping they'll change their mind. You can still do everything in Steps 1-4 (reply, tell them, loop in their manager, recognise internally) — the public reuse is simply the one piece that's off the table.

What if the review is about a team effort, not one person?

Share it with the whole team the same way, and if you want to reuse it publicly without singling anyone out, you generally don't need individual consent for a review that doesn't name anyone specifically — though it's still worth a quick check if it describes a very identifiable situation.

Should I ask for consent before or after telling them about the review?

After. Let the thank-you land on its own first — it should feel like recognition, not a pitch for content. Ask about public reuse as a clearly separate, optional follow-up.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦