"The blonde girl on reception was incredibly rude and made me feel like an inconvenience."

This is the review that keeps managers up at night, because it's not one problem. It's three, all at once.

A customer who feels disrespected and wants acknowledgement.
An employee who is about to read a public description of themselves and may well have a completely different account of what happened.
Every future customer, watching how you treat your own staff in public.

Get this reply wrong in either direction — throwing your employee under the bus, or dismissing the customer to defend your team — and you damage something you can't easily repair.

Before you write anything: talk to your employee

This is the step people skip because they want the review answered quickly. Don't skip it.

Find the person, privately, and ask what happened — genuinely asking, not accusing. Very often you learn something that changes the picture completely: the customer was abusive first, there was a policy the employee was correctly enforcing, they were dealing with an emergency, or it was someone else entirely.

You may also learn that your employee was, in fact, having a terrible day and was short with someone. That's a management conversation, not a public one.

Never post a reply about a staff member before you've spoken to that staff member. They will read your reply, and finding out this way is the fastest way to lose good people.

The rules for the public reply

Never name the employee. Not their first name, not their role if it identifies one person, not "the young lady on reception." Even if the reviewer named them, you don't repeat it.
Never confirm the accusation publicly. "We have spoken to the member of staff concerned and disciplinary action has been taken" is a nightmare — for the employee, and for every other person on your team reading it.
Never deny the customer's experience. "That doesn't sound like our team" tells the reviewer they're lying and tells every reader you don't listen.
Never defend by attacking. Even if the customer was abusive, the public reply is not where you say so.
Do take it seriously and take it offline. That's the whole play.

The formula

Acknowledge how they were made to feel (not what your employee did) → state your standard → move it to a private channel.

The distinction in the first step is subtle and it's the whole trick. "I'm sorry you were made to feel unwelcome" accepts their experience without accepting an accusation you haven't verified.

8 examples

1. The standard reply

Thank you for telling me. Nobody should leave here feeling like an inconvenience, and I'm sorry that's how you felt. I'd like to understand exactly what happened — please email me at [email] and I'll look into it personally. — [Name], Manager

2. When you've already spoken to the team

I'm sorry — that isn't the welcome we want anyone to have. The team and I have talked about your visit and taken it on board. If you're willing, I'd value five minutes on the phone: [phone].

3. When your employee has a very different account

Thank you for the feedback, and I'm sorry the visit left you feeling this way. I've spoken with the team and I'd like to hear your side properly rather than rely on one account — [email] comes straight to me.

4. When the customer was abusive

I'm sorry your visit ended badly. We hold our team to a high standard of courtesy and we expect the same in return, so I'd like to understand the full picture. Please contact me directly at [email].

5. Clinic or professional practice

Thank you for your feedback. We can't discuss individual visits publicly, but we take concerns about how patients are treated very seriously. Please contact our practice manager on [phone] so we can address this properly.

6. When a policy was being correctly enforced

Thank you for the feedback, and I'm sorry the conversation felt unfriendly. We do have to apply [policy] consistently, but it should always be explained kindly — if that didn't come across, that's something for us to work on. Happy to talk it through: [email].

7. Restaurant or bar, busy service

Sorry about this — a busy room is never an excuse for making someone feel brushed off. Thank you for telling us rather than just not coming back. If you email me at [email] I'd like to make your next visit better.

8. When it's a repeated theme

Thank you for being direct. You're not the first person to mention this and that tells me it's on us to fix rather than a one-off. We're making changes to how we handle [situation]. I'd appreciate hearing more: [email].

Handling it internally

The public reply takes two minutes. The internal handling is what actually matters.

Tell the employee before it's public. Show them the review yourself. Nobody should find out by scrolling Google.
Ask, don't accuse. "A customer left this, can you help me understand what happened?"
Look for the pattern, not the incident. One complaint about a good employee is life. Four complaints in three months is a performance conversation.
Defend them internally if they were right. Staff who see a manager cave to every complaint stop enforcing anything.
Never post a reply implying discipline. Your team will notice, and morale drops faster than your rating ever did.

The thing most owners get wrong

In the rush to look responsive, businesses write replies that sound good to the customer and terrible to the team. "This has been addressed with the individual concerned" feels decisive when you write it. Read it as the employee: your manager just publicly announced you were disciplined, to strangers, before speaking to you.

Good staff leave over that. And staff turnover damages your reviews far more, and far longer, than any single complaint. If you're building rules for how your team handles this, our guide to a review response policy covers who replies and what they're allowed to say.

Reploi drafts replies that acknowledge the customer without ever naming or implicating an employee — so the fastest reply is also the safest one. Start free — 5 replies/month →

How to Respond to a Review About a Rude Employee