How to Automate Google Review Requests (Without Breaking the Rules)

Muhammad Shahid·AI-Powered Digital Marketing Consultant

Google Ads Certified

Meta Blueprint Certified

Google Analytics Certified

Updated October 2026

A small business can automatically request Google reviews by connecting the event that marks a finished job, such as a closed job, a paid invoice or a patient checkout, to a message that sends the customer the business’s Google review link. The software waits a set time, sends one request, sends one reminder if needed, then stops. Nobody has to remember, and nobody chooses who gets asked.

That last part matters more than most guides admit. Almost every page ranking for this topic is written by a company selling a review tool, and most of them skip the rules entirely. Google bans incentives and selective asking. The US now has a federal rule on reviews with civil penalties behind it. Review texts in the US run into consent law and carrier registration. A badly built automation can scale a policy breach as easily as it scales reviews.

I build these systems for local service businesses as part of my local SEO work, mostly for trades, clinics and home services. This guide is the setup I actually use: the link, the trigger, the delay by trade, the message, the reminder and stop rules, the compliance checklist, and what to do once the reviews arrive.

Why automate review requests instead of asking in person?

Because asking works, but people forget to ask. BrightLocal’s Local Consumer Review Survey 2026 found that 78% of consumers were asked to leave a review in the past year, and 83% of those who were asked went on to leave one. The request is the lever. Automation simply makes sure it is pulled after every single job, not just on the days the owner remembers.

The same survey, based on 1,002 US adults and published in February 2026, found that 97% of consumers read online reviews of local businesses and 74% look for reviews written in the last three months. That second number is the one I show owners. A business with 300 reviews, most of them from 2022, looks less active to a buyer than a competitor with 80 reviews and five from last week.

What reviews do for your local ranking

Google says reviews feed local ranking, but it does not say by how much. Its own guide to improving local ranking groups them under prominence: “This factor’s also based on info like how many websites link to your business and how many reviews you have.” It adds: “More reviews and positive ratings can help your business’s local ranking.”

“Can help” is the honest ceiling. Reviews sit alongside relevance and distance, and a business two suburbs away from the searcher will not outrank a closer one on review count alone. Anyone promising a map pack position from a review campaign is selling a guess. I cover how the pieces fit in my guide to what local SEO actually is.

Where reviews do their clearest work is after the ranking: the moment a buyer compares three businesses on the map. That is a trust decision, and it is why I treat review requests as part of the system that turns visibility into calls, not as a reputation side project.

Why manual asking breaks down

In the businesses I work with, the pattern is always the same. The owner asks for reviews for two weeks after reading an article, the count jumps, then a busy month arrives and the asking stops. Reviews come in bursts, then go quiet for months. The failure is the system, not the person. A technician finishing a hot job at 6 p.m. is not thinking about Google.

• Memory fails under load. The busiest weeks produce the most happy customers and the fewest requests.
• People choose who to ask. Staff naturally ask the friendly customers, which drifts toward the selective asking Google bans.
• Timing drifts. A request sent two weeks later gets a fraction of the response of one sent the same afternoon.
• Nothing gets measured. Without a log of requests sent, you cannot tell a weak message from a weak month.

How does an automated review request system work?

An automated review request system has four parts and one rule. The parts are a trigger (the event that says the job is done), a delay (how long to wait), a message (one short text or email carrying your Google review link) and a stop condition (reviewed, replied, opted out or reminder sent). The rule is that every customer goes through the same flow, with no filter.

It is a narrow slice of reputation management, and it sits in the same place in the business as automated lead follow-up: the software handles timing and memory, and a person handles anything that needs judgement. You do not need a dedicated platform to start. Most businesses already own software that knows when a job is finished.

Step 1: How do you get your Google review link and QR code?

Get the link from Google itself. Google’s help page on creating a review link or QR code gives the path: go to your Business Profile, select Read Reviews, then Get more reviews, and select Copy. That link opens the review box for your listing directly, which removes a step for the customer.

