Replying to Google reviews across many locations: a workflow that holds up

The workflow that holds up across many locations is simple to state: bring every location's reviews into one queue, answer the negative and the oldest unanswered reviews first, hold each location to a reply time you can actually keep, write in one brand voice with room for local detail, and let an agent draft while a person checks and sends. What breaks multi-location reply programmes is rarely the writing. It is reviews sitting unseen in a profile nobody opened this week, a reply that names the wrong member of staff, or a well-meant offer that turns into a policy problem. This post sets out the order, the rules and the sign-off steps, so a team can run it whatever tools they use.

Why replies are worth the effort

Owner replies are public and they are not filtered by star rating. Anyone reading a review sees your answer beneath it, posted under the business rather than your personal name, and the reviewer is alerted when you reply. Reviewers can still edit their review after reading your response.¹ That last point matters more than it sounds: a calm, specific reply to a complaint is the only lever you have on a review that is already written.

There is also outside evidence that replying changes what happens next. A study published in Marketing Science compared hotel reviews on a platform where hotels regularly responded with a platform where they rarely did. Hotels that started responding saw a 0.12-star increase in ratings and a 12% increase in review volume. They also received fewer negative reviews, but the negative reviews that did arrive were longer and more detailed.² That is one sector and one time period, so treat it as a direction rather than a promise, but it is the right direction, and it matches what most operators see: people write more carefully when they know someone is reading.

That last figure is worth knowing before you set targets. Google checks each reply against its content policies before it appears, which usually takes up to 10 minutes but can take up to 30 days, and a reply that is not approved has to be edited.¹ "Sent" and "live" are not the same thing, so your process should track both.

Step one: one queue, every location

With three locations you can open each profile in turn. With thirty, someone will miss one, and the missed one is usually the quiet branch that gets a scathing review on a Sunday. The fix is structural: every location's reviews flow into a single list that shows the location, the rating, the age of the review and whether it has a reply. Whether that list is a shared spreadsheet fed by a weekly export or a dedicated tool, the rule is the same. Nobody works from a single profile's review tab.

Decide who owns the queue. For a brand with a central marketing team, that is usually one person who triages and drafts, with branch managers supplying facts. For an agency, it is the account lead for each client, with the client signing off anything sensitive. Write the owner down. An unowned queue is how a review goes unanswered for six weeks.

Step two: triage in a fixed order

Work the queue in the same order every time, so the riskiest reviews are never the ones left for Friday afternoon.

Step three: reply time targets you can keep

There is no official deadline for replying, so the targets below are ours, set from running reply queues for multi-location businesses. The principle matters more than the exact numbers: tighter targets for worse reviews, and targets that a real team can hit on a bad week, not just a good one.

Measure the oldest unanswered review per location, not the average reply time. An average hides the one branch that has fallen three weeks behind. If a location keeps missing its target, that is a staffing or ownership problem to fix, not a writing problem.

Tone: one brand voice, local details

Across many locations you want replies that sound like the same business wrote them, without reading like the same sentence pasted thirty times. Google's own reply tips point the same way: keep replies clear and helpful, and rather than sending the same thank you to everyone, focus on reviews where you can share a helpful update.³

Keep promotions out of replies. Google's guidance is to avoid using a response to offer deals or promotions.³ A reply is read as evidence of how you treat people, and a discount code in it reads as a sales pitch.

Using staff names carefully

Naming the person a customer praised is one of the best things a reply can do. It is also where multi-location replies go wrong most often, for three reasons.

• Reviewers misspell names. Repeating 'Jenifer' back when your colleague is Jennifer looks careless and it is permanent until someone edits it.
• Reviewers get names wrong entirely, or name someone at a different branch. Check the name belongs to that location before you use it.
• People leave. A reply thanking someone who left last month can confuse the next customer who asks for them.
• Some staff do not want their name on a public page. Ask once, record the answer, and respect it in every reply.
• When in doubt, thank 'the team'. It is never wrong, and it is far better than a wrong name.

The practical answer is a short team list per location: correct spellings, who has left, and who prefers not to be named. Whoever drafts replies checks names against it, every time.

When not to reply in public

Most reviews deserve a public answer. A few deserve a short public answer and the real conversation somewhere else. Your reply sits on a public page indefinitely, so anything you would not say to a stranger in the queue does not belong in it.

Equally, do not argue. If a review contains facts you dispute, state your position once, calmly, and offer to talk. If a review looks fake or breaks the content policy, report it through your Business Profile rather than debating it in the reply. A long public rebuttal draws more attention to the review than the review ever got on its own.

Policy: no incentives, no review gating

Reply programmes and review request programmes are usually run by the same people, so the rules for both belong in the same playbook. Two practices cause most of the trouble.

Google's content policy lists offering incentives such as payment, discounts or free goods and services, and discouraging negative reviews or selectively soliciting positive ones, as fake engagement. It also excludes content based on a conflict of interest, which can include current or former employment.⁴ The incentive ban covers incentives to post, change or remove a review.³

In the UK, the Competition and Markets Authority's guidance on the Digital Markets, Competition and Consumers Act gives a directly relevant example of a banned practice: contacting a customer who has left a negative review and offering a refund or gift card if they change it. The same guidance describes encouraging only satisfied customers to leave reviews as a form of cherry-picking, and warns against making an offer of dispute resolution contingent on a customer not leaving a negative review.⁵

Fix the problem because it is the right thing to do. Never make the fix depend on what happens to the review.

