Eligibility rule
A plain rule that describes who receives the request without using satisfaction, rating likelihood, or staff preference.
The straight answer
Make the invitation easy, not the outcome biased.
Start with a defined group of customers who had the same genuine experience. Give them the official Google review link or QR code. Ask for an honest account, make it optional, and use the same neutral message regardless of whether you expect praise or criticism. Pause if the channel, consent, policy, or local rule is unclear.
What you leave with
Review-link check
A human-verified official Google destination and a no-incentive/no-pressure checklist.
Approval record
A small receipt documenting the exact copy, channel, timing, owner, and exceptions.
Route map
Six steps before any customer contact.
- Name the genuine experience. Define the completed service or product and the date range. This guide is for people who actually had the relevant experience, not a purchased list or a speculative prospect group.
- Set one neutral eligibility rule. Example: every customer who completed a defined service in a specified period, except operationally ineligible contacts. Do not use a “happy customer” filter, a four-star threshold, or a complaint-suppression branch.
- Prepare the official Google destination. A qualified owner, not an AI assistant, creates or confirms the current Google review link or QR code. Verify it reaches the intended business.
- Write a request that does not steer. Ask for an honest experience. Do not ask for a positive rating, include desired talking points, attach a discount, or tie a benefit to posting, changing, or removing a review.
- Run the human approval gate. An accountable person reviews the actual audience, contact basis, channel, timing, link, copy, and applicable rules. Nothing sends from this guide or worksheet.
- Improve the service, not the sample. Route negative feedback to a responsible owner. Fix the underlying experience; do not trade value for removal or hide the feedback from prospective customers.
AI roles, kept small
Safe preparation
- Draft a neutral template from an approved rule.
- Turn a human-provided policy note into a checklist.
- Find missing fields in a manually supplied approval packet.
- Summarize themes from approved, non-sensitive feedback.
Human approval required
- Choosing recipients, channel, timing, and copy.
- Checking contact permissions, consent, platform, industry, and local requirements.
- Opening a Google account/Profile or generating the actual destination.
- Sending, scheduling, posting, replying, escalating, or offering remediation.
Never delegate to AI
- Sentiment screening or “only ask happy customers” logic.
- Offering incentives or requesting a rating/content.
- Accessing/exporting a CRM, inbox, phone system, or Business Profile.
- Suppressing, editing, removing, or bargaining over feedback.
Agent roles
Planner, editor, approver
Planner: makes a blank packet. Editor: drafts neutral copy. Approver: accountable human who checks the real audience and decides whether any send may happen. There is no autonomous sender role.
Quick decision table
Keep the ask neutral.
| Situation | Safe route | Stop / change route |
|---|---|---|
| You want more Google reviews | Give every eligible customer the same optional request and official link/QR. | Do not ask only people likely to leave praise. |
| You want to use a coupon, drawing, or gift | Pause and obtain qualified policy/legal review before a program decision. | For Google reviews, do not offer value in exchange for any review action. |
| A customer is unhappy | Offer normal service recovery through an accountable human, independent of a review outcome. | Do not make help conditional on changing, removing, or withholding a review. |
| You want a staff member to ask in person | Use a voluntary, low-pressure reminder after the interaction, subject to policy review. | Do not require or pressure a customer to write while on the premises. |
| You want AI to run the campaign | Use AI only to prepare a reviewable blank packet. | Do not let it select customers, access systems, or send messages. |
Runnable artifact
Build your neutral request packet.
Use the printable worksheet to define the eligible group, verify the official destination, approve one message, log exceptions, and recheck policy. It is intentionally disconnected from customer systems.
Open worksheet.mdFailure modes
The satisfaction fork
“Happy?” surveys that route positive respondents to Google and complaints elsewhere can become review gating. Use one rule independent of sentiment.
The subtle bribe
A discount, giveaway entry, gift, refund, or other benefit tied to posting, changing, or removing a review is not a neutral request.
The automation leap
A polished template does not authorize bulk contact. Human approval of the actual audience, channel, and copy must come first.
Primary source desk
Policy first. Template second.
- Google: create a review link or QR code
- Google: tips to get more reviews
- Google Maps: prohibited and restricted content
- FTC: consumer reviews and testimonials rule Q&A
- O*NET: Market Research Analysts and Marketing Specialists
Reviewed July 14, 2026. This is educational workflow guidance, not legal advice or a guarantee of compliance, review volume, rating, ranking, leads, or revenue. Rules vary by platform, jurisdiction, contract, and industry.
Continue the local-growth route
Google Business Profile cleanup
Prepare a verified profile before routing customers to it. Open the related guide for the complete route.
LocalFlow
Place review requests in a wider local-business system, not as a standalone growth trick.
AI marketing operating system
Use a human approval gate before any AI-assisted customer-facing workflow.