A Review Response Playbook Template You Can Actually Hand to a New Location Manager

Most multi-location businesses that struggle with review replies already have a policy, in the sense that someone wrote a paragraph about tone once and put it in an onboarding doc. What they don't have is anything a location manager can actually open mid-shift, with a real review in front of them, and use in under a minute. That gap — not a missing framework — is why replies get delayed, why new hires either go silent or wing it, and why the tone drifts location to location even when everyone technically agrees on the rules. This is the playbook: real starting templates for the three situations that cover almost every review, plus the one-page version of the policy that makes them usable by someone who's never seen this document before.

How to actually use these — three rules first

• Fill in every bracket. A template with [PRODUCT/SERVICE] or [SPECIFIC DETAIL] still in it reads worse than no reply at all — it's visible proof nobody read the review.
• Never copy-paste the same filled-in reply twice. Google and customers both notice repetition across a listing; vary the opening line even when the situation is identical.
• Treat these as a starting draft, not a finished one — for anything in the negative/sensitive tier especially, read it once more before posting as if a stranger who wasn't there is about to read it.

Tier 1 — Routine positive (4-5 stars, no specific complaint)

This is most of what any location receives, and the fastest tier to reply to well. The only real mistake here is sounding like every other reply on the page.

Template: general thanks

Thank you so much for the kind words, [FIRST NAME]! We're glad your visit to [LOCATION NAME] went well, and we hope to see you again soon.

Template: thanks + specific mention

Thanks for the great review, [FIRST NAME]! We'll be sure to pass your comments about [SPECIFIC DETAIL — e.g., a staff member's name, a dish, a service] along to the team — it means a lot. See you again soon at [LOCATION NAME].

Template: thanks + light invite back

We really appreciate you taking the time to write this, [FIRST NAME]. [LOCATION NAME] is glad you had a great experience, and we'd love to have you back — [OPTIONAL: mention a seasonal item, new hours, or upcoming change if genuinely relevant].

Tier 2 — Neutral or mixed (3 stars, or a minor gripe inside a good review)

These need to acknowledge the specific comment, not just the star rating — a generic thanks on a review that mentions a real issue reads as not having been read at all.

Template: minor complaint, otherwise positive

Thank you for the honest feedback, [FIRST NAME]. We're glad you enjoyed [WHAT THEY LIKED] overall, and we hear you on [SPECIFIC ISSUE] — that's not the standard we hold ourselves to, and we're working on it. Hope to have the chance to change your mind about that one part next time.

Template: wait time / slow service

We appreciate you sticking with us, [FIRST NAME], and we're sorry the wait ran longer than it should have on [DAY/TIME IF MENTIONED]. That's useful for us to know about staffing at [LOCATION NAME] specifically — thank you for flagging it, and we hope the rest of your visit made up for it.

Template: price or value complaint

Thanks for the feedback, [FIRST NAME]. We know [PRODUCT/SERVICE] is a real investment, and we want it to feel worth it every time — we're sorry this visit didn't fully land that way. We'd genuinely like to hear more if you're open to it: [CONTACT METHOD].

Tier 3 — Negative or sensitive (serious complaint, safety, legal, refund)

These are the ones worth writing slowest, and the only tier where the goal of the public reply isn't to resolve anything — it's to show a future reader that the business took it seriously and moved the conversation somewhere it could actually be resolved. Never confirm details you can't verify, never argue, and always move to a private channel.

Template: general negative experience

[FIRST NAME], thank you for taking the time to share this, and we're sorry your experience at [LOCATION NAME] didn't meet the standard we hold ourselves to. We'd like to understand exactly what happened and make it right — please reach us at [CONTACT METHOD] with your visit date so we can look into this directly.

Template: something serious (safety, legal, discrimination — escalate first, reply second)

[FIRST NAME], we take this seriously and want to look into it directly rather than respond here without the full picture. Please contact us at [CONTACT METHOD — ideally a named manager, not a general inbox] at your earliest convenience so we can address this properly.

The one-page policy sheet

The templates above only stay consistent across locations if whoever's using them also has the four rules that sit above all of them — short enough to actually be read, not a document that gets skimmed once during onboarding and never again.

1. Reply within 24-48 hours for Tier 1 and 2, same-day for Tier 3. A well-written reply that arrives a week late reads as a business that doesn't care, regardless of the wording.
2. Never argue with a reviewer publicly, and never confirm a fact you can't personally verify — 'we looked into this' is fine, 'you're wrong about X' never is.
3. Anything alleging discrimination, a safety incident, or a legal threat skips the standard flow entirely and goes straight to whoever handles that at the company — not the location manager, and not a template.
4. Always fill in the brackets. If a location manager doesn't have a specific detail to add, that's a signal to actually go find one before replying, not a reason to leave it generic.

Where a template stops being enough

A filled-in template is a real improvement over a blank box, but it doesn't solve the two problems that actually cause multi-location reply programs to fail over time: nobody notices when a location quietly stops using the templates and drifts back to generic replies, and nobody's tracking which locations are running behind on response time until a customer complains publicly about it. Those are visibility problems, not writing problems — see our full framework on splitting the reply decision by review type, not by team, for how that gets solved without adding another person to the workflow.

Common mistakes

• Leaving a bracket unfilled — worse than no reply, since it's visible proof the review wasn't actually read.
• Using the exact same filled-in wording for every review of the same type, which starts to look templated to anyone reading several replies in a row.
• Letting a Tier 3 template go out without a second read — these are the replies most likely to be screenshotted.
• Treating this playbook as the finished policy rather than the starting draft — it still needs a real person's judgment on anything outside the routine cases.

FAQ

None of this replaces judgment — it replaces the blank box. Give a new location manager these templates and the one-page policy sheet, and they can write a reasonable, on-brand reply to almost anything that comes in on day one, without waiting for someone at headquarters to draft it for them or guessing at what the brand voice is supposed to sound like.