This is the line to brief every branch manager on. Offering a refund to an unhappy customer is good service. Offering it on condition that they change their review is the banned version. The difference is one sentence in an email, which is why it belongs in writing in your playbook.

Approvals, especially for agencies

If you reply on behalf of a client, the reply is published as their business, so agree up front which replies you can send yourself and which need their sign-off. A simple split works for most clients.

1. 1

   Agree the rules once

   Tone, sign-off, words to avoid, the team names list, and who at the client resolves complaints. Write it down and attach it to the account.
2. 2

   Send positive replies within the rules

   4 and 5 star reviews that follow the agreed rules go out without sign-off. Spot-check a sample each month with the client.
3. 3

   Hold negative and sensitive replies for sign-off

   1 to 3 star reviews, anything mentioning health, money, staff conduct or a legal threat: draft, then hold until the client confirms the facts and approves the wording.
4. 4

   Chase the oldest, not the loudest

   If sign-off is slow, post a short holding reply that thanks the reviewer and gives a contact route, then follow up once the facts are agreed.

Drafting with an agent, sending as a person

Drafting is where an agent saves the most time. Given the review, the location and your brand rules, it can produce a sensible first draft in seconds, and for a queue of forty reviews that is the difference between a morning and an hour. The risks are predictable: invented details, a repeated misspelling of a name, a promise the branch cannot keep, or a tone that is slightly too cheerful for a complaint.

• Read every draft before it is posted. Edit anything the reviewer did not actually say.
• Check every name in the draft against the location's team list.
• Remove any offer, discount or promise that has not been agreed with the branch.
• For 1 to 3 star reviews, a person writes or rewrites the final version and a person presses send.
• If you use automatic replies at all, limit them to 4 and 5 star reviews, ideally star-only ratings with no written text.

How SearchOps handles this

Everything above works with a spreadsheet and discipline. If you would rather the queue built itself, this is how SearchOps review monitoring and the Reply Inbox support the same workflow.

1. 1

   See what needs a reply across every location

   The reviews overview shows how many reviews are awaiting a reply, how many of those are low ratings, and a Needs a reply list of the locations with reviews waiting longest, low ratings first. Trustpilot and Tripadvisor reviews sit alongside Google on Pro and above.
2. 2

   Work the queue in the Reply Inbox

   Choose a connected Google Business Profile and the inbox opens on Awaiting, the reviews with no reply yet. Filter by star rating to take the low ratings first.
3. 3

   Let the agent draft in your style

   Generate reply drafts a response you can edit. You set tone, length, sign-off, whether the reviewer's name is used, whether an emoji is ever allowed, and any guidance about what to mention.
4. 4

   Names checked against the location's team

   Drafts respell staff names using a team list built from the location's website, your own past replies and repeated mentions in reviews. Names the list cannot confirm are left out, and the draft thanks the team instead.
5. 5

   A person posts, or parks it for sign-off

   Post reply sends it to Google, and the inbox shows Pending Google until it is live, or Rejected with the reason. Reply later puts a sensitive review on your Tasks until a reply is posted.

Below each draft, a Names in this reply panel shows any name that was corrected or left out, with one-click answers (works here, who they meant, or do not name them) that are saved so you are only asked once. You can also open the full team list from the inbox to fix a spelling, add a new starter, or mark someone who has left so replies never mention them.

On Pro and above, a location connected to its Business Profile can have an auto-reply rule. It is deliberately narrow: it covers 5 star reviews only or 4 stars and above, can be limited to ratings with no written review (the default), never replies to a 1 to 3 star review, never touches a review that already has a reply, and will not post a draft that still names someone the team list cannot confirm. That keeps the routine thank yous moving while every complaint stays with a person.

To see what each plan includes, including auto-reply and the extra review sources, compare the plans on our pricing page.

Questions people ask

Should we reply to every Google review, including star-only ratings?

Ideally yes, but in priority order. Every negative and mixed review should get a considered reply. Star-only positive ratings can get a short thank you, and this is the one band where a template or an automatic rule is reasonable. If capacity is tight, cut from the bottom of the triage list, never the top.

Who should sign the reply: the business, the branch or a named person?

Replies appear under the business, not your personal name.¹ A sign-off such as "The team at the Leeds clinic" works for most brands. A named manager on complaint replies can add accountability, but only if that person is happy to be contacted and is still in the role.

Can we edit or delete a reply later?

Yes. You can edit or delete an owner reply from your Business Profile.¹ If a reply you posted seems to have vanished, our post on missing Google review replies covers the usual causes.

Can we offer a refund to someone who left a bad review?

You can resolve a complaint, including with a refund, as long as it is not conditional on the review. Offering a refund or gift card in exchange for changing a negative review is given as an example of a banned practice in UK guidance.⁵ Resolve the issue, then leave the review decision to the customer.

Is it acceptable to use an agent to write replies?

Drafting with an agent is a sensible use of one, provided a person reads every reply that goes out on a negative or sensitive review and checks names and facts. The reviewer cares whether the reply is accurate and sincere, not who typed the first draft.

Do replies help us get more reviews?

The best published evidence, from hotels, found more reviews after businesses started responding.² The bigger driver is still asking every customer, which we cover in the personal-ask premium.

The short version

Put every location's reviews in one queue with a named owner. Answer the negative and oldest reviews first, against reply targets set by rating. Keep one brand voice, check every staff name, and take sensitive conversations offline. Never trade anything for a review or for changing one, and ask every customer, not just the happy ones. Let an agent draft, and let a person send. Do that consistently and the reply queue stops being a weekly fire drill and becomes part of how each branch is run.