Google Review Request Text Templates That Follow the Rules

A Google review request text should identify the business and location, follow a real completed customer event, invite honest feedback without predicting sentiment, use the correct owned Google review link, and honor messaging and privacy controls. It should not offer value for a review, ask only apparently happy customers, require a positive rating, tell staff or customers what to write, or count a sent request as a published review.

TaskChad sells Google Business Profile management, review workflows, messaging, and automation services. We have a commercial interest and are not a neutral evaluator. These templates are adaptable examples, not customer results, Google endorsement, or legal conclusions. This page is not legal advice, privacy advice, or industry-specific professional advice.

Standard review request text

Hi [First Name], thank you for choosing [Business Name] at [Location]. If you would like to share honest feedback about your experience, you can use our Google review link: [Owned Review Link]. Feedback is optional. [Required opt-out language]

Use after a verified completed service or other approved customer event. The message does not assume satisfaction and does not tell the person to leave five stars.

Verify business identity, location, review destination, customer event, destination number, send timing, suppression, and template version immediately before send.

Short review request

[Business Name]: If you would like to leave honest feedback about your completed visit, use [Owned Review Link]. Feedback is optional. [Required opt-out language]

Use the short version when business and location remain clear. Do not use a generic redirect controlled by an unrelated vendor when an owned or verified Google link is available.

Test the link from a signed-out mobile browser and confirm it opens the intended eligible Business Profile, not a similarly named location.

Location-specific request

Hi [First Name], thank you for visiting [Business Name, Location]. You may share honest feedback about that location here: [Location Review Link]. Feedback is optional. [Required opt-out language]

Carry the completed service location from the authoritative transaction or appointment record. A central brand should not send every customer to the strongest profile or corporate office.

Keep location corrections auditable. If the system cannot determine the right entity, assign a human exception rather than guessing.

Completed service request

Hi [First Name], [Business Name] has marked service [Reference] completed. If that record is correct and you would like to share honest feedback, use [Review Link]. If the service is not complete or you need help, reply HELP instead. [Required opt-out language]

This version includes a record-correction path. Do not send when the job, appointment, delivery, case, or payment remains disputed or incomplete under the business's policy.

The review workflow should stop if the person replies with a service problem. Create a private owner task and do not condition support on review removal or revision.

Appointment-based request

Thank you for visiting [Business Name] on [Date]. If you would like to leave honest feedback, use [Review Link]. If you need help with the appointment record, reply HELP. [Required opt-out language]

Use the minimum appointment detail. For sensitive services, omit the service type and follow qualified privacy guidance. A check-in or confirmed appointment is not proof of completion.

The appointment reminder templates remain a separate operational program. Do not combine a reminder and review request in one message.

Contractor or field-service request

Hi [First Name], thank you for working with [Business Name] on service [Reference]. If the work is complete and you want to share honest feedback, use [Review Link]. If anything still needs attention, reply HELP so the service team can review it. [Required opt-out language]

Do not automatically exclude HELP replies from future neutral review eligibility as a way to avoid negative feedback. Resolve the service case independently. Qualified leaders should define whether and when another optional request is appropriate.

Bilingual request

Hi [First Name], thank you for choosing [Business Name]. You may share honest feedback in English or Spanish here: [Review Link]. Gracias por elegir [Business Name]. Puede compartir comentarios honestos en inglés o español aquí: [Review Link]. Feedback is optional. Sus comentarios son opcionales. [Approved opt-out language]

Ensure both language versions communicate optional, honest feedback. Do not translate "review" into wording that implies complaint-only or praise-only feedback. Preserve a human language-support route.

Email version

Subject: Optional feedback for [Business Name]

Hi [Preferred Name],

Thank you for choosing [Business Name, Location]. If you would like to share honest feedback about your experience, you may use our Google review link: [Verified Link]. Feedback is optional and does not affect service or support.

If you need help with an unresolved issue, contact [Owned Support Route].

Keep review and support destinations separate without filtering based on sentiment. The email should not say the business needs a high rating or ask the customer to revise criticism.

In-person or receipt wording

Your honest feedback is optional and welcome at [Short Owned Review Route or QR Code]. If you need service help, contact [Support Route].

QR codes and printed links need the same entity verification and change control. Test them after profile merges, moves, ownership changes, or vendor migrations.

Do not have staff hover while a customer writes or provide suggested review language. The request should not create pressure.

A follow-up request that remains neutral

Hi [First Name], this is the final optional feedback reminder from [Business Name] for [completed event/reference]. If you want to share an honest Google review, use [Review Link]. No response is required. [Required opt-out language]

Use only when the business has approved a second attempt and the recipient remains eligible. Cap frequency. Do not repeatedly contact silent customers or create urgency around the review.

Wrong location correction

We previously sent a review link for the wrong [Business Name] location. Please disregard that link. If you choose to share honest feedback about [Correct Location], use [Correct Link]. We are sorry for the confusion.

Preserve the incident, affected records, wrong link, correct entity, repair owner, and suppression decision. Do not ask a customer to copy or move a review between profiles.

