Why review requests need an operating system
Occasional review requests create an inconsistent customer experience. Staff may ask at different moments, use different wording, forget the link or improvise when criticism arrives. Automation amplifies those gaps unless the business defines who receives a request and what happens next.
A review workflow connects six decisions. It defines the eligible customer moment, the neutral request, the route to Google, the person monitoring responses, the privacy and escalation rules, and the monthly learning review. It should sit beneath the broader work of optimising a Google Business Profile, without drifting into categories, service areas or a general local ranking checklist.
Google says reviews should reflect a genuine experience. Its guidance on getting and replying to reviews recommends valuing honest and balanced feedback, replying conversationally and protecting privacy. That makes the operating goal straightforward. Give every eligible customer a fair route to comment, then handle what they say consistently.
Set the policy boundaries before choosing tools
A compliant workflow asks for an honest account of a real experience. It doesn't ask for five stars, positive wording, a named staff member or a particular phrase. It doesn't screen customers by sentiment before deciding who receives the Google link.
Google's fake engagement and rating manipulation policy allows merchants to solicit genuine reviews without incentives or attempts to influence the rating or content. It prohibits paid or in-kind reviews, selectively soliciting positive reviews, discouraging negative reviews, pressuring customers on the premises, staff review quotas and requests for specific content.
| Practice | Policy-safe position |
|---|---|
| Neutral request | Ask eligible customers to describe their genuine experience honestly |
| Review gating | Don't send only satisfied customers to Google while diverting criticism elsewhere |
| Incentive | Don't offer money, discounts, gifts, loyalty points or prize entry for a Google review |
| Staff target | Give staff responsibility for following the process, without review quotas or named-staff prompts |
| Suggested wording | Explain how to access the review page, without scripting sentiment or content |
| Private feedback | Offer a service channel to everyone, without making it a condition before the Google link appears |
Australian law and Google policy answer different questions. The ACCC's online review guidance says fake or misleading reviews and arranged fake reviews are unlawful. It also warns against suppressing genuine negative reviews. In wider review contexts, an incentive must apply regardless of sentiment and be clearly disclosed to avoid misleading consumers.
Google's platform rule is stricter. Google prohibits incentives in exchange for a Google review, even when the reward is available for positive and negative feedback. For a request that directs somebody to Google, follow Google's no-incentive rule.
Violations can affect more than an individual review. Google's Business Profile restrictions guidance says fake-engagement enforcement can include removing reviews, temporarily stopping new reviews or ratings, temporarily unpublishing existing ratings or reviews, and displaying a consumer warning.
Choose the customer moment that earns a fair request
The right trigger comes after the customer has enough experience to form a view. For a trade, that could be confirmed job completion or a resolved return visit. For a professional service, it could be delivery of an agreed milestone, completion of an engagement or another point where the customer has received the promised work.
These are practical choices, not Google-prescribed timing rules. Map the real service journey and select a moment that is easy to verify in the system your team already uses. A paid invoice alone may be too early if delivery is incomplete. A closed job may be misleading if a defect or open complaint remains unresolved.
Use one eligibility rule across customers who reach the same trigger. A private service-recovery path can run alongside the review request, but dissatisfaction shouldn't remove access to the Google link. That separation prevents review gating and gives the business a direct way to resolve genuine problems.
Before sending anything, check whether the customer has already been asked, whether the experience is complete, whether contact permission and channel rules are satisfied, and whether an active dispute needs human review. Restraining duplicate or poorly timed messages protects the customer relationship without filtering by expected sentiment.
Build the request route
The shortest route is usually Google's own review destination. Google's review link and QR code instructions say a business can open its Business Profile, choose Read Reviews, then Get more reviews to copy the link or access the QR code. Google currently says the QR code can be generated through a computer browser, not a mobile device.
Google suggests placing the route in receipts, thank-you emails, chat follow-ups and in-store displays. Choose the channel that naturally follows the completed experience. Email can carry a little context, SMS suits a concise follow-up, and a printed QR code can support an in-person handover. A QR code on its own still needs plain wording that explains where it leads.
Test the link and QR code from a device that isn't signed into the profile owner account. Confirm that the correct business opens. Keep the destination controlled by the profile owner rather than a staff member's personal short-link account. If an automation sends the request, retain a visible owner, a failure queue and a way to stop a message before it goes out.
One restrained reminder may be reasonable when the customer hasn't responded, but Google doesn't prescribe an ideal delay or frequency. Decide whether a reminder suits the relationship and document that choice. Repeated prompting can turn an optional request into pressure.
The operating fields matter because automation will repeat whatever has been defined, including mistakes. Record them before switching a workflow on.
Write a neutral request people can answer honestly
Good request copy identifies the business, refers to the completed experience and makes honest feedback optional. It doesn't predict the customer's opinion or coach the response.
For email, adapt this structure:
Hi [first name], thank you for choosing [business] for [service or project]. If you'd like to share your experience, you can leave an honest Google review here: [review link]. Your feedback helps us understand what worked and what we can improve. Thank you, [sender name].
For SMS, keep the identity and destination clear:
Hi [first name], it's [sender] from [business]. If you'd like to share honest feedback about your recent experience, you can leave a Google review here: [review link]. Thank you.
For an in-person request:
If you'd like to share your experience, this QR code opens our Google review page. Honest feedback is welcome.
These templates intentionally avoid five-star language, positive-review prompts, staff names and suggested keywords. That keeps the request aligned with Google's rule against influencing a rating or review content.
Give every review a clear response route
The response owner needs enough authority to acknowledge ordinary feedback and a clear threshold for escalation. A rushed reply from the wrong person can reveal private information, argue about facts that haven't been checked or make a service issue harder to resolve.
For a positive review, thank the customer briefly and refer only to details they have already made public. Avoid turning the reply into an advertisement. For a mixed review, acknowledge both the useful feedback and the concern, then say what the team can examine.
For a negative review, verify the internal record before replying. A useful public response acknowledges the experience, stays factual and offers an appropriate private route. Google's reply guidance recommends professional, conversational responses and moving complex matters to phone or email to protect privacy.
Don't confirm that somebody is a customer or disclose their address, payment status, health information, legal matter, project details or private communications. This applies even when the reviewer has mentioned some details themselves. A safe response can be simple:
Thank you for raising this. We'd like to review what happened and discuss it directly. Please contact [role or business channel] so the right person can look into the details with you.
Escalate before replying when the review involves safety, health, discrimination, legal threats, payment disputes, vulnerable people or allegations of serious misconduct. Keep an internal record of the review, the evidence checked, the approved response and the recovery action. Get appropriate professional advice where the issue sits outside the team's competence.
Spam, impersonation and other policy-violating content belong on a different route. Preserve a record, assess the review against Google's content rules and use the reporting process when there is a specific policy basis. Don't report an authentic negative experience merely because it is damaging. If reviews disappear, restrictions appear or the whole profile becomes hard to find, use the Business Profile visibility and restriction diagnostic.
Measure the workflow through operating signals
The workflow should tell you whether the operation is functioning and what customers are teaching you. It doesn't need a target review count or a claim that request frequency, response speed or keywords create a predictable ranking result.
Record the number of eligible completed experiences, requests sent, delivery failures, Google reviews observed and replies completed. Add the channel, escalation state and a short theme label. Keep customer-sensitive detail in the appropriate business system, outside the public response log.
Review the themes monthly. Look for repeated praise that the service can substantiate, recurring friction, requests sent before work was truly complete, messages that failed, unresolved escalations and process steps that staff avoid. Choose one operating improvement and name its owner.
Review activity is one part of local search reporting. The guide to measuring Google Business Profile performance through qualified leads shows how to keep profile interactions separate from enquiries and revenue. That distinction prevents a review programme from being judged by a star average alone or credited with commercial outcomes the evidence can't support.
Know when the system needs coordinated support
A small business can run this workflow with a verified profile, one accountable owner, a reliable completion trigger, approved neutral copy and a documented escalation route. Start there. Test every customer-facing path and review the first month manually before increasing automation.
Coordinated help becomes useful when profile ownership is unclear, customer facts conflict with the website, requests can't be triggered reliably, sensitive replies lack governance, visibility changes accompany policy warnings or reporting can't connect activity with qualified demand. At that point, SEO support can bring the profile, website proof, local visibility and measurement into one implementation plan.
The practical decision is whether the business can name the trigger, owner, message, response rule and monthly measure today. If any field is missing, define it before sending the next automated request.