A Review That Names an Employee: Replying Without Wronging Anyone

"The staff member Sarah was rude and knew nothing about the product." One star, and your employee's name is out there for everyone.

This review puts you between two parties: an angry customer the public is reading, and an employee whose name is published in a complaint that may be unfair. A reply that satisfies one damages the other — unless you know the shape.

Key takeaways:

• Never blame your employee publicly, however accurate the review.
• "The responsibility is ours as a team" is the sentence that protects both.
• Naming a staff member may breach the personal-information policy — or may not.
• Tell the employee before they find it themselves.
• A reply promising "accountability" repels talent and unsettles readers at once.

Will it be removed? Sometimes

Google's policy prohibits posting "personal information of another posted without their consent such as: full name". But it explicitly allows:

"An individual's name if it is part of the commonly known or advertised business entity" or "if they are a public-facing professional conducting business under their name"

(Prohibited & restricted content)

In practice:

• First name only ("Sarah") → usually allowed. A report will likely be rejected.
• Full name of an ordinary employee → a stronger basis for a personal-information report.
• A doctor, lawyer or anyone practising under their own name → explicitly allowed, not removed.
• A name plus a phone number or private detail → a clear violation; report immediately.

Steps in reporting a policy-violating review. Don't bet on removal — reply as though it will stay.

The golden rule of the reply

Never blame your employee publicly. Even after checking and finding the complaint entirely accurate.

Three wrong shapes that owners write in good faith:

• ❌ "The employee concerned will be held accountable" — it looks decisive, and readers see a place that throws its team to the public while your team reads it as a threat.
• ❌ "Sarah is new and still training" — an excuse that exposes weak training and embarrasses her.
• ❌ "Sarah is one of our best and this isn't true" — arguing with the customer, and dragging her into a public dispute.

The correct shape carries responsibility institutionally:

We're sorry the experience wasn't what we want it to be. The responsibility is ours as a team, and we'd like to hear the details from you at [email] so we can put it right.

Note what it contains: a real apology, no name at all, and a move to private. Readers see mature management, and the employee doesn't find her name in an official reply.

⚠️ Never repeat the employee's name in your reply. You naming her pins it to the page and makes it part of the business's official record, not just a customer's words.

Before replying: check internally

The review may be accurate, unfair, or about somebody else entirely. Within hours:

1. Check who was on shift at that time.
2. Ask the employee calmly about the incident — before she sees it online.
3. If there's a recording or an order record, review it.

The second point matters more than it looks: an employee discovering her name in a public review before hearing from you is worse than the review itself.

If the complaint is accurate

The public reply doesn't change — responsibility stays institutional. What changes is what you do internally, and that isn't published.

You can name the action without naming the person:

We've reviewed how we greet customers after your feedback, and thank you for telling us.

That is a strong line for the next reader: a business that changes based on what it's told.

If it's unfair

Don't defend sharply, and don't deny on your employee's behalf:

We take every piece of feedback seriously and would like to understand what happened more clearly. Email us at [email].

Then tell your employee explicitly that you don't consider her at fault. Internal support is what prevents a resignation — not the public reply.

The other side: praise by name

A review praising an employee by name is a gain — thank them without overdoing it:

We're glad the experience was good, and we'll pass your words to the team.

⚠️ But never ask for it. Google's current policy prohibits merchants from soliciting reviews that include specific content, including content that identifies a staff member. "Mention my name in the review" is now an explicit violation — detail in what changed in Google's review policy.

FAQ

The employee asks me to get it deleted — what do I say?

Explain that you don't have deletion powers, and that you reported it if there was a basis. More importantly: tell her where you stand internally.

Can I report on her behalf?

You can report the review as personal information. The individual concerned can also report it, and their report carries more weight.

A review that insults the employee with profanity?

Different category: offensive content and profanity are explicitly prohibited. The report is much stronger here, and the reply stays short and neutral.

Should I reply if the review is old?

Yes, acknowledging the delay. Method in how fast you need to reply.

The bottom line

A review naming an employee is managed with two rules: protect the employee publicly, and handle the problem internally. Confusing the two is what produces bad replies.

The test is simple: if your team read your reply, would they feel protected or handed over? The answer decides whether the reply is fit to publish.

And when these cases arrive among twenty reviews a week, holding a consistent tone is the hard part. Raddly drafts each reply in your business's voice within the boundaries you set, keeping them human and disciplined at the same time.