The Review Request Problem Is a Timing Problem
Most small businesses that want more Google reviews are asking in the wrong moment. They ask while still on the job site, before the client has seen the finished result. They ask in the invoice email, which the client reads in a frustrated state because they are about to pay money. They ask three weeks later when the client has moved on mentally and cannot remember enough specifics to write a useful review.
The research on review request timing is consistent: the optimal window is 12 to 24 hours after job completion, when the client has experienced the finished result but the experience is still fresh. That window is specific enough that manual requests almost never land in it consistently. Automation does.
How the Workflow Is Triggered
The trigger is whatever event in your workflow marks a job as done. This varies by business but common options include a status change in your CRM when a job moves to “Completed,” a payment received webhook from Stripe or PayPal, a form submission from your field team at the end of each job, or a row update in a Google Sheet where you track project status.
When that trigger fires in Make.com, the scenario waits for the delay you configure. Set it to 18 hours for most service types. Then it sends a message to the client via SMS, email, or both. The message includes your Google review direct link, which you get from your Google Business Profile dashboard under “Get more reviews.” One tap from the message. No searching. No navigating to find your business. Straight to the review form.
What the Message Should Say
Short is better. The message that converts is not the one that explains why reviews matter or lists all the benefits of leaving one. It is the one that feels personal, arrives at the right moment, and makes the action as easy as one click.
The structure that works: address the client by name, thank them for the specific job (not just “for your business”), say that a Google review helps your business grow, and give the direct link. Four sentences maximum. Send it from a phone number or email address that a real person monitors so that if they have a question or a problem, they can reply to the same message.
SMS converts at a higher rate than email for review requests. Most benchmarks show SMS review request conversion rates running two to three times higher than email for the same message at the same timing. If you have client phone numbers and have obtained permission to text, build the SMS version first. The email version is the fallback for clients whose phone numbers you do not have. Both can run in the same Make.com scenario with a conditional step that checks which contact information is available.
What This Does for Your Search Ranking Over Time
Google uses both the total number of reviews and the recency of reviews as signals in local search ranking. A business that receives a consistent flow of new reviews ranks above competitors whose review count is higher but whose most recent reviews are months old. That recency advantage is one of the clearest benefits of automating the ask after every completed job rather than running occasional review request campaigns.
The compounding effect of consistent review requests is also worth understanding. A service business completing 80 jobs per month with a 10 percent review conversion rate from an automated request generates roughly eight new reviews per month. Over six months that is nearly 50 reviews. Over a year it is close to 100. That profile, with both volume and recency, puts you in a substantially different position in local search than a competitor who asks occasionally and manually.
The full picture of how this fits into your client follow-up workflow after a completed job is covered in the client follow-up automation guide. The review request is one step in a broader post-job sequence that can also handle referral asks and repeat purchase prompts.
The Setup Time and Ongoing Cost
The initial build for a single-trigger, single-channel review request scenario in Make.com takes one to two hours for someone familiar with the platform and three to four hours for a first-time builder. The scenario runs on Make.com’s Core plan at $10.59 per month, which is enough operations capacity for a business completing up to a few hundred jobs per month. Beyond that, the Pro plan at $18.82 per month covers most growing service businesses comfortably. For a breakdown of how Make.com’s operation costs scale as you add more automations, the Make.com credits guide explains what to expect.
