How to reply
A good rude staff review response apologises, takes responsibility and moves the details offline, without discussing any employee in public.
"We're sorry. Every customer deserves to be treated with courtesy, and what you describe isn't acceptable. I've raised it with the team, and I'd like to understand more: please write to [email] with the date and time of your visit. – [Name], Store Manager"
What not to say
- "Our staff are always polite." It calls the customer a liar.
- "We have spoken to [name]." Names do not belong in public replies.
- "The staff member has been dismissed." Never discuss staff actions publicly.
- "Maybe you misunderstood."
Investigating fairly
- Get the date, time and details privately.
- Talk to the team on that shift.
- Check whether the store was understaffed or unusually busy.
- Look for other reviews describing the same thing.
Look for the pattern
Complaints about staff attitude often cluster at peak times, in stores short of staff or after policy changes that staff must enforce. If rude-staff complaints rise at several stores at once, look for a common cause before blaming individuals.
Which stores need attention: a triage method.
Which stores need attention a triage methodFree review snapshot
Want this done for your own reviews?
No commitment. We use your details only to send your snapshot and follow up. Privacy policy
An example
A retail chain sees rude-staff complaints rise at 12 stores after a new rule requiring ID for exchanges. Reviews describe staff "refusing" and "arguing". Staff were enforcing a rule they could not explain. Clear signage, a script and authority for managers to make exceptions bring complaints back down; no disciplinary action was needed.
Common mistakes
- Disciplining first, investigating later.
- Ignoring the pattern across stores.
- Defensive public replies.
- Not following up with the customer.
Common questions
Should the named employee reply?
No. A manager replies on behalf of the business.
What if the customer was abusive too?
Reply calmly and professionally; do not argue in public.
Should we tell the customer what action was taken?
Thank them and say it was looked into; staff matters stay private.
How do we prevent these complaints?
Staffing at peaks, training on difficult conversations and policies staff can explain.
In short
Apologise without naming anyone, take it offline, investigate fairly, and look for the conditions behind the behaviour across stores.
Variants by situation
"We're sorry you felt ignored while waiting for help. That's not the welcome we want for anyone. We're looking at how the floor is staffed at busy times. – [Name], Store Manager"
"Thank you for telling us. Being spoken to that way is not acceptable, and I've raised it with the team. Please write to [email] with the date of your visit. – [Name], Area Manager"
"We're sorry. Our staff should explain policies clearly and courteously, and we're improving how this one is explained at the counter. – [Name], Store Manager"
Checklist
- No names in public.
- Apology without qualification.
- Private route for details.
- Pattern checked across stores and shifts.
Supporting your team
Share the pattern with store teams without singling anyone out in public, and ask what made those moments hard: queues, rules they could not explain, or too few people on the floor. Staff who are heard are more likely to fix the conditions behind the complaints.
Doing this with Falcon
Falcon's CRM is where a team handles replies across stores. For each review it suggests an owner from your taxonomy, drafts a reply from the playbook for the review's theme and sentiment, and checks the draft before it is saved: is it long enough to sound personal, does it contain a phone number or email, does it promise compensation that needs a manager's approval, and does it fit the channel's length. Reviews can be assigned, escalated and tracked to done. The reply itself is posted in Google Business Profile.