Google Review Response Examples for Every Rating and Situation
Browse adaptable Google review response examples for positive, mixed, and negative feedback, with notes on why they work and what to personalize.
Use a Google review response example as a starting structure, never as text to paste unchanged. Pick the closest situation, replace brackets only with verified public details, remove anything you can't support, and get the right person's approval. Stop routine drafting for privacy, threats, safety, discrimination, or serious employee claims.
Every scenario and name below is fictional. None comes from a ReviewRobot customer or claims a result.
How to choose a Google review response example
Choose by situation and risk before choosing by star rating. For the full operating method, use the full Google review response process.
| Rating or signal | Situation | Goal | Tone | Escalation flag |
|---|---|---|---|---|
| 5 stars with detail | Specific praise | Recognize the public detail | Warm and brief | Low |
| 5 stars, no text | Star-only rating | Thank without inventing context | Very short | Low |
| 4 stars | Praise plus suggestion | Acknowledge both parts | Balanced | Low to medium |
| 1–3 stars | Routine service complaint | Show ownership and a next step | Calm | Medium |
| Any rating | Disputed facts or unknown reviewer | Invite private verification | Neutral | High |
| Any rating | Privacy, threat, safety, discrimination, or serious personnel claim | Protect people and facts first | No routine reply yet | Stop |
Make four edits to any example: identify one detail the reviewer made public, match the emotional temperature, add a real owner or contact route, and delete unverifiable or private material. Google advises businesses to keep replies short, relevant, personal, conversational, privacy-aware, and non-promotional (Google reply guidance, checked August 23, 2026).
Positive Google review response examples
| Fictional situation | Adaptable reply | Fields to change | Why it works | Weaker version to avoid | Escalation |
|---|---|---|---|---|---|
| 1. Detailed praise | “[Name], thank you for mentioning [public detail]. We'll pass your kind words to [public-facing team or role].” | Name, detail, team | Mirrors real praise without a pitch | “Thanks for the five stars! We're the best [keyword] in town.” | Low |
| 2. Short praise | “[Name], thank you for taking a moment to leave this note. We're glad you had a good experience with [public detail, if any].” | Name and only a stated detail | Stays proportionate | “Thank you for your detailed feedback about our staff and service.” | Low; omit detail if none exists |
| 3. Returning customer | “[Name], thank you for coming back and for mentioning [public detail]. We appreciate the trust you've placed in our team.” | Name, visible repeat-visit detail | Recognizes loyalty without inventing history | “We've loved serving you every month for years.” | Medium if records would be needed |
| 4. Employee mention | “[Name], thank you for recognizing [employee name already in the review]. We'll make sure [they] see your note.” | Public employee name, pronoun | Uses only what the reviewer published | “We'll add this to [employee]'s personnel file.” | Medium; no personnel details |
| 5. Milestone | “[Name], we're glad [public milestone] was a good experience. Thank you for letting our team be part of it.” | Public milestone | Fits the moment without claiming private context | “Congratulations on [private fact not in review].” | Medium if the milestone is sensitive |
| 6. Star-only rating | “[Name], thank you for the rating. We appreciate you taking the time.” | Name only | Doesn't invent a service or outcome | “We're thrilled you loved your appointment and our friendly staff.” | Low |
Four-star and mixed Google review response examples
| Fictional situation | Adaptable reply | Fields to change | Why it works | Weaker version to avoid | Escalation |
|---|---|---|---|---|---|
| 7. Praise plus suggestion | “[Name], thank you for the kind words about [public praise] and the suggestion about [public concern]. [Role] is reviewing that point.” | Both public details, real role | Acknowledges both sides without asking for five stars | “Thanks! What would earn the fifth star?” | Low |
| 8. Good result, poor communication | “[Name], we're glad [public result] went well, and we're sorry the updates weren't clear. [Role] can discuss the communication gap at [business contact].” | Result, issue, role, contact | Separates the result from the failure | “The result was good, so the communication shouldn't matter.” | Medium |
| 9. Wait-time concern | “[Name], thank you for noting the wait. We're reviewing how [public delay] was communicated; please contact [role] at [business contact] if you'd like to discuss the visit.” | Delay, role, contact | Doesn't invent the cause | “We were busy because everyone loves us.” | Medium |
| 10. Price concern | “[Name], we hear your concern about [public price issue]. We don't want to discuss account details here, but [role] can review the charge with you at [business contact].” | Public issue, role, contact | Protects billing details | “Your invoice proves the price was correct.” | High; verify before replying |
Don't offer a refund or discount on the condition that someone changes a rating. Google's policy prohibits incentives tied to posting, revising, or removing a review (Maps content policy, checked August 23, 2026).
Negative Google review response examples
Use the negative-review response playbook before adapting disputed, unknown-reviewer, privacy, threat, or serious allegation wording.
| Fictional situation | Adaptable reply | Fields to change | Why it works | Weaker version to avoid | Escalation |
|---|---|---|---|---|---|
| 11. Clear mistake | “[Name], you're right that we missed [verified public commitment]. [Role] is reviewing the handoff; contact us at [business contact] if you'd like to talk.” | Commitment, role, contact | Accepts only a checked mistake | “We're sorry you feel that way.” | Medium; verify first |
| 12. Long wait | “[Name], we're sorry the wait wasn't explained. We'd like to review the visit privately; please contact [role] at [business contact].” | Role, contact | Addresses the communication issue without exposing records | “You arrived late, so the wait was your fault.” | Medium |
| 13. Employee complaint | Hold routine wording. After an authorized review, if a reply is appropriate: “[Name], your concern has gone to the manager responsible for reviewing it. We won't discuss personnel matters publicly.” | Name, authorized manager | Protects the review and employee process | “That employee has been disciplined.” | Stop until internal or qualified review |
| 14. Disputed facts | “[Name], we've reviewed the information available and can't match every public detail. Please contact [senior role] at [business contact] so we can check without discussing private records here.” | Role, contact | Doesn't call the reviewer dishonest | “Our records prove you're lying.” | High |
| 15. Unknown reviewer | “We haven't identified the visit from the public details. Please contact [role] at [business contact] with the date and location so we can investigate privately.” | Role, contact | Describes uncertainty without declaring the review fake | “You're not a customer. Delete this.” | High; report only if policy fits |
| 16. Privacy limit | Hold routine wording. If cleared: “[Name], we take the concern seriously, but we can't discuss private account information here. Please contact [authorized role] at [business contact].” | Authorized role, contact | States the boundary without confirming private facts | “Your account shows [private detail].” | Stop until privacy review |
| 17. Resolved issue | “[Name], thank you for speaking with [role]. We're glad the immediate issue was addressed, and we'll keep the account details private.” | Role; use only if verified | Notes follow-through without asking for a review change | “Since we fixed it, please update your rating.” | Medium |
Google says verified businesses can reply publicly, reviewers receive a notification after an approved reply posts, and businesses can later edit or delete their replies (Google Business Profile Help, checked August 23, 2026). Notification, recovery, and a rating change are never guaranteed.
Three industry examples where the details change the reply
These remain fictional scenarios, not industry playbooks.
| Fictional situation | Adaptable reply | Fields to change | Why it works | Weaker version to avoid | Escalation |
|---|---|---|---|---|---|
| 18. Hotel reservation and privacy | “[Name], we're sorry the arrival process caused frustration. We can't discuss reservation details here; [front-desk manager] can review them at [business contact].” | Public issue, role, contact | Avoids confirming stay dates, room, or payment | “You booked the cheaper nonrefundable room.” | High; privacy check |
| 19. Auto-repair diagnosis dispute | “[Name], we understand you question [public diagnosis or charge]. [Service manager] can review the inspection record with you privately at [business contact].” | Public issue, role, contact | Doesn't claim a diagnosis is correct in public | “The scan proves your car had [condition].” | High; no technical advice |
| 20. Restaurant safety or service claim | Hold routine wording for a safety allegation. If cleared for public reply: “[Name], your concern went to [responsible manager]. Please contact us at [business contact] so we can review the visit privately.” | Manager, contact | Puts investigation before wording | “Nobody else got sick, so it wasn't us.” | Stop for safety review |
None of these examples claims a real case, customer, test, rating change, or business outcome.
An unknown name is not enough to call a review fake. Google says removal is limited to policy violations and documents the reporting route separately (Google reporting guidance, checked August 23, 2026).
How to personalize any example in four edits
| Generic phrase | Question to ask | Safer replacement | Reason |
|---|---|---|---|
| “Thanks for your feedback” | What public detail deserves acknowledgment? | “Thank you for mentioning [public detail]” | Shows attention without inventing context |
| “We'll look into it” | Who owns the next step, and is it approved? | “[Role] is reviewing [public issue]” | Gives the promise an owner |
| “Contact us” | Which public channel reaches the right person? | “Contact [role] at [business contact]” | Reduces another handoff |
| “We're sorry for everything” | What can the business honestly acknowledge? | “We're sorry [verified public problem] happened” | Avoids admitting an unchecked claim |
Keep the length proportionate. A star-only rating needs one short line; a serious complaint may need less public text because more work happens privately.
AI may help adapt a starting structure, but a person still has to supply verified context and approve the result. The separate guide explains how to adapt an example with AI and human review without turning this page into a prompt library.
Phrases to remove before you publish
| Remove | Problem | Replace with |
|---|---|---|
| “Thanks for your feedback” on every review | Reads as copied and ignores the detail | One public detail or a shorter thank-you |
| “You're wrong” | Starts a public argument | A factual boundary and private contact route |
| Repeated city and service keywords | Turns the reply into promotion | Natural wording about the review |
| “We guarantee this won't happen again” | Makes an unowned promise | A real, approved next step |
| Account, medical, financial, address, or personnel detail | Exposes private information | A privacy boundary |
| “We'll give you [benefit] if you remove this” | Ties recovery to review content | Handle recovery with no review condition |
| A coupon or sales pitch | Ignores the reviewer and conflicts with Google's guidance | A direct response |
| Blame aimed at the reviewer or employee | Escalates the dispute | Neutral wording and internal review |
Before approval, confirm the public detail, facts, privacy boundary, tone, real owner, contact route, and any promise. Read the reply aloud. If one sentence would make the case worse when quoted alone, rewrite it or hold publication.
ReviewRobot can prepare a draft based on the review and keep a person in control of editing, regeneration, approval, and publication. After the manual checks are complete, see how to draft, edit, and approve replies. The product doesn't know private case facts, publish without approval, or guarantee a rating, ranking, or conversion result.
Editorial status: This draft contains 20 fictional examples. A second human editor must still run the reuse test before publication and reject any row that invites invented facts, rote copying, public argument, or private disclosure.
“Thank you, Maya. We’re glad the repair was finished on time and that Alex kept you updated. We appreciate you choosing us.” A useful response names one real detail from the customer’s review and avoids generic filler. Replace the fictional details with facts the customer made public before posting.
Add ReviewRobot as a preferred source on Google
See more of our guides and research in Google Search.
