Your Review Problem Isn't Effort. It's Timing.
Here's what review collection looks like at most Kentucky service businesses: you finish a job, you mean to ask for a review, you get pulled into the next thing, and three days later you remember while you're driving to a quote. Maybe you text them. Maybe you don't. Maybe you ask the customer who was pleasant and skip the one who grumbled about the invoice.
That's not a system. That's a hope.
And it's why your competitor down the road with worse work has forty more reviews than you do. They're not better at the job. They're better at asking at the exact moment the customer feels good about the job.
The fix isn't discipline. It's a trigger. Something happens — the job gets marked complete, the invoice gets paid, the tech closes the ticket — and a message goes out without anyone remembering to send it. That's it. That's the whole idea. The rest of this post is how to build it.
Why Reviews Actually Move Revenue for Local Service Businesses
Quick grounding, because you should know what you're building toward.
Google's local pack — the three-business map result that shows up when someone searches "HVAC repair near me" — weighs review quantity, review recency, and review ratings as ranking factors. Google says so in its own documentation on local ranking. Prominence, relevance, distance. Reviews feed prominence.
But ranking is only half of it. The other half is the click. Two plumbers show up in the map pack. One has 18 reviews from 2022. One has 240 with a handful from last week. The number of people who call the stale one is very close to zero.
For a service business where a single job might be worth hundreds or thousands of dollars, the math on review volume isn't subtle. You're not optimizing a vanity metric. You're optimizing whether the phone rings.
The Trigger: When to Fire the Request
This is the part people get wrong, so let's be precise.
The request should fire when the customer's satisfaction is highest — which is almost never when the work ends.
Think about the actual emotional arc of a service job:
- During the job: customer is stressed, there's disruption, there's a bill coming.
- Immediately after: relief, but also fatigue, and they want you out of their house.
- A few hours later: the AC is cold. The sink drains. The room looks good. Now they're happy.
- A week later: it's normal. They've forgotten the before.
Your window is roughly 2 to 24 hours after job completion, and the right spot inside that window depends on your trade.
Trigger timing by job type
Same-day residential service (HVAC, plumbing, electrical, appliance repair):
Fire 2–4 hours after the job is marked complete. The customer has had time to use the thing you fixed. Don't wait overnight — by tomorrow they're back in their own life.
Multi-day projects (remodels, roofing, landscaping installs):
Fire 24–48 hours after final walkthrough. There's cleanup settling, there's the "wow" of seeing the finished space without workers in it. Immediately after walkthrough, they're still in punch-list mode and thinking about what's wrong.
Appointment-based services (salons, med spas, dental, chiropractic):
Fire 1–2 hours after checkout. The haircut still looks fresh. Same-day is non-negotiable here.
Recurring services (lawn care, cleaning, pest control):
Don't fire on every visit — you'll train people to ignore you. Fire after the third completed service, then not again for six months. Loyalty is the signal, not a single visit.
Anything invoiced net-30:
Fire on payment, not on completion. Asking for a review while an unpaid invoice is sitting in their inbox is a bad look and a bad conversion rate.
What the trigger connects to
The trigger has to come from a system that already exists in your workflow, or it won't last. Options, roughly in order of reliability:
If none of those exist in your business, that's the actual first project — not the review system. You need a defined "done" event before you can automate off of it.
SMS or Email? Stop Guessing.
Short answer: SMS for the ask, email for the follow-up.
Longer answer, because the reasoning matters.
Text messages get opened. Almost immediately, almost always. For a one-tap action — click link, leave review — that immediacy is everything. The customer is on their phone, the Google review form opens in their browser, they're logged into their Google account already, and the whole thing takes 40 seconds.
Email is slower, more likely to sit, and more likely to get filtered. But it's better for anything that needs explanation, and it's better if your customer base skews older or if you're in B2B where people live in their inbox.
The practical rule
- Residential consumer services → SMS first. Follow up by email in 3 days if no review.
- B2B or commercial accounts → email first. The person who hired you may not be the person who answers the cell number on file.
- Never send both at the same time. It reads as desperate and it doubles your unsubscribe rate.
Compliance, briefly, because it's real
You need consent to text customers. Get it on the intake form, on the service agreement, or on the booking page — a simple checkbox with clear language that they may receive service-related text messages. Include opt-out language in your messages. "Reply STOP to opt out" belongs in your first message to any customer.
This is not optional and it's not hard. Build it into intake once and never think about it again.
The Messages
Keep them short. Every extra sentence costs you completions.
The SMS ask
>Hi [First Name] — [Tech Name] here from [Business]. Thanks for letting us take care of your [service] today. If we did right by you, a quick Google review helps other [City] folks find us: [link]
Reply STOP to opt out.
Why this works:
- It's from a person, not a brand. Use the tech's actual name. Customers remember the human who was in their house.
- It names the specific service. "Your water heater install" beats "your recent service."
- It gives a reason that isn't about you. "Helps other London folks find us" is a small favor. "Help us grow our business" is a chore.
- One link. No menu. No star rating widget. Every decision point is a dropoff point.
The email follow-up (3 days later, only if no review)
Subject: Quick favor, [First Name]?
>[First Name],
>We finished up your [service] on [day] and wanted to check in — everything still working the way it should?
>If so, would you mind leaving us a quick Google review? It takes about a minute and it genuinely helps us reach more people around [City].
>[Button: Leave a Google Review]
>And if something isn't right, just reply to this email and I'll handle it personally.
— [Owner Name], [Business]
Two asks in one message: review if happy, reply if not. That second line does a lot of work.
Stop after two
Two touches. That's the limit. A third request annoys people who already decided not to, and annoyed customers are the ones who leave the one-star reviews you were trying to avoid in the first place.
The Private Feedback Path (This Is the Part Most People Skip)
Here's the uncomfortable truth about automated review requests: you're going to send one to someone who's unhappy. Your automation doesn't know the tech was late or the price went over estimate.
You need a route that catches those people before they route themselves to Google.
How to build it correctly
Send the SMS to a short landing page — on your own domain — that asks one question: "How did we do?" with two paths.
- Positive path → immediately redirects to your Google review link
- Negative path → opens a short private form that goes straight to the owner's phone and email
That's it. One question, two doors.
The line you cannot cross
This is where businesses get themselves in trouble, so read carefully.
You cannot filter who gets asked for a review based on how they rate you. Google's policies prohibit review gating — selectively soliciting positive reviews while suppressing negative ones. Violating it can get your reviews removed or your profile penalized.
The legitimate version of this works differently: every customer gets the same request, with the same access to the Google link. Your feedback page offers a private channel as an additional option, not as a wall. The unhappy customer can still find your Google listing in four seconds — you're not stopping them. You're giving them a faster, more satisfying alternative: a real person who will actually fix the problem.
Most people who are mildly annoyed would rather be heard than be public. Give them that option and a good number take it. The ones who don't were going to post anyway, and now at least you got the heads up.
Then actually respond
A private complaint that disappears into a form inbox is worse than no form at all. Route negative feedback to a phone, not a shared email. Call within a few hours. Fix it if it's fixable.
A fair number of customers who get a real phone call from the owner after a bad experience will end up leaving a positive review on their own — not because you asked, but because the recovery impressed them more than the original job would have.
Building It: The Stack
You don't need enterprise software. You need four pieces that talk to each other.
A reasonable build order
Step 8 is the one people skip. Your first timing guess will be close but not right. Look at when reviews actually come in versus when you sent the request, and move the window.
What to Track
Three numbers. Don't overcomplicate it.
- Request-to-review rate — reviews received ÷ requests sent. This is your conversion number and it's the one you optimize.
- Reviews per month — the absolute number, because volume and recency both matter to Google
- Private feedback volume — how many unhappy customers you caught before they went public
If request-to-review rate is low, your timing or your message is off. If private feedback volume is zero, your path is probably buried and you should make it more visible.
The Real Point
A review system isn't a marketing tactic you bolt on. It's an asset that compounds. Every month it runs, your local ranking gets a little stronger and your Google listing gets a little more convincing to the next person who searches.
The business that asks every single customer, automatically, at the right moment, will out-review the business that asks when it remembers. Not because they work harder. Because they built it once and stopped thinking about it.
Build it once. Let it run.
If you're a service business in London, Corbin, Somerset, Richmond, or Lexington and you'd rather have this built than build it, that's what we do. Our AI automation work is exactly this kind of thing — connecting the systems you already use so the right message goes out at the right time without anyone remembering to send it. Book a strategy call and we'll map out what your trigger points are and what it'd take to wire them up.
Founder & Director of Photography, Envision Media Co. · London, KY
Cody has run camera on 300+ shoots for 50+ businesses across southeastern Kentucky since 2022, from Somerset marinas to Corbin contractors to Lexington retail. He still shoots most jobs himself, which is where the specifics in these posts come from. More about Cody.
Ready to Grow?
Let's Build Something Together
Want results like the ones we write about? Book a free strategy call and let's make it happen.
