How to Automate Google Review Requests Safely

How do you automate Google review requests?

You automate Google review requests with a short workflow: a trigger that marks the job as finished, a wait, one message with your Google review link, one reminder, and a stop rule. The hard part is not the sending. It is making sure the workflow follows Google's contributor policy and the FTC's review rule, which most how-to pages for these tools mention in a line or skip. This is the kind of build our AI and automation services cover, and it is a small, low-risk first automation.

What does Google's policy actually allow?

Google allows you to ask customers for reviews of a genuine experience, but not to pay for them, filter who you ask, or pressure anyone. Google's Maps user-contributed content policy, checked on 13 November 2026, says merchants may "solicit or encourage the posting of content that does represent a genuine experience" without offering incentives or trying to influence the rating or content. The same page lists what merchants may not do:

• Offer incentives such as payment, discounts, free goods or services in exchange for a review, or for changing or removing a negative one.
• "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers."
• Ask staff to solicit a certain number of reviews, or reviews with specific content.
• "Require or pressure users to leave ratings or write reviews while on the premises."

It also treats content "based on a conflict of interest", including current or former employees, as a violation, and says content posted because of an incentive "will be removed from Maps." The page does not mention automated or bulk requests by name, so the safe reading is that automation is fine and the rules about who you ask and why still apply to every message it sends.

Google's Business Profile help adds practical points: you can ask customers to visit a link or scan a QR code, customers must be signed in to a Google Account to post, and replies are public, so keep them short and do not use them to offer deals.

Why is review gating the biggest mistake?

Review gating is the common automation design that asks "how was it?" first and sends only the happy answers to Google, which breaks Google's ban on selectively soliciting positive reviews. Many review tools and many guides for them present this as a feature: high ratings go to the public page, low ones to a private form.

Two sources set the limit:

• Google's policy bans "selectively solicit positive reviews from customers", as quoted above. The page does not use the phrase "review gating", but the conduct is exactly that.
• The FTC says in its questions and answers on the Consumer Reviews and Testimonials rule that the rule "does not contain a specific prohibition" on this practice, but that it "could violate the FTC Act". The rule has been in effect since October 21, 2024, and the FTC says courts can impose civil penalties for knowing violations of it.

We have read only the FTC's staff answers, not the rule text, because the official rule page was not reachable from our environment. This article is general information, not legal advice.

What to build instead (our reading, not Google's wording).

1. Send the same review request to every customer who completed the job, with no rating question before the link.
2. If you also want private feedback, offer it to everyone, next to the review link, not in place of it.
3. Never hide or delay the public link because of a score, a survey answer or a sentiment guess.
4. Read complaints in the inbox and fix them. A review request is not a way to avoid hearing them.

Our guide to marketing for aesthetic clinics makes the same point for a sector where reviews carry extra advertising rules.

What about incentives, quotas and in-store requests?

Offering a discount, a gift or a prize draw for a review is prohibited by Google, and the FTC adds that its rule does not prohibit incentives "as long as there isn't an express or implied requirement that the reviews have to express a particular sentiment", which is a lower bar than Google's. Google's rule is the stricter one for a Google review. The FTC also says offering incentives to remove negative reviews "could be an unfair practice in violation of the FTC Act".

Three other habits cause trouble:

• Staff targets. "Three reviews each this month" is the quota Google names. Measure the review rate of the whole flow instead.
• Tablets at the counter. Google says merchants should not pressure customers to review while on the premises. Hand over the QR code and let them post later, away from the counter.
• Employee and family reviews. Google treats a conflict of interest as a violation, so staff, former staff and relatives should not post.

On the other side, the FTC's Q&A says the rule does not prohibit simply asking satisfied customers to update their reviews, but threatening a reviewer, accusing them falsely or making groundless legal threats to get a review removed is covered by its review-suppression provision. Reply politely, and use Google's own tools for reviews that break its policy.

How do you get the Google review link and QR code?

You get both from your Business Profile, and the same link goes into every automated message. Google's help says you can ask customers to visit a Google link or scan a QR code. A search summary of that help page describes the path as opening your reviews and choosing "Get more reviews", but button labels vary by account and device, so follow what your own Business Profile shows. Test the link in a private browser window, signed in to a different Google Account from the one that manages the profile, and confirm that it opens the review box for the right location. Multi-location businesses need one link per location.

How do you build the sequence?

Build it in this order, and test each step with a real job before the next:

1. Choose the trigger from a system of record: the CRM stage "job complete", the paid invoice, or the attended appointment. Never trigger from a form fill, because the customer has not had the service yet.
2. Add exclusions: open complaints, refunds, people who opted out of messages, and anyone you have asked in the last 90 days. The 90 days is our starting rule, not a Google figure.
3. Wait. We start with the next business day for most service jobs and adjust from your own results.
4. Send one message in your voice, naming the person who did the work, with the link. Keep it plain. Do not mention the rating you hope for.
5. Send one reminder about a week later only if no review and no reply has arrived. Our rule of thumb is one request plus one reminder, then stop.
6. Route replies to a person. A "the engineer was late" reply should reach the owner as a service issue, not be followed by another automated nudge.
7. Alert on failure. A workflow that silently stops looks like a slow month.

Consent for texts and email

A review request sent by text is sent by your business to a customer's phone through an automated system. The consent, carrier-registration and opt-out rules in the US, UK and elsewhere are the same ones that govern lead follow-up, and we set them out with sources in how to automate lead follow-up. In short: collect separate SMS consent at the first enquiry and store it on the contact record, check it before every text, and use email where you have no text consent. Whether a review request counts as marketing under a given law is a question for your lawyer; the cautious route is to treat it as consented messaging.

Which tool should send the requests?

Any tool works if it can fire from a completed job, wait, check a condition and stop, and the policy rules above are your design brief for it. The four common routes:

We could not retrieve HighLevel's own review-request help page when writing this, so we describe no HighLevel setting by name; the third-party guides we found disagreed with each other. Check the vendor's current documentation before you rely on any field name, and see is GoHighLevel worth it if you are still choosing a platform.

How do you reply to reviews and measure the result?

Reply to reviews yourself, publicly, in a sentence or two. Google's help advises against the same generic thank-you for everyone and against offering deals in replies. Measure three numbers each month: requests sent, reviews received per request, and the share of reviews that mention a specific person or service. If the rate is low, fix the moment of asking and the message, not the number of reminders. Local businesses that rely on map results, such as a phone repair shop, usually find that review wording about a specific service is more useful than a high count alone, though we have no study to cite for that.

Should you build it yourself or get help?

One trigger, one email and one reminder is a fair do-it-yourself job in a CRM you already use. Help pays for itself when several sources feed the trigger, texts need consent and registration, locations multiply, or you want the replies routed and measured. If you are weighing it against other tasks, see what to automate first and what an automation agency costs. 1920 Agency is based in Islamabad, with locations in Rawalpindi and Lahore, and works with clients remotely. We quote after mapping the job.