Service-problem response

Thank you for telling us. We have stopped the review-request sequence and assigned your service message to [Team] under [Reference]. The current next step is [Verified Step]. You are not required to change or remove any public feedback to receive support.

Do not negotiate review removal, threaten, disclose private facts, or ask a model to argue the case. Keep the private incident outcome separate from the public review and request campaign.

The Google Business Profile review management guide covers public response and escalation.

What Google's policy sources say

Google's tips for getting more reviews, checked August 13, 2026, explains that businesses can create and share a review link or QR code and says incentives for reviews are prohibited. Google's review-response guidance, also checked August 13, 2026, describes replying to reviews.

Use the current official account and policy surfaces rather than a copied vendor rule. Google can change product features and enforcement. These sources do not endorse TaskChad or assure that a request, review, response, or profile will remain published.

Do not review-gate

Review gating includes sending the public link only to people predicted to be happy, using a private survey to divert criticism while inviting praise publicly, or asking staff to decide which customers "deserve" a request based on expected rating.

Define eligibility from neutral operational facts: correct business and location, completed approved event, valid destination, permitted timing and channel, no duplicate request, and no active exclusion under a consistently applied policy.

If a customer has an unresolved service issue, route it for help. Do not make resolution conditional on staying silent, changing a rating, or deleting a review. Document the review-request and service-recovery programs separately.

Do not incentivize or script sentiment

Avoid discounts, gifts, sweepstakes, loyalty points, refunds, priority service, staff rewards tied to positive reviews, or any other value offered for review content. Do not provide sample praise, keywords, star guidance, or city-service phrases to copy.

The business may ask for honest feedback in the customer's own words. Keep staff training explicit: identify the optional route, step away, and do not watch the rating selection.

Protect privacy and confidential relationships

Use the minimum detail required to identify the business event. Sensitive health, legal, financial, care, housing, employment, or other relationships may need more restrictive wording and qualified review.

Do not put diagnoses, matter types, account issues, addresses, payment information, or complaint details in URLs or general analytics events. If a person posts private information publicly, respond neutrally and move the case to an approved channel.

Build the eligibility and suppression system

Store customer and location ID, completed event and evidence, event date, eligible date, contact channel decision, message version, review link ID, send count, suppression, open service case, provider receipt, reply, and terminal state.

Exclude duplicates, staff, vendors where inappropriate, test records, invalid destinations, wrong persons, opt-outs, uncompleted events, and records already requested under the frequency rule. Apply eligibility at enqueue and immediately before send.

The automated review request workflow owns the system architecture, human boundaries, and audit design.

Route clicks and reviews cautiously

A link click does not prove a review was submitted. A new review may not be attributable to one request, and public reviewer names may not safely or reliably match customer records. Avoid invasive matching.

Report requests sent, delivery where supported, link interactions, new reviews at profile level, review-request replies, opt-outs, wrong persons, service escalations, and unknown attribution separately. Do not claim a causal rating increase from a campaign without appropriate evidence.

Test the workflow

Use controlled records for completed service, incomplete service, wrong location, duplicate customer, open complaint, opt-out, wrong number, link failure, merged profile, multilingual request, and staff/test account. Do not publish synthetic reviews.

Verify entity, link, optional language, provider receipt, reply route, suppression, service escalation, and analytics. Stop the launch if a customer can reach the wrong profile or if negative replies disappear.

Measure business outcomes without corrupting review integrity

Track eligible events, exclusions by reason, queued requests, suppressed sends, messages sent, provider delivery where supported, failures, replies, opt-outs, wrong persons, link interactions, profile-level review movement, private service cases, and unknown attribution.

Keep reviews separate from leads and revenue. A review may influence future discovery, but it is not a click, qualified lead, booked service, or collected payment. Compare profile impressions, clicks, calls, GA4 activity, completed services, and revenue through their own evidence trails.

Audit staff and vendor behavior

Quarterly, observe how review requests are triggered at the counter, in the field, by email, by text, and through third-party software. Verify that the same neutral eligibility rules apply, customers are not watched or coached, links reach the correct location, and open service cases receive support without pressure.

Inspect staff incentives and vendor dashboards for hidden rating filters, sentiment gates, automatic retries, or language that suggests only positive feedback. Disable any path the business cannot explain and audit.

Keep Google Business Profile optimization checklist, Google Business Profile post strategy, and review requests as separate operations. Activity in one does not prove performance in another.

Reconcile profile moves and merges

When a business moves, merges a duplicate, changes ownership, or restructures locations, freeze automated review requests until the correct public entity and link are verified. Inventory every stored review URL, QR code, receipt footer, text template, email workflow, and staff handout.

Use controlled tests without publishing a review. Confirm the intended profile opens on mobile and desktop and that location identity remains clear. Retire stale links and preserve the change receipt so old campaigns cannot restart with the wrong destination.

If review requests are active but the business cannot prove neutral eligibility, correct location, customer support, and policy-safe suppression, run the TaskChad Revenue Leak Score. We can map the workflow without guaranteeing reviews, ratings, rankings, or revenue.