Automate the review request after a job
Reviews come from asking, not from luck
Pull the review history of almost any small service business and you find the same shape. A cluster from the launch, a few from customers who were unusually happy or unusually angry, and long stretches of nothing. The work stayed good the whole time. The asking is what came and went.
The fix is not a campaign. It is a habit the business cannot forget, because the habit is the part humans drop first. The most reliable way to hold it is to attach the review request to an event that already happens every time a job ends, and let an automation carry it. The owner stops being the thing the whole system depends on remembering.
Timing is the whole game
A review request works or fails on when it lands. Ask an hour after the final walkthrough or the paid invoice, and the customer still remembers the name of the person who did the work, the problem you solved, and how it felt to be handled well. Ask a week later and you are competing with everything that happened since.
This is exactly the kind of timing people are bad at and machines are good at. Nobody finishes a hard job and thinks, now let me go send a polished review link. So the request slips to tomorrow, then to never. An automation that fires off a signal you already record, a job marked complete or an invoice marked paid, closes that gap without anyone having to remember.
The message itself should be short and specific, not a form letter. A good one names the actual job, thanks the person by name, and gives a single link that opens straight to the review box. Every extra step you make someone take, a login, a search, a choice between platforms, is a place they quietly give up. The automation removes those steps so the only thing left to do is type a sentence.
What the automation actually does
A version that holds up in the real world stays small:
- Watches for the signal that a job is done: a status change, a paid invoice, a closed ticket, whatever your system already tracks
- Waits a set delay, often an hour or the next morning, then sends a short message in your voice with a direct link to the one review platform you care about
- Asks each customer once, and never asks the same person twice, so nobody feels nagged
- Logs who was asked and who left a review, so you can see the rate instead of guessing at it
Keep a human where it counts
Two rules keep this honest. First, you never buy or fake a review, and you never route the ask around a platform's rules to filter for the good ones. That is the fast way to get an account pulled, and customers can smell it. The automation asks everyone the same way.
Second, give the unhappy customer a different door. A simple version asks how the job went before it points at a public review. Happy answers get the review link. Anything lukewarm gets routed to you, quietly, so you hear about the problem before the internet does. That is not hiding bad reviews, it is fixing the cause while you still can, and a customer you win back that way is worth more than the star rating ever was.
Why it is worth building
Reviews are the closest thing a small business has to compounding interest. They sit on the exact page a new customer reads before they call, and they keep working while you sleep. The businesses that win the search results are rarely the ones doing better work. They are the ones who asked, every time, on time.
This is a strong early automation because the stakes are low and the payoff is public. A wrong send costs you an awkward text, not a lost deal, so it is a safe place to build trust in letting a machine reach your customers at all. It fits a dealership closing sales all week or a contractor wrapping jobs, and it is the sort of quiet, event-driven task a managed retainer is built to run and watch. Build it once, and the asking never gets forgotten again.
The audit answers this for your business
Two weeks, $2,500 flat ($1,000 for the first three clients), and you get the map of your own automatable work with dollars on it.