Review escalation: when to escalate a review to a person

Why escalation matters

Review escalation is what keeps a routine process from mishandling a serious complaint. A cheerful template under a review that describes food poisoning, discrimination or a threat can do real harm. Escalation rules decide which reviews leave the normal reply flow, who handles them and how fast.

Escalate these

• Safety and health: injuries, illness, contamination, pests.
• Discrimination or harassment claims.
• Legal threats or mentions of lawyers, consumer forums or regulators.
• Serious allegations against a named employee.
• Fraud or billing disputes involving significant amounts.
• Extortion: demands linked to negative reviews.
• Media, influencer or social media attention.
• Repeat complaints from the same customer.

Who receives what

• Safety and health: operations or safety lead, same day.
• Discrimination, harassment, staff allegations: HR and communications.
• Legal threats: legal, before any reply.
• Fraud and billing: finance or customer care.
• Extortion: central team; report through Google's extortion form.
• Media attention: communications.

Replying after escalation

Once escalated, reply briefly and seriously, or wait for approval if the reply could have legal or safety implications. Never argue the facts in public.

An example

A store manager sees a review saying a child slipped on a wet floor. Instead of replying, the manager escalates to operations, who check CCTV and incident logs the same day. The reply, approved by operations, apologises, says the area manager will call, and gives a contact. The store adds wet-floor signage checks to its hourly rota.

Common mistakes

• Replying before the right person knows.
• Escalating everything, which buries the serious cases.
• No time limit on escalations.
• Never reviewing escalations for patterns.

Common questions

Checklist

• Triggers written down.
• An owner per trigger.
• Time limits.
• Approval rules for replies.
• Monthly review of escalations by type and store.

In short

Escalate safety, health, discrimination, legal, staff allegations, fraud, extortion and media cases before replying; route each to a named owner with a time limit, and review escalations for patterns.

An escalation record

For each escalated review, record the date, store, trigger type, who received it, when it was acknowledged, the decision, the reply posted and any follow-up action. A simple shared sheet is enough to start. Reviewed monthly, it shows which stores generate the most serious complaints and whether escalations are handled within their time limits.

Over a quarter, the record usually reveals one or two recurring causes worth fixing centrally.

Training store teams

Show store managers five real examples of reviews that should be escalated and five that should not, and explain the difference. Most teams escalate correctly once they have seen the boundary; without examples, they either escalate everything or nothing.

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.