Reputation · July 31, 2026 · by admin
You automate review requests without annoying customers by asking once, right after the job, through text (not email as the default), and by asking every customer equally rather than filtering out anyone you suspect might leave a bad review. That last part isn't just good manners; selectively soliciting positive reviews while steering unhappy customers elsewhere, known as review gating, is explicitly against Google's review policies.
Most small service businesses either ask inconsistently (a good tech remembers, a busy one doesn't) or don't ask at all. Both leave reviews on the table. The fix is a simple, automatic trigger tied to job completion, not a person remembering to do it on a Friday afternoon.
This post covers the timing, channel, and message mechanics that get real review volume without turning into spam.
The gap between businesses that ask and businesses that don't is bigger than most owners assume. In BrightLocal's 2026 Local Consumer Review Survey, 78% of consumers say they were asked to leave a review for a business in the past 12 months, and 83% of those who were asked went on to leave one, per BrightLocal's research. The same survey found 28% of consumers say they will "always" leave a review if asked, up sharply from 16% a year earlier. Customers aren't reluctant. They're just rarely asked at the right moment.
If you can only automate one channel, make it SMS. Text review requests get opened 95% to 98% of the time, compared to 20% to 35% for email, and SMS click-through on the review link itself runs 25% to 40% versus 5% to 12% for email, according to Kenect's research on text messaging engagement. Timing matters too: a request sent within two hours of finishing the job sees response rates 3 to 4 times higher than one sent the next day, per the same source.
Email still has a place, particularly for customers who don't text or for a second, gentler nudge a few days out. But if you're building the automation from scratch, text-on-completion should be the default trigger.
Generic requests ("Please review us!") convert at 8% to 12%. Requests that mention the specific technician, service performed, or the customer's name convert at 15% to 22%, roughly double, according to industry data compiled by WiserReview. Automation doesn't mean generic. A message template that pulls in the tech's first name and the job type ("Thanks for having Mike out to fix your AC today...") takes the same one-time setup as a blank template but performs meaningfully better.
This is the part most businesses get wrong without realizing it. Google's user-generated content policy prohibits discouraging or prohibiting negative reviews and selectively soliciting positive reviews from customers, according to Google's own contribution policy. In plain terms: you can't send review links only to customers you think will say something nice, and you can't run a "feedback filter" that quietly routes unhappy customers to a private form while sending happy ones to Google.
This practice, known as review gating, isn't just a Google Business Profile risk. It also runs into the FTC's 2024 rule against fake or manipulated reviews, which carries civil penalties, according to reporting summarized by SEOlogist. The safe, compliant approach is simple: ask every customer who completes a job, the same way, every time. If someone had a bad experience, you'll find out from the review, and you can respond to it professionally instead of trying to prevent it from existing.
| Step | What to automate | Why it matters |
|---|---|---|
| Trigger | Job marked complete in your scheduling/invoicing tool | Removes reliance on a tech or office staff remembering |
| Channel | SMS first, email as backup or second touch | SMS gets opened and clicked far more often |
| Timing | Within 1 to 2 hours of job completion | Response rates drop sharply after the first day |
| Message | Personalized with tech name and service type | Roughly doubles conversion vs generic text |
| Audience | Every completed job, no filtering | Required by Google's policy; also builds trust |
| Follow-up | One gentle reminder after 3 to 5 days, then stop | Avoids spam without giving up on slow responders |
The instinct to send three or four reminders usually backfires. One well-timed, personalized text right after the job, followed by a single gentle nudge a few days later if there's no response, covers the vast majority of realistic conversions. Beyond that, you're mostly annoying customers who already decided not to respond, and repeated review-nagging is a common complaint in negative reviews, which is a strange way to end up hurting your own rating.
FieldRobin automates this specific workflow: review requests fire automatically when a job is marked complete, with a message personalized to the tech and job type, sent by text. You set it up once per job type and it runs the same way for every customer, which is also what keeps it compliant with Google's rules against selective asking.
As soon as possible, ideally within one to two hours of the job wrapping up while the experience is still fresh. Response rates drop noticeably by the next day and keep dropping the longer you wait.
No. Asking customers for reviews is fine and encouraged by Google. What's against the rules is asking selectively, only requesting reviews from customers you expect to leave a positive one, or discouraging negative reviews.
No. Incentivizing reviews, offering a discount, gift card, or other reward in exchange for a review, violates Google's policies and the FTC's rules against manipulated reviews, regardless of whether the incentive is tied to a positive rating.
One follow-up is usually enough, sent three to five days after the first request. More than two total touches tends to produce diminishing returns and a higher chance of annoying the customer.
We use AI to assist with research, outlining, and drafting. Every article is reviewed, edited, and fact-checked before publication. When appropriate, we verify information against primary sources and update articles as new information becomes available.