When a Review Names One of Your Staff
Why Google usually leaves the name in place, what is genuinely reportable, and how to reply without putting your own server in the public firing line
A review, two stars, and a first name in the middle of it. “The server, I think she was called Anna, was completely overwhelmed and rude.” Anna has worked for you for four years, she was alone on the floor that night, and she is going to read this. Probably today.
The first thought is usually to report the review. That works less often than most people assume, and the reason sits in Google’s own policies.
Why the name usually stays
Google prohibits content containing another person’s personal information posted without their consent, and spells out what that covers: “full name, or last name, their face in a photograph or a video”.
There are exceptions, and every one of them concerns names only. They cover an individual’s name where it is part of the commonly known business entity, and the name of “a public-facing professional conducting business under their name”, with examples such as doctors, lawyers, realtors and executives whose professional connection to a place is publicly known.
A server is therefore a borderline case. The German version of the policy reads more broadly than the English one, and the examples point at professionals trading under their own name rather than at employed staff. In practice the first name almost always stays up, so reporting a review purely over the name has little chance. The photograph is a different matter, see below.
(Source: Google: Prohibited and restricted content policies)
What is reportable anyway
The line runs between work and private life, not between pleasant and unpleasant.
- Private details unrelated to the job: home address, private phone number, facts about someone’s personal life or family
- Insults and hate speech: abuse, degradation, attacks on origin, gender or appearance
- Clearly fabricated events: someone who was never there, or a mix-up with a different venue
Harsh criticism of the work itself stays up, even when it is one-sided or unfair. What a removal request has to look like when there genuinely is a violation is covered in our article on getting a Google review removed.
When a photo shows the person
This case sits very differently, and in the business’s favour.
A face in a photograph is on Google’s prohibited list, and none of the exceptions that apply to names apply to images. Uploading a recognisable photo of a member of staff without their consent therefore breaches the policy, whether the accompanying text is warm or furious.
That includes the kindly meant photo. “Best server in town” under a portrait of the waitress is no more voluntary for the person pictured than the complaint is. Removing it later, after someone moves on to another job, is harder precisely because nobody objected at the time.
There is a legal layer on top, independent of Google’s policy, and it is worth knowing which rule applies where.
EU-wide, the General Data Protection Regulation treats a photograph showing an identifiable person as personal data, and gives that person a right to erasure. This applies in every member state, including Austria and Germany.
Austria, section 78 UrhG, prohibits publishing images of a person where doing so would harm their legitimate interests.
Germany, section 22 KunstUrhG, is stricter in wording: images of a person may only be distributed or publicly displayed with that person’s consent.
The practical difference: Germany turns on missing consent, Austria on harmed legitimate interests, which an angry caption under the photo tends to support. In all cases the right belongs to the person pictured, not to the business. This points at the legal position, it is not legal advice.
In practice:
- Tell the person first, before you act. It is their image and their call
- Either of you can report it, the business through the profile and the person themselves. Their report carries more weight, because only they can confirm that consent was missing
- Take a screenshot first, including the date and the guest’s profile name
- Do not make the photo a topic in your reply, and do not repeat the name. Every mention raises the visibility of the very thing you want gone
- With praise, ask whether the person wants it to stay. Some are delighted, others are not, and both are fine
The reply: responsibility yes, the person no
This is where a bad review either ends or turns into a second problem.
Reply as the business, not about the person. The first person plural is not evasion, it is factually right: the server did not decide the staffing level that evening, the rota did.
Do not defend in public detail. “Anna had 40 guests on her own that night” sounds like an explanation, but it makes the person even more of a topic and hands the guest an opening to come back.
Confirm nothing you have not checked. A hasty “We are sorry, we have spoken to the member of staff” is a public admission of fault about someone who cannot answer for themselves.
A reply that holds up:
Thanks for the feedback. We were understaffed that evening, and that is on us, not on the team. We would like to understand what exactly went wrong. Please get in touch with us directly.
The underlying pattern for replies like this is in our article on responding to negative Google reviews.
The part almost everyone skips: the team
The review is public, the person concerned will read it either way. The only question is whether they hear it from you or from a guest who brings it up.
- Tell them first, briefly and without drama, before they find it themselves
- One review is a data point, not an appraisal. Staffing decisions based on a single guest opinion are a management failure
- Watch for patterns, not incidents: if the same name keeps appearing in a similar context over months, that is a conversation. Once is a bad evening
- Show them the reply before it goes live. It removes the fear of being sacrificed in public
And the other way round: praise by name
The obvious idea, asking guests for a review that names the server, is unfortunately not one. Google explicitly names it as a violation to have staff solicit reviews containing specific content, including content that identifies a staff member.
That covers the engineered request, not the voluntary mention. If a guest writes of their own accord that Anna saved the evening, nothing is wrong with that, and a personal reply is worth twice as much. What else is off limits when collecting reviews is in our article on the rules for collecting Google reviews.
At a glance
| Situation | Right response |
|---|---|
| Server’s first name, criticism of the work | Leave it, reply as the business, discuss internally |
| Private details of the person published | Report it, reply factually in parallel |
| Insult or degradation | Report it, reply briefly and with dignity |
| Guest demonstrably never visited | Report with grounds, do not argue in public |
| Photo shows the person, negative text | Tell the person, let them report it, do not mention the photo in your reply |
| Photo shows the person, praise | Ask whether they want it to stay, otherwise let them report it |
| Praise by name, written voluntarily | Reply personally, show it to the team |
The bottom line
The name usually stays, and that cannot be changed. What can be changed is what happens next: a reply that puts the business on the hook rather than the person, and a conversation with the team that comes before the guest’s, not after. Making sure every review gets a timely reply that sounds like you and not like a template is what SupaPresence handles for restaurants. Join the pilot for free.
Frequently Asked Questions
Can I have a review removed that names a member of staff?
Usually not. Google prohibits publishing personal information without consent, but explicitly exempts the name of a person who normally interacts with customers and acts on behalf of a business. Service staff generally fall under that exemption.
What is reportable in such a review after all?
Private details unrelated to the job, such as a home address, a private phone number or facts about someone’s personal life. Insults and hate speech too. Criticism of the work itself stays up.
Should I defend the staff member in my reply?
Not publicly, and not in detail. Reply as the business in the first person plural, take responsibility for how the evening ran, and handle the rest internally. A public rebuttal only makes the person more of a topic.
Should I show the review to my team?
Yes, and before anyone finds it themselves. Otherwise the person hears about it by accident, from a guest or a colleague. A short conversation beforehand takes the sting out.
A guest uploaded a photo of my staff member, what now?
A face in a photograph is on Google’s prohibited list, and unlike a name it has no exception. Without the consent of the person pictured the image is reportable, with negative and positive text alike. Tell the person first, their report carries more weight than yours.
Can I ask guests to mention a staff member by name?
No. Google names it explicitly as a violation to solicit reviews containing specific content, including content that identifies a staff member. That covers the engineered request, not a guest mentioning someone of their own accord.