Review Management Is a Workflow, Not a Reply Button: Ask, Route, Reply, Escalate, Use

Review management is the set of routines that decide how customer reviews are requested, where they land, who answers them, which ones escalate and what the business learns from them. A complete system covers five jobs: ask, route, reply, escalate and use. Most teams only do the third.

That imbalance is understandable. Replying is the step platforms make easiest: Google lets a verified business answer its reviews directly, so the work lands on whoever holds the login and happens whenever they notice a notification. Asking depends on someone remembering. Routing, escalating and using depend on nobody in particular, so they quietly do not happen.

This guide is the operating layer around those jobs. It does not repeat the platform walkthrough in How to Get More Google Reviews Without Breaking the Rules, the reply and escalation craft in A Review Reply Should Solve the Next Step, Not Win an Argument, or the analysis method in Review Mining Should Preserve the Complaint, Not Just Harvest the Phrase. It shows how those pieces connect and where the rules draw hard lines.

The rules differ by platform, so a single “send everyone to review us” script tends to break at least one of them. Start from what each source says, read in October 2026, and design the workflow to the strictest of them.

Review gating means screening customers by satisfaction and sending only the pleased ones to the public platform. Google's policy language names the practice when it bars merchants from selectively soliciting positive reviews. The safest design is one where selection cannot happen, because the invitation depends on an event and never on an opinion.

The rule is short: every customer who reaches the trigger event receives the same invitation, through the same channel, with the same link. A job marked complete in the CRM or field-service system is a good trigger because it is a record, not a staff member's guess about the customer's mood. Staff can still say thank you in person. They just cannot choose who gets the link.

A private route for complaints is worth having. We read Google's policy as allowing a private contact option next to the public link and as disallowing one instead of it. If you are unsure, show both, and let the customer choose.

Repeat customers need a rule too. If the same customer books several jobs a year, decide whether you ask after each job or only after the first and then again after a long gap. Whatever you choose, apply it to everyone, and stop asking anyone who has already reviewed that location. Google also notes that reviews are available only in certain countries and for certain business categories, so confirm your listing can receive them before you build a program around it.

Platform notifications go to whoever holds the login, so the first routing job is to pull every review into one queue. The minimum record is the platform, location, date, rating, theme tag, owner, status and the time the reply was posted. A shared spreadsheet is enough to start; the discipline matters more than the tool.

Triage by what the review says rather than by its star count. A three-star review that describes a billing error needs a different owner from a five-star review that mentions a staff member by name. The windows below are starting points we suggest, not benchmarks from a study. Set yours to what the team can keep every week.

A public reply has two readers. One is the reviewer. The other is the next customer scanning the profile, who will judge you by how the response sounds far more than by the review itself. Write for the second reader: specific, calm, and ending in a next step.

A workable structure runs four beats. Acknowledge the specific issue in one sentence. Add a fact only if it corrects the public record without exposing private details. Give a direct way to continue the conversation offline. Stop. Here is an illustrative reply, written for this article and not taken from any real business: “Thank you for telling us the technician arrived outside the window we gave you. That is not the standard we aim for, and our dispatch manager would like to hear the details. Please call the office number on our profile or reply to the email we sent today.”

Practices that handle health information face extra limits on what a reply may confirm, including whether the reviewer was a customer at all. Local SEO for Dentists and Dental Practices covers the patient-privacy side. For any business, the safe habit is to confirm nothing the reviewer has not already said.

Escalation is a list of triggers agreed in advance, because the middle of an argument is the wrong moment to decide who handles legal threats. The table pairs each situation with the move that protects you and the move that creates a second problem.

Once a month, tag each review with a theme such as speed, price, communication, quality, staff or billing. Count the themes and read the negative reviews in full. Then give each theme one decision: fix it, test a fix, accept it with a written reason, or escalate it. A theme list without a decision beside each line is just a more organized way of ignoring customers.

Treat counts as signals, not rates. Reviews come from people who chose to write, so ten complaints about parking may be a real problem or may be one lively week. Review Mining Should Preserve the Complaint, Not Just Harvest the Phrase explains how to keep the original wording, which matters more than the tally.

Reuse outside the platform raises its own questions. If you quote a customer on a service page or in an ad, you are making a different kind of claim from a review that sits on Google. A Testimonial Needs Permission, Context, and an Expiry Date covers that step. When you can match a review to a job, record the link in the CRM so service history and feedback sit together. When you cannot, do not guess.

Track the health of the loop as well as its output. A star average tells you how customers feel on balance. It does not tell you whether you are asking everyone, answering on time or acting on what you hear.

Start with ownership, not software. In week one, name the queue owner and a backup, list every location and platform where reviews appear, and put the escalation triggers from the table above on one page that a manager has signed. Nothing else holds until a named person is on the hook for the queue.

In week two, build the single queue and backfill the last 90 days of reviews into it. Reply to anything unanswered that deserves an answer, starting with the negative reviews that describe a specific event, and contact those customers directly where you can identify them. Do not mass-edit old replies. A rewritten reply history looks odd and fixes little.

In week three, wire the ask to the trigger event: one invitation, one link per location, one reminder, and a log of every invitation so coverage can be calculated. If the invitation goes by text, settle consent first. In week four, hold the first theme review. Read the month's reviews together, tag the themes and leave with at least one decision and an owner for it.

After that the system should run on a fifteen-minute weekly check of the queue and a monthly theme meeting. If it needs more than that to stay alive, it is too complicated for a team that has other work.

Multi-location businesses add one complication: the people who know what happened at a branch are not the people who hold the central login. Keep one central queue, and give each location manager a way to answer a factual question within a day, such as a short form or a named contact. The central responder writes the reply and the local manager supplies the facts. That split is our suggestion, not a platform requirement, and it keeps the tone consistent and the facts right.

The common failures are organizational rather than technical. A well-meaning manager starts a free-coffee-for-a-review promotion without knowing it breaks Google's policy. A branch sets a staff quota, which the policy names as a problem. Someone with the login replies in anger at ten at night. A rating target creeps into a performance review. None of these needs bad intent, only an unwritten process.

Insider reviews are the quietest risk. The FTC rule covers reviews written by company insiders, and FTC staff say a business is not liable merely because an employee happened to receive a standard invitation and wrote a false review on their own. Staff writing glowing reviews because a manager asked is a different matter, and the rule is aimed at it.

Finally, platform policies move. Re-read the Google, Yelp and FTC pages in the sources below each quarter and note the date you did. This article reflects what those pages said in October 2026, and it is general information, not legal advice.