1. Sign in to the Google account that manages your Google Business Profile and search your business name, or open it in Google Maps.
2. Select Read Reviews, then Get more reviews. On some accounts the button is labelled “Ask for reviews”.
3. Select Copy to copy the review link, and paste it somewhere you can find it, such as a note in your CRM.
4. For a QR code, right-click the code in the same panel and save the image. Google notes that review QR codes “can only be generated on a computer browser, not on mobile devices.”
5. Test the link on a phone that is not signed in to your business account, so you see exactly what a customer sees.

The QR code still has a job

A QR code on an invoice, a receipt or a card left on the counter catches customers who were never going to open a text. Use it as a second route, not a replacement. One caution from Google’s own policy: do not hand a customer a tablet at the front desk and stand over them. More on that below.

Some guides send you to third-party tools that build a link from your Place ID. That works as a fallback if you do not have profile access yet, and my free review link generator does the same job, but Google’s native link is the one I use, because it is official and it does not break when a tool changes. Customers also need to be signed in to a Google account to post, as Google’s reviews help page notes, so expect a small share to drop off at the sign-in step.

Step 2: What should trigger the review request?

The trigger should be the software event that proves the job is finished: a job marked complete, an invoice paid, or a patient checked out. Use the system your team already updates every day, because a trigger only fires if someone presses the button. A review request fired from a booking date rather than a completion event will eventually reach a customer whose job was cancelled.

Field service and practice software

Many trade platforms now include review requests. Jobber’s reviews feature can send a request when a job closes, a visit is completed or an invoice is paid, and it states that “Jobber only sends one review request to a given client every 6 months.” Housecall Pro’s reviews app lets you turn on automatic emails to collect reviews after a job is finished or paid.

ServiceTitan accounts usually connect to a review platform through an integration rather than a built-in feature, so check what your plan includes before you buy a second tool. Dental and medical practice software often has its own patient messaging module. If the native option exists and the team already lives in that system, I use it, even when it is less flexible.

CRMs and connectors

If the business runs on a customer relationship management system, the trigger is usually a pipeline stage change, such as moving a deal to Won or Job Complete. Where the job software and the messaging tool do not talk to each other, a connector like Zapier can pass the completed-job event to whatever sends the text. Keep it to one connection. Every extra hop is another place it can silently break.

Whatever the setup, exclude a few cases on purpose: cancelled jobs, warranty callbacks still open, internal test records and customers who have already opted out of messages. Those are operational exclusions. Excluding a customer because you think they are unhappy is not, and that difference is the whole of the next policy section.

Step 3: How long after the job should the request go out?

Send it while the visit is fresh but after the result is obvious. For most service trades that is one to three hours after the job closes. For clinics, the same day after checkout. For bigger projects, after handover rather than after the last day on site. Avoid late evenings: a review request at 10 p.m. reads as noise.

These are my working defaults across the accounts I manage, not a published standard. Adjust them by watching your own completion rates for a month.

One clinic note: keep treatment details out of the message entirely. “Thanks for visiting us today” is enough. A text that names a procedure can expose health information to whoever sees the phone screen, and it is never needed to get the review.

Step 4: What should a review request text say?

A review request text should name the business and the person, thank the customer for something specific to the visit, ask one question, include the link and offer an opt-out. Keep it under about 300 characters so it reads in one glance. Do not ask for five stars, do not suggest wording, and do not promise anything in return.

Google’s Maps content policy is specific here. Merchants should not “request that specific content be included” in a review. So “Please mention our fast service!” is out, and so is “If you were happy, please leave us 5 stars.” Here are three templates I start from:

Text or email?

SMS is usually my first channel when consent exists, because the customer is holding the phone the review gets written on. Email is the fallback and the better choice at night; Jobber’s help article notes its own late-evening requests go by email only. Review vendors publish large SMS-versus-email multipliers, but I have not found an independent study behind them, so I do not quote one.

For the email version, standard email marketing rules apply: a recognisable sender name, a plain subject line such as “How did today’s visit go?”, one button to the review link and a working unsubscribe. Write both in the owner’s voice. Customers can tell when a message was written by a vendor template.

Step 5: How many reminders, and when should it stop?

One reminder, then stop. Send the first request, wait three to five days, send a single reminder to anyone who has not reviewed or replied, and end the sequence. A third and fourth message rarely adds reviews and reliably adds opt-outs and irritation. The stop rules matter as much as the send rules.

