This post may contain affiliate links. If you buy through one, we may earn a commission at no extra cost to you. See our Affiliate Disclosure for details.
The job went well. The client said so twice, once at the door and once in a text with three exclamation marks. You meant to ask for a review that evening. Then a quote needed writing, then a supplier called, and by Thursday the moment had passed and asking felt strange. Most small businesses don't have a review problem. They have a remembering problem, and that is the part software is genuinely good at.
Pick the channel your customers already use to talk to you, then automate only the timing and the reminder. SMS suits service work where the job ends in person and the customer’s phone is the relationship; email suits online sales, longer projects and anyone who never gave you a mobile number. Two rules matter more than either channel: ask every customer, not just the happy ones, and never tie a reward to a positive review. Google’s policies and the FTC’s 2024 rule on fake reviews both cover this, and automation makes breaking them easy to do at scale.
The ask is easy. The timing is the whole job.
A review request has one moving part worth automating: when it goes out. The wording can be written once. The link never changes. What slips is the send.
Consider what "the right moment" means for different kinds of work. A plumber's customer is happiest an hour after the leak stops. A web designer's client is happiest the day the site launches, not the day the final invoice clears. Someone who bought a candle online can only judge it after it arrives, which may be a week after they paid.
So the trigger matters more than the tool. The useful question is: which event in your existing systems marks the moment the customer knows the job went well? A job marked complete in a scheduling app. An order marked delivered. A project moved to "done". Whatever that event is, it becomes the starting gun, and a short delay after it — a couple of hours, a day, a few days for shipped goods — is usually the only thing left to decide.
One reminder is reasonable. A second reminder starts to feel like a collections notice, and a review earned by pestering reads that way too.
Email vs. SMS, side by side
| SMS | ||
|---|---|---|
| Best fit | Online orders, projects, clients you already email | On-site services, appointments, local trades |
| What you need first | An email address you're allowed to use | A mobile number and documented consent to text it |
| Setup effort | Low if you already run an email tool | Higher: a texting platform, and in the US usually carrier registration |
| Where it goes wrong | Lands in promotions or spam, gets ignored | Feels intrusive if unexpected; consent mistakes carry legal risk |
| Room for a personal note | Plenty | One or two sentences |
Neither column wins outright. The deciding row is the first one.
SMS has a reputation for getting read, and for in-person service work it tends to match how the relationship already runs — the customer texted you to book, texted when you arrived, and a text afterward fits the pattern. The cost is the setup. In the US, texting customers from a business number generally requires their prior consent, and most business texting platforms require carrier registration (often called A2P 10DLC) before messages are delivered reliably. That paperwork is manageable, but it's not a same-afternoon job, and the rules differ by country.
Email is the lower-friction option for anyone already sending order confirmations or project updates. If you run a tool like GetResponse or HubSpot, a review request is just one more automated message tied to an event — the same mechanics behind a welcome email sequence that runs itself, pointed at the end of the relationship instead of the start. As of September 2026, this post quotes no prices; check the official GetResponse pricing and HubSpot pricing pages on the day you decide, and confirm which plan tier includes event-triggered automation, since that's the feature this setup depends on.
If the whole relationship ran through a phone, the review request probably should too. Photo by Helena Lopes via Pexels.
Two rules that decide what you're allowed to automate
Here is where automation earns a warning label.
A common feature in review software goes like this: send a short survey first, route happy customers to your public review page, and route unhappy ones to a private feedback form. It's often called review gating. It looks clever. Google's policy on fake engagement says businesses shouldn't discourage negative reviews or selectively solicit positive ones, which is precisely what that routing does.
The second rule is about rewards. Google's same policy prohibits offering money, products or services in exchange for reviews. In the US, the FTC went further in August 2024 with a final rule banning fake reviews and testimonials, which, among other things, targets incentives conditioned on a review expressing a particular sentiment and the suppression of negative reviews through threats or intimidation.
What this means in practice is simple, if slightly uncomfortable. The automation should send the same request to everyone who completed a job or received an order. You can still ask unhappy customers what went wrong — just not in a way that decides whether they're allowed to see the public review link.
Treat this section as orientation, not legal advice. If you're running promotions around reviews or operate outside the US, read the primary sources yourself.
Where each channel quietly goes wrong
Email fails silently. A request lands in a promotions tab, nobody opens it, and the only symptom is that reviews simply don't arrive. Because the system reports "sent", it looks healthy. This is the same failure pattern as any other automation that breaks without anyone noticing, and the fix is the same: check the outcome, not the activity. Once a month, count new reviews against completed jobs.
SMS fails loudly, which is almost better. A customer who didn't expect a text will tell you. The risk is that "telling you" sometimes means a complaint rather than a reply, which is why consent collection belongs at booking, not at the review stage.
Both fail the same way when the link is wrong. Get it straight from the source: Google explains how to share a link to your Business Profile that asks for reviews, and that link — not a search results page, not your homepage — is what every automated message should carry. One tap should land the customer on the review box. Every extra tap loses people.
Write the request once, by hand, before any tool sends it for you. Photo via Pexels.
What a good request actually says
Short. Specific to the job. One link.
A workable email version reads something like: "Thanks again for having us fix the kitchen tap on Tuesday. If you have a minute, a short review helps other people nearby find us: [link]. Either way, thank you." The SMS version is the first and last sentence with the link between them.
The phrase "either way" does real work. It tells the customer that an honest review, including a critical one, is welcome — which keeps you on the right side of the rules above and, frankly, reads as more confident than asking for five stars. Replies to reviews matter too; answering them is a small support habit, the same muscle as deciding what a chatbot or autoresponder should handle versus what needs you personally.
Send one request by hand tomorrow
Before connecting anything, do this: open your Google Business Profile, copy the review link, and send it personally to the last three customers whose jobs went well — by whichever channel they last used to contact you. Note which channel gets a response.
That small test answers the email-or-SMS question for your specific customers better than any comparison table, including the one above. It also gives you the wording you'll later hand to automation, already proven on real people. Once you know which channel works, set a single trigger tied to job completion or delivery, one reminder at most, and the same request for everyone.
저는 한국에서 직원 없이 혼자서 두 개의 소규모 사업체를 운영하고 있습니다. 견적, 회계, 마케팅, 웹사이트 관리까지 모두 제가 직접 하고 있습니다. 개발자는 아니지만, 이 사이트의 자동화 시스템은 AI 코딩 도우미를 활용하여 밤늦게까지 오랜 시간 공들여 구축했고, 모든 콘텐츠 관리 및 게시도 제가 직접 담당하고 있습니다.