You finish the job, the customer is happy, and you mean to ask for a review. Then the next call comes in and the moment passes. Automation fixes the forgetting. The catch is that some review tools also offer a “happy customers only” filter, and that one feature breaks Google’s review policy.
Review requests are one part of local SEO for contractors, alongside your profile and your website.
Here is how to automate the request the compliant way: who gets asked, what the message says, when it stops, and which workflow branches to never build.
Get review requests out after every job
Book a call and we’ll set up a request workflow that asks every completed customer the same way, with no gating and no repeat asks.
Let the Buzz BeginQuick answer: how should Google review automation work? Automate the request, never the review. Trigger one request when a job is marked complete, send the same neutral message to every eligible customer, send at most one reminder, and stop for anyone who already reviewed, already got a request, or opted out. Do not route only satisfied customers to Google: Google’s policy prohibits selectively asking for positive reviews.
Who should receive a review request?
Every customer whose job is actually complete, with exclusions based on facts, never on how you think they feel.
Send to: customers with a completed job and permission to contact them by the channel you are using.
Exclude, for these reasons only:
- The job is not complete yet.
- The customer opted out of messages, or you have no permission to text or email them.
- The customer already received a request for this job, or already left a review.
- The contact is an employee, a relative of an employee, or a business partner. Google’s review policy treats reviews based on those relationships as a conflict of interest.
- The contact is a test or duplicate record.
Notice what is not on the list: “customer seemed unhappy,” “gave a low score on our survey,” or “had a complaint.” Leaving those customers out because of their likely opinion is the definition of selective asking.
What should the request say?
One short, neutral message, the same for everyone:
“Hi [Name], thanks for choosing [Business] for [the job] on [day]. If you have a minute, we’d appreciate a Google review: [link]. Reply STOP to opt out of texts.”
Once reviews arrive, here is how to respond to Google reviews, good and bad.
Three rules keep it within Google’s policy:
- No incentives of any kind. Google prohibits offering payment, discounts, or free goods or services in exchange for a review. The federal consumer reviews rule separately bans incentives tied to positive or negative reviews, but Google’s rule is stricter: no incentive at all.
- Don’t ask for specific content, including mentioning a staff member by name. Google’s policy now calls this out directly.
- Don’t suggest a rating. Google allows review requests only when they don’t try to influence the rating or what the review says, so “leave us 5 stars” is out.
For in-person and email versions, use the scripts in our guide on how to ask for Google reviews.
When should requests send, and how do you stop repeats?
- Trigger on completion. Use the moment the job is marked complete in your schedule or CRM, not a calendar date that might be wrong if the visit moved.
- Send within the same day while the visit is fresh.
- One reminder, then stop. Limit it to a single follow-up a few days later.
- Record the request. Store the date a request was sent on the customer record and check it before every send.
- Recurring customers get asked once, not after every weekly pool cleaning or monthly pest visit. Decide how long to wait before asking a repeat customer again, write it down, and apply it to everyone.
Can you collect private feedback without gating?
Yes, if private feedback is offered alongside the Google review link, to everyone, rather than instead of it. A customer who had a bad experience should see the same Google link as everyone else, and may also use the private option if they prefer.
Workflow with prohibited branches
The allowed workflow:
- Job marked complete.
- Check exclusions: opted out, already asked, already reviewed, employee or relative, test record. If any apply, stop.
- Send the same neutral request with the Google link, optionally with a “tell us privately” link next to it.
- Wait a few days. If no review was detected and no reply came in, send one reminder.
- Record the request date and stop.
Branches to never build:
| Prohibited branch | Why it breaks the rules |
|---|---|
| “How did we do?” survey first, then the Google link only for 4 or 5 stars | Selectively asking for positive reviews |
| Private feedback form instead of the Google link for unhappy customers | Same problem: the Google ask depends on sentiment |
| “Leave a review and get 10% off your next visit” | Incentives are prohibited |
| Weekly review quota for each tech | Google’s policy bars asking staff to solicit a certain number of reviews |
| “Please mention [tech name] in your review” | Requests specific content and names staff |
| Asking the customer to leave the review on a tablet before the tech leaves | Google says merchants should not require or pressure reviews while on the premises |
| Sending requests only after a complaint has been resolved | Deciding who gets asked based on how they feel risks selective asking |
How do you audit the workflow?
Once a month, spend fifteen minutes checking:
- A random sample of completed jobs: did each one get exactly one request?
- No branch in the automation depends on a rating, survey score, or complaint flag.
- Message text contains no offer, no suggested rating, and no request to mention a person.
- Opt-outs were honored.
- No one on the team has a review quota.
Related guides cover choosing your Google Business Profile categories and tracking Google Business Profile leads.
Reviews are one part of a healthy profile; the rest is in our Google Business Profile checklist. If you want this run for you, automated review requests with responses handled are part of our Local Visibility service.
Frequently asked questions about Google review automation
Can I only send review requests to satisfied customers?
No. Google’s policy prohibits selectively asking for positive reviews. Send the same request to every eligible customer.
Can I offer a discount or entry into a drawing for a review?
No. Google prohibits incentives of any kind in exchange for reviews, whatever the review says.
Is it okay to ask in person?
Yes, as an invitation. Google says businesses should not require or pressure customers to leave a review while on the premises, so let the customer review later, on their own time.
How do I avoid asking the same customer twice?
Record the date of every request on the customer record and check it before sending. Recurring-service customers get asked once, then not again until the waiting period you set.
Final thoughts on Google review automation
The best review automation is boring on purpose: every completed customer, one neutral message, one reminder, and a record that stops repeats. Skip the satisfaction filters and incentives, and the reviews you collect will be ones you can keep. If you want a second look at your current setup, book a call with one of our hive specialists today.