• Stop on reply. If the customer replies with a complaint or a question, the sequence ends and a person responds.
• Stop on opt-out. STOP, unsubscribe and their variants end every message, not just the review flow.
• Stop on review, where you can detect it. Many tools match new Google reviews to customer names. Where they cannot, the one-reminder cap does the job.
• Cap recurring customers. A weekly cleaning client should not get 52 requests a year. One every six months, as Jobber enforces, is a sensible ceiling.
• Respect quiet hours. I send between 9 a.m. and 8 p.m. local time and hold anything outside that window.

The cap is also why recency needs a steady flow rather than a campaign. A business that finishes 40 jobs a month and asks every customer once builds a stream of fresh reviews. A business that blasts its whole customer list once a year gets a spike, then a long silence that buyers can see.

What do Google’s review rules allow?

Google allows and encourages asking customers for reviews, including through a link or QR code. It bans paying for reviews in any form, asking only happy customers, discouraging negative reviews, requesting specific content and pressuring customers on the premises. These rules sit in the Maps user-contributed content policy, and reviews that break them can be removed.

Google’s prohibited content policy says merchants may not “Offer incentives – such as payment, discounts, free goods and/or services – in exchange for posting any review or revision or removal of a negative review.” Under the separate heading of Rating Manipulation, it bans merchants that “Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.”

The parts that catch automation

• Prize draws and discounts. “Leave a review to enter our monthly draw” is an incentive. Google’s tips page calls incentivised reviews “fake & misleading content” that is “strictly prohibited.”
• Staff quotas. The policy also bans “Merchants requesting that staff solicit a certain number of reviews.” Automation removes the need for a quota at all.
• On-premises pressure. Merchants “should not require or pressure users to leave ratings or write reviews while on the premises.” A QR code on the counter is fine. Standing over the customer is not.
• Review content. No scripted wording, keywords or star requests in the message.

Is review gating allowed?

Not on Google. Review gating means asking customers to rate you first, then sending only the happy ones to Google and routing the rest to a private form. Google’s policy bans selectively soliciting positive reviews, which is exactly what gating does. Some review tools still offer it, and at least one ranking guide I read recommends leaving unhappy customers out of request batches.

The US rule is different, and the difference is worth knowing. The Federal Trade Commission’s own Q&A on its review rule answers the gating question this way: “The rule does not contain a specific prohibition against such conduct. But this practice could violate the FTC Act.” So gating is a clear Google ban and a legal risk in the US, not a specific federal rule breach.

How to keep a private feedback option without gating

You can still give customers a private way to raise a problem. The test is simple: does every customer receive the public Google link, whatever they say? If yes, a line like “If anything was not right, reply here and I will sort it” is good service. If a low score removes the Google link from the flow, it is gating. I set up client automations so the review link goes out before any rating question, which makes the distinction impossible to blur.

Which laws apply to automated review requests?

Three layers apply on top of Google’s policy: rules on fake and incentivised reviews (the FTC rule in the US, the DMCC Act in the UK), rules on texting (consent law and carrier registration) and rules on email. None of them stop you from asking customers for honest reviews. They govern rewards, suppression, consent and opt-outs. This section is general information, not legal advice.

The FTC Consumer Reviews and Testimonials rule

The FTC announced its final rule on 14 August 2024, and it took effect on 21 October 2024. Section 465.4 makes it unlawful for a business to give incentives “conditioned expressly or by implication on, the writing or creation of consumer reviews expressing a particular sentiment.” Section 465.7 targets review suppression through threats, intimidation or false accusations.

The FTC says the rule “authorizes courts to impose civil penalties for knowing violations.” The inflation-adjusted maximum published in the Federal Register in January 2025 was $53,088 per violation. For most small businesses the practical lesson is short: no rewards tied to review sentiment, and never pressure anyone to remove a review.

Texting consent and carrier registration in the US

The Telephone Consumer Protection Act of 1991 treats texts like calls, and whether a post-job review request counts as a marketing message is not settled. My approach is to remove the question: collect texting consent at booking, with wording that mentions follow-up and review messages, and keep a record of it. The FCC’s 2024 revocation-of-consent order also means words like stop, quit, cancel and unsubscribe must be honoured.

Separately, carriers require registration for business texting from ordinary 10-digit numbers. Twilio’s A2P 10DLC documentation states: “Anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register for A2P 10DLC.” Registration covers your brand and your use case, and unregistered traffic faces more filtering and extra carrier fees. Most review and field-service platforms walk you through it.

Email, the UK and everywhere else

Review emails in the US fall under the CAN-SPAM Act of 2003 basics: honest sender details, a physical address and a working unsubscribe. In the UK, the Competition and Markets Authority’s fake reviews guidance, published in April 2025, explains the ban on fake and concealed incentivised reviews under the Digital Markets, Competition and Consumers Act 2024.

Wherever the business is based, the same three habits cover most of the risk: get consent before you text, identify the business in every message, and make opting out instant. Then check your own country’s messaging rules before the first automated message goes out.

Do you need a dedicated review tool?

Not to start. If your job software already sends review requests, switch that on first. A dedicated review platform earns its cost when you run several locations, need requests across many review sites, want one inbox for every review, or need reporting by technician and location. For a single-location trade business, the native feature plus a reminder usually covers it.

If you do buy a platform, check two settings on day one: that any “rate us first” screen is turned off or always shows the Google link, and that texting runs through a registered sender such as Twilio or the platform’s own registered numbers. Those two settings are where most compliance problems I find in existing setups come from.

What should you do once the reviews arrive?

Reply to every review, positive and negative, within a few days. Google’s own guidance says “Your replies are public and help you build good relationships with customers.” BrightLocal’s 2026 survey found 89% of consumers expect businesses to respond to reviews, and 81% expect that reply within a week. Replies are read by the next buyer, not just the reviewer.

Where AI helps and where it does not

AI is useful for drafting replies, especially for a business getting 30 or more reviews a month. I would not let it post unattended. The same BrightLocal survey found 50% of consumers are unlikely to choose a business whose responses look templated or generic. A short, specific reply that names the job beats a polished paragraph that could sit under any review on Google Maps.

For negative reviews, a person replies, every time. Acknowledge the problem, take the detail offline and fix it if you can. Never threaten, never pressure the customer to remove the review and never offer something in exchange for an edit. That last one breaks Google’s policy and, in the US, runs straight into the FTC rule on review suppression.

How do you measure whether review automation is working?

Track four numbers each month: requests sent, the share of requests that became a review, new reviews per month and the age of your most recent review. The first two tell you whether the system works. The last two tell you what a buyer sees. Pull a baseline of the last 90 days before you switch anything on, or you will not know what changed.

• Requests sent vs jobs completed: should be close to 100%, minus your operational exclusions. A gap means the trigger is not firing.
• Request-to-review rate: varies by trade and channel. Watch your own trend rather than a vendor benchmark.
• Reviews per month: steady beats spiky, given that 74% of consumers look for reviews from the last three months.
• Opt-out rate: if it climbs, the message, timing or frequency needs work.
• Reply rate and reply time: every review answered, ideally inside a week.

Reviews are one part of how a local business gets chosen, alongside the Google Business Profile itself, the website and how fast calls are answered. That is the same system I describe in map pack vs AI search, where review signals also feed how answer engines describe a business. Good search engine optimization gets you seen. Fresh, honest reviews help you get picked.

How I would set this up for a local service business

In order, this is the build I recommend for a single-location business. Most of it fits into an afternoon if the job software already has a review feature:

1. Copy the official review link from Google Business Profile and test it on a signed-out phone.
2. Check consent in your booking flow, and register for A2P 10DLC if you text US customers from a 10-digit number.
3. Pick the trigger in the system your team already updates: job closed, invoice paid or checkout.
4. Set the delay for your trade and the quiet hours.
5. Write the request and one reminder in your own voice, with no star request and an opt-out.
6. Switch off any gating screen and remove any reward language.
7. Set the reply routine, with a named person approving replies to negative reviews.
8. Review the numbers monthly against your 90-day baseline.

Review requests are one of the cheapest parts of local growth to fix, because the happy customers already exist. If you want this connected to your Google Business Profile, your job software and the rest of your local SEO, book a Local Visibility Audit and I will show you where the review flow is leaking first.

Frequently asked questions about automating Google review requests

The questions owners ask me most before they switch it on.