Review gating means screening customers by expected sentiment and only sending the happy ones to a public platform. Google's prohibited and restricted content policy for reviews forbids selective solicitation, so send the same request to every completed customer.

IndustryPublished Jul 29, 2026Updated Jul 29, 2026 8 min readBy Cross X Agency

Review Request Automation for Auto Shops, Without Gating

Q: What should trigger the request

Job status set to complete with the vehicle released, plus a short delay so the customer has driven the car. Invoice creation and scheduled appointment date are weaker triggers because they can precede actual pickup.

Q: One reminder, configurable interval

A single reminder to non-responders is a reasonable ceiling. Keep the interval configurable, adjust it from the shop's own results, and suppress it for anyone who already replied or left a review.

Q: Incentives are a trap worth avoiding

Offering discounts or prizes for reviews creates disclosure obligations under FTC guidance and can conflict with platform rules. Asking without offering anything is simpler and keeps the reviews credible.

Q: What to do with negative feedback

Offer a direct contact for anyone who had a problem while keeping the review link available to everyone, then respond publicly, briefly, and factually to criticism and move specifics to a private conversation.

A review request should fire on real job completion, ask everyone the same way, allow one reminder, and never filter by expected sentiment. Here is how to build it inside the platform rules.

Short answer: build the review request on a real completion trigger, send the same honest optional ask to every completed customer, allow one configurable reminder, do not filter by expected sentiment, keep consent and opt-out handling intact on text, and route dissatisfied feedback to a person rather than suppressing it.

Reviews matter to auto shops because most people choosing where to leave their car are strangers making a trust decision quickly. That makes the request worth automating and it also makes it worth doing correctly, because the shortcuts here are the ones platforms explicitly prohibit.

What should trigger the request

The trigger should be the moment the customer has actually experienced the work: vehicle picked up and job closed. Invoice creation is not the same event, since invoices are often generated before pickup, and the appointment date is not the same event either, since jobs run long. Where the shop management system exposes a job-completed or vehicle-released status, use that.

Good trigger: job status set to complete and vehicle released.
Weak trigger: invoice generated, which can precede pickup.
Weak trigger: scheduled appointment date, which ignores reschedules and delays.
Add a short delay after the trigger so the customer has driven the car before being asked about it.

Do not gate reviews

Review gating means asking customers how they feel first and only routing the happy ones to a public review platform. It is a common feature in review tools and it is prohibited by Google's prohibited and restricted content policy for reviews, which forbids soliciting reviews selectively from customers based on expected sentiment. The safe and honest build is the same request to everyone who completed a job.

Check the platform's own policy before configuring a tool

Google's prohibited and restricted content policy for reviews governs what a business may and may not do when asking for reviews, including selective solicitation. The FTC's guidance on endorsements and reviews covers incentives, disclosure, and the treatment of fake or suppressed reviews. Read both before enabling any review feature, and treat this guide as a summary rather than legal advice.

What the request should say

Short, plain, and clearly optional. Identify the shop, reference the vehicle or service so it does not read as a mass send, ask directly, and provide the link. Do not imply that a specific rating is expected and do not tie the request to any benefit.

Who is asking and from which shop.
One line of real context, such as the service and the vehicle.
A direct, optional ask with the review link.
An alternative path for problems: a name and a number for anyone who would rather talk first.
Opt-out language on text channels.

One reminder, configurable interval

A single reminder to people who did not respond is a reasonable ceiling. Beyond that the request becomes pressure, and pressure applied to a review ask is exactly the thing that produces the review nobody wants. Make the interval a setting rather than a hardcoded number so the shop can adjust from its own results, and suppress the reminder for anyone who already left a review or replied.

Illustrative sequence

A short delay after vehicle release, then one reminder several days later if there is no response, is an example structure to configure. It is not a claim about response rates. Adjust from the shop's own data and stop sending to anyone who has replied or opted out.

A review request sent by text is still an automated business message. It needs a valid consent basis, clear identification of the business, and immediate honoring of opt-out requests, and delivery depends on registration and carrier policy. The FCC consumer guide and Twilio's A2P 10DLC documentation cover the baseline, and a deeper walkthrough of the delivery side sits in why business texts are not sending.

Incentives are a trap worth avoiding

Offering a discount, a free service, or an entry into a drawing in exchange for a review creates disclosure obligations and can conflict with platform rules. The FTC's guidance on endorsements addresses incentivized reviews and the responsibilities that come with them. The uncomplicated default is to ask without offering anything, which also keeps the resulting reviews credible.

What to do with negative feedback

Give unhappy customers a real path, but do not use that path to divert them away from the public platform. A request can include a line offering a direct contact for anyone who had a problem, while the review link stays available to everyone regardless of how they feel. When a negative review does arrive, respond publicly, briefly, and factually, and move the specifics to a private conversation.

Practice	Status	Why
Same request to every completed customer	Recommended	Meets platform expectations and produces representative reviews
Sentiment survey before the review link	Avoid	Selective solicitation is prohibited by Google's review policy
Discount in exchange for a review	Avoid	Creates disclosure obligations and can conflict with platform rules
One reminder, then stop	Recommended	Keeps the ask from turning into pressure
Public factual response to criticism	Recommended	Visible to future readers and keeps the record accurate

Where this fits in the wider system

Review requests sit at the end of the job, which makes them part of the same customer record as intake, quoting, and follow-up rather than a separate tool. Keeping them in one system is what allows suppression rules to work across reactivation, follow-up, and review asks at the same time. That connected build is described on the Automotive Lead Leak page, and the reactivation side is covered in auto detailing customer reactivation.

Request a Lead Flow Review