An automated review request system fires a text message to a customer roughly 90 minutes after their appointment is marked complete, with a direct link to leave a Google review. That one trigger, running after every job, is responsible for most of the review growth we see across service business builds. No manual reminder to the front desk, no end-of-day batch email, no hoping the tech remembered.
This post is part of the business automation guide for service companies and covers Pattern 6 of the Core 8 automation stack. If you are trying to understand the full picture of what a well-built automation layer looks like, that guide is the right starting point. Here we go deep on the review request piece specifically.
Why do manual review requests almost never work?
Manual review requests fail because they depend on a person remembering to do one extra thing at the end of a busy day, and that almost never happens consistently. The technician finishes the job and drives to the next one. The front desk fields three calls while closing out the ticket. By evening, the ask for a review is long forgotten.
Even when someone does remember, the timing is usually off. A request that arrives the morning after a service job gets a fraction of the engagement of one that arrives while the customer is still thinking about the work that was just done. The experience has to be fresh. That freshness window is real, and it closes quickly.
There is also a selection bias problem with manual outreach. When a person decides who to ask, they tend to reach out to customers they already have a relationship with, or ones they are confident were happy. That means the businesses that ask manually end up with a skewed sample. The automation treats every completed appointment the same way, which produces a truer picture of your business and a much higher total count.
of consumers regularly read reviews before choosing a local service business.
What triggers an automated review request?
The trigger is the appointment status being marked complete inside your CRM or scheduling tool. When a job is closed out, the automation checks the elapsed time, waits for the configured window, then sends the SMS. Nothing fires until that status changes, so you are never sending a request before the work is done.
In practice, when we wire up this sequence, the first thing we configure is the completion trigger rather than a time-based trigger. Time-based triggers (send at 5pm every day, for example) create a batch problem: a dozen requests go out at once, which looks unnatural and can trigger spam filters. Status-based triggers are individual and real-time. Each customer gets their message at the right moment relative to their own appointment, not based on a clock on the wall.
The trigger also carries context into the message. The automation can pull the customer's first name, the technician's name, and sometimes the specific service performed, so the request reads like a message from a person rather than a campaign blast.
What is the right timing window for the message?
The 60-to-90-minute window after appointment completion consistently outperforms every other option in the builds we have run. Send too soon and the customer may still be on-site wrapping up. Send the next morning and you have lost the emotional peak of the experience. The 90-minute mark hits when they are back home, settled, and the job is still on their mind.
We always time the SMS trigger to 90 minutes after appointment completion: early enough that the experience is fresh, late enough that the person has pulled out of the parking lot. That window outperforms next-day emails by a significant margin in our builds. The data from our own systems is consistent enough that we have stopped testing alternatives to it and just set it as the default configuration.
A 24-hour email serves as a fallback. If the SMS link was never clicked, an email the following afternoon gets a second shot. The message is shorter in the email and acknowledges that you reached out yesterday, which frames the follow-up naturally rather than making it feel like a second cold ask.
Should you use SMS or email for review requests?
SMS is the primary channel for review requests because open rates are materially higher and the link requires one tap on the same device the customer will use to leave the review. Email is worth including as a fallback, but it should not be the first message out the door.
The SMS message itself should be short: three sentences at most. Identify who you are, reference the appointment, and include the link. Long messages get ignored. The goal is to remove every step between the customer and the review form.
One thing we configure in almost every build: the review link goes directly to the "Write a review" screen on Google Business Profile rather than the general listing page. That single change removes one tap and one decision from the customer's path. When you make leaving a review slightly easier, more people complete it.
How do you stop unhappy customers from posting publicly?
A two-step message sequence routes feedback privately before it ever reaches Google. The first message asks a simple question about the experience, something like "How did today's visit go?" with an easy positive or negative reply option. Positive responses receive a follow-up with the Google review link. Negative responses go to a private feedback form or trigger an alert to your team so someone can reach out directly.
This is called sentiment routing, and it does not violate Google's review policies provided every customer receives the initial message regardless of what you expect their response to be. The key is that you are not filtering who gets asked, only routing the response path based on what they tell you. Blocking the link entirely from customers who express dissatisfaction would be problematic; giving unhappy customers a private channel to share feedback while happy customers go to Google is standard practice.
A pool service company we worked with had only 11 Google reviews despite having hundreds of active clients on their route. The front desk had been meaning to set up some kind of review system for over a year but never found the time to figure it out. Once the two-step automated sequence was running, they collected over 40 new verified reviews within 60 days. The owner noted that several of those came from long-term clients who had simply never been asked before. The reviews were there to earn, waiting on a system that never existed.
Which review platform should you send customers to?
Google Business Profile should be the default for nearly every service business. Google reviews feed directly into map pack ranking, appear in AI-generated search answers, and are what most customers look at before making a call. Spreading review volume across five platforms sounds comprehensive but usually means thin coverage everywhere.
Once you have a strong Google foundation, secondary platforms depend on your category. Yelp matters for salons, spas, and restaurants in metro markets. Houzz and Angi carry weight for contractors. Healthgrades or Zocdoc for medical and dental. The automation can be configured to route certain customers to a secondary platform based on a tag or segment, but start with Google and add channels once the baseline volume is established.
Reviews on Google also have a compounding benefit that most owners do not think about: they feed how Google and AI systems perceive your business's reputation, which affects both map pack visibility and whether your business gets cited in AI-generated answers to local queries. This is covered in more depth in the Google Business Profile and map pack checklist, but the short version is that consistent recent reviews are one of the clearest signals you can send.
Is it legal to automate review requests via text?
Yes, with proper consent in place. The path that keeps you compliant: collect prior express written consent at booking (your online scheduling form or intake paperwork covers this if the language is there), include a clear opt-out in every message (STOP to unsubscribe), and never offer any incentive in exchange for a review.
The incentive rule is the one that surprises business owners most often. Offering a discount for leaving a review violates both FTC guidelines and Google's own review policies, even if you frame it as a thank-you. The message should be a straightforward ask, nothing attached.
For deeper detail on SMS compliance requirements, the post-visit follow-up automation guide covers the consent and timing rules that apply to all customer-facing sequences, not just review requests. The rules that apply to review SMS are the same ones governing any automated outreach.
How does review automation connect to the rest of your systems?
Review volume is not a vanity metric in isolation. It is one of the clearest inputs into local search ranking and one of the fastest ways to build the social proof that converts a first-time visitor on your website into a caller.
Inside a full automation stack, the review request is Pattern 6. It fires after the appointment is complete, which means it sits downstream of confirmation (Pattern 3), reminders (Pattern 4), and the post-visit follow-up (Pattern 5). Each of those sequences set the customer up to have a good experience, which makes the review ask more likely to land well. A client who got a reminder and showed up on time, whose job was done without issue, is far more likely to leave a positive review than one who had friction at every step.
The reviews also feed back into your visibility. A steady stream of recent, verified reviews on Google Business Profile is one of the inputs that affects map pack position. Combined with the rest of the profile work covered in the map pack checklist, review automation is one of the highest-leverage operational changes a service business can make, because it produces a recurring output with no recurring effort.