Reviews that name a specific waiter, chef, or host: how to respond

Saturday night a 5-star review comes in: 'Andrew took care of us, made our night.' Tuesday morning another one: 'Server Andrew was rude to us from the moment we walked in.' Same name, same restaurant, opposite reviews. How do you respond to each?

Reviews that name a specific employee are delicate territory. Your responses can do a lot of good — or create serious employment problems — depending on how you handle them.

Positive reviews with a name: the public compliment that works

When a customer mentions an employee in a positive review, it's a gift. Your response should: (1) mention the employee by name, (2) reflect that the review reached that person, and (3) use a warm tone without sounding scripted.

Wrong: 'Thanks for your visit.' (Doesn't mention Andrew. Wastes the moment.)

Right: 'Laura, so glad Andrew made your night. We'll share your review with him — he's going to be happy. Come back soon.'

This response works because it closes the loop: the customer mentioned Andrew, you confirm to Laura that Andrew will hear about it, and by making it public, other customers see that good employees get recognized at your restaurant.

If several customers mention the same person in their reviews — that's valuable operational information. That person is probably one of your strongest assets and worth recognizing internally too, not just on Google.

Negative reviews with a name: legal territory

Here's where it gets complicated. When a customer publicly posts something negative about a named employee — 'Server Mike was rude,' 'Chef Marco sent the food out cold on purpose' — three risks appear at the same time.

1. Defamation risk to the employee. Employees have rights to their name and reputation. If your response publicly confirms the attributed behavior ('we apologize that Mike was rude'), the employee could argue the restaurant publicly acknowledged something that hurts their professional reputation.
2. Employment risk. Disciplining an employee in a public response can be problematic. If you later decide to fire them and they sue, that response can be used as evidence.
3. Error risk. The customer might have the name wrong. The employee might have been having a personal bad day. Reacting publicly before investigating privately is bad management.

The correct response NEVER confirms the named employee's behavior, NEVER disciplines publicly, and always moves the conversation to a private channel.

Pattern for negative reviews with a name

The pattern is:

'Andrew, thanks for writing. We're sorry your experience wasn't what you were looking for. We want to understand what happened — write to us at management@examplerestaurant.com with the details and we'll review internally.'

Notice what this response does NOT do: it doesn't confirm the employee's name, doesn't admit the behavior occurred as described, doesn't commit to a specific action against that person. It simply acknowledges that something happened, invites private dialogue, and commits to reviewing.

Notice too: the invitation goes from the restaurant to the customer, not the other way around. We don't promise the restaurant will reach out. We give them the email and the customer decides.

After publishing the response, you do investigate internally — but privately, with a cool head, talking to the employee, to whoever else was working that day, to the host. The internal action and the public response are two separate paths.

When the customer names the wrong person

This happens more often than you'd think. The customer remembers 'the tall server' and assigns them a name that comes to mind — and it turns out to be wrong. Or confuses them with the host. Or uses a generic name.

Don't correct in public. If the customer wrote 'Peter' and the server was Anthony, don't reply with 'actually it was Anthony who took your table.' It sounds defensive and creates a weird public exchange.

Just use the general pattern: acknowledge, invite private dialogue, review internally. If the private conversation confirms it was a different person, that stays between you and the customer.

Why 'Approve everything' makes sense for some restaurants

If your restaurant frequently gets reviews naming staff — whether due to the nature of the service (bartenders, sushi chefs, host of the brand) or because the team is high-visibility — the 'Approve everything' preset in Westify might be the right fit.

With 'Approve everything,' every response comes to you via SMS before publishing. You review the pattern is right before it goes out. Takes 30 seconds per review, but gives you complete control on the type of reviews where control matters most.

The other two presets ('Hands off' and 'Review critical reviews') work for most businesses. But if you work in a category where names appear often, 'Approve everything' is the safer option. You can switch to it from the panel anytime.