Customers will mostly leave a review if you ask them. According to BrightLocal, 83% of the people who were asked to leave one this year went on to do it. The hard part is that busy owners don’t ask, because the phone rings and a truck won’t start and Tuesday turns into last month.
Automated review requests take the remembering off your list, and that is nearly all they do. The rest of this article is the setup we’d build and the rules that decide what you can do with it.
Why asking by hand fails
When asking depends on memory, you ask after the jobs that went well, on the days you think of it. Your profile gets five reviews in one week in March and nothing until fall.
Readers look at the dates. In BrightLocal’s Local Consumer Review Survey 2026, a panel of U.S. adults, 74% of consumers said they look for reviews written in the last three months. Picture a homeowner in Bethlehem choosing between two carpet cleaners with similar ratings. One has a review from last week about a flooded basement dried out in a day. The other’s newest review is from spring.
Recent reviews are also one input into how a business appears in local results, alongside several others. We cover the rest in our guide to ranking in the Google map pack.
Automated review requests should fire from a real event
The request should be triggered by something that happened in your business: a job marked complete, an invoice paid, an appointment checked out. A monthly email to your whole list is easier to set up, but it brings back the old problem. You get a burst of reviews, and the request lands on people whose repair is a distant memory.
An event trigger sends one request per job while the work is on the customer’s mind. It’s where we’d start in any marketing automation setup, because everything else depends on it. The automation can only react to what your team records. If jobs get closed out whenever someone remembers, the requests go out whenever someone remembers, and you have automated the old problem.
So we’d ask about your day first. Which event is recorded on every single job, and by whom? Does the technician close the job from the truck, or does someone in the office catch up on Friday afternoon?
Timing depends on what you sell. A plumber who just stopped a leak can ask the same day or the next morning. For auto repair, the day after pickup suits better, once the customer has driven the car. Whatever the timing, set a sending window. A job closed out at nine at night should wait until morning, because a late text can turn a pleased customer into an annoyed one.
Ask by text first, email second, and send one link
A text is usually the better way to ask. People read it fast, on the phone where they are already signed in to Google. Email covers customers with no mobile number on file or who haven’t agreed to be texted.
That agreement comes first. Ask at booking or intake, with a checkbox on the form or a line your front desk reads aloud: “Can we text you about your appointment and follow up afterward?” Store the answer in the customer record and have the automation check it before sending. Texting consent has its own rules, so what you prepare is the record, and your attorney or texting provider confirms what it must cover.
Then use one link, the one Google provides for requesting reviews on your Google Business Profile, which opens the review form directly. A homepage link or a page with a row of review sites adds steps, and each step loses some people. We’ve written separately about getting more calls from your Google Business Profile.
The message should come from a named person and, where your records are clean, mention the job: “Hi Karen, it’s Dave, who replaced your water heater today. Thanks for having us out. If you have a minute, would you leave us a Google review? Here’s the link.” No suggested star rating, no hints about what to write. If your job types are internal shorthand, leave the job out. A plain thank-you beats warmly thanking someone for their “SVC CALL MISC.”
One request, one reminder, then stop
The whole sequence is two messages. The request goes out, and a few days later one short reminder goes to anyone who hasn’t opened the link. A third message rarely earns a review, and it can make a satisfied customer remember you as the company that kept texting.
Repeat customers need a rule of their own. Say you run a lawn care company in Easton and a customer is on a weekly route. Without a quiet period, that household could be asked every few visits. We’d set the gap in months.
Two parts stay human. First, a sentence on the way out: “You’ll get a text from us later today with a link for a review, and it really helps us.” Now the text is expected, and it comes from someone the customer just met. Second, someone has to read the replies. Some customers answer the text instead of using the link, and now and then one mentions mud on the stairs. That should reach a person the same day, because it is a chance to put something right before it becomes the review.
Replies to the reviews themselves stay human too. BrightLocal’s survey found most consumers expect business owners to respond. Pick someone who knows the work well enough to thank a customer by name and answer criticism calmly.
Google and FTC rules for review requests
Some setups ask “How did we do?” first, then send happy customers to Google and unhappy ones to a private form. That is review gating, and Google doesn’t allow it. Google’s Maps user-generated content policy says merchants may not “discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.” A technician who only triggers the request after jobs that went well is doing the same thing by hand.
The same policy bars merchants from offering incentives, “such as payment, discounts, free goods and/or services,” in exchange for a review. That rules out the gift card drawing and the discount on the next oil change, however well meant.
Federal rules apply too. According to the FTC’s questions and answers on its Consumer Reviews and Testimonials Rule, the rule took effect on October 21, 2024, and courts can impose civil penalties for knowing violations. It covers fake reviews, and incentives tied to an express or implied requirement to express a particular sentiment. The FTC’s answers don’t treat emailing all of your purchasers to ask for reviews as a problem in itself. On asking only customers you believe are happy, the rule has no specific prohibition, but the FTC says the practice could violate the FTC Act.
Google’s policy is stricter on incentives, so we’d follow it. We’re marketers, not lawyers, so specific questions belong with your attorney. In practice the setup stays simple: every customer gets the same request, nothing is offered in return, and the reviews say what they say.
Check it monthly, then start with one job
Automations break quietly. Someone renames a job status, a new hire checks customers out differently, and the requests stop without an error message. Three checks a month catch most of it:
- New reviews this month, not your total. The total only goes up.
- Requests sent against reviews received. If requests drop, look at the trigger. If requests hold and reviews fall, look at the message, the link or what’s said at the door.
- A test send to your own phone, to see what arrives, when, and with which link.
Automation makes asking consistent. It doesn’t make the service good, and if jobs run late and calls go unreturned, a reliable request will document that reliably. Nobody controls whether a given customer writes a review, what it says, or how Google weighs it. A realistic aim is a few new reviews in most months, building slowly.
This week, write down which event marks a job finished in your records and who enters it. It takes about fifteen minutes and costs nothing, and it tells you whether the trigger exists yet.
Tell us how you ask for reviews now and where it usually falls apart, and we’ll say what we’d set up and what your team would need to do. Your first consultation is free, and you can send us a message when you’re ready.