Quick Answer
Mark a job complete in ServiceM8, wait 24 hours, then send the customer a short personalised SMS and email with a direct link to your Google review page. Zapier handles the trigger, the delay, the message generation and the send. Set it up once, leave it running, watch your review count climb from the trades average of around 12 to the 50-plus that drives serious local search lift.
Table of Contents
- What the automated review pipeline actually does
- Why automated reviews move the needle for trades
- What you'll need before you start
- Step 1: Connect ServiceM8 to Zapier
- Step 2: Build the trigger and the 24-hour delay
- Step 3: Generate a personalised request with Zapier AI
- Step 4: Deliver via SMS and email with the review link
- Step 5: Monitor the inbox and auto-draft replies
- Google's review policy in plain English
- What tradespeople are saying
- Recommended videos
- Frequently asked questions
- My verdict
Zapier
ServiceM8
Google Business ProfileWhat the automated review pipeline actually does
The pipeline is four moving parts. ServiceM8 fires a Zapier webhook the moment you mark a job complete. Zapier waits 24 hours. Zapier AI writes a short message that names the customer and the work you did. Zapier sends it by SMS and email with a one-tap link straight to your Google review form.
That sequence does three things a manual ask never does. It catches the customer when the job has settled in their mind but the impression is still fresh. It speaks to them by name about the boiler, board or socket they actually paid for. And it goes out every single time without you having to remember.
I built a version of this for Elite Heating and Plumbing years before Zapier could do half of what it does now. The principle has not changed. If you ask every customer, in the right window, with the right specifics, more of them say yes. Automation just enforces the discipline.
Don't send the request the second the job ends. The customer is still wet, dusty or paying the bill. 24 hours later they have made the tea, looked at the work, and decided whether you delivered. That's the moment.
Why automated reviews move the needle for trades
Google's local pack, the three businesses that show up above the map, is largely a function of three things. Proximity, relevance and prominence. Reviews are the loudest signal you control in the prominence bucket. Volume matters. Recency matters even more. Around 73 percent of UK consumers say they only trust reviews from the last 30 days, which means a one-off push to get to 50 reviews and then stopping is worse than ten reviews drip-fed every month.
The economics back this up. A trades business with 50-plus reviews gets around 266 percent more enquiries than one sitting on a handful, and the average UK tradesperson has roughly 12 reviews on file. The gap between average and visible is small enough to close in a quarter if you ask every customer.
Most trades businesses already know reviews matter. The block is process, not belief. The engineer finishes at five, drives to the next job, forgets to ask. The owner promises to ask "tomorrow" and the week goes by. By Friday the customer has moved on and the moment is gone. An automated pipeline removes the gap between intention and action.
If you already use a job management system that knows when a job is complete, the build is straightforward. ServiceM8 is the cleanest fit because the "job completed" event is well-defined and the Zapier integration is mature. You can apply the same principles to Tradify, Jobber or other systems, but the steps below use ServiceM8 by name.
For broader context on review automation across other stacks, see our complete Google Reviews automation system guide. If you want to see how this fits inside a wider referral and growth engine, the n8n referral engine playbook covers the next step.
What you'll need before you start
The kit list is short. None of it requires a developer.
An active ServiceM8 account on any paid plan (the free 30-job tier is too restrictive for automation). A Zapier account. The Free plan handles two-step Zaps, but for this pipeline you'll want at least the Professional plan because we use a multi-step Zap with AI. A verified Google Business Profile that has been active for at least 60 days. Roughly 45 minutes to set everything up, plus 10 minutes a month for monitoring.
Budget is modest. ServiceM8 Starter is £25 a month for unlimited users and 50 jobs (the most common entry plan for sole traders), Growing is £59 for 150 jobs, and Premium is £119 for 500 jobs. Zapier's Professional plan starts at around £24 a month with 750 tasks, which is comfortably more than the average trades business will spend on review requests. Add SMS costs at five pence each via ServiceM8 and the whole pipeline lands at roughly £55 a month for a sole trader on Starter, or £85 a month for a small team on Growing.
| Component | What it does | Monthly cost |
|---|---|---|
| ServiceM8 Starter | Job management, complete event, SMS sending | £25 |
| Zapier Professional | Trigger, 24-hour delay, AI, multi-step Zap | £24 |
| Google Business Profile | Verified listing, review link, public reviews | Free |
| SMS overage | 5p per SMS above plan allowance | Variable |
Grab your Google review short link first. From your Google Business Profile dashboard, click "Get more reviews" and copy the short URL. It looks like g.page/r/AbCdEf123/review. You'll paste this into Zapier in Step 4. If you skip this and try to find it later, you'll end up sending customers to a generic Google search page that converts at less than half the rate.
Step 1: Connect ServiceM8 to Zapier
Open Zapier and click "Create Zap" in the top left. In the trigger panel, search for ServiceM8 and select it as the app. ServiceM8 has been on the Zapier marketplace since 2018, so the connector is stable. Choose "New Job Created" first if you want to test the connection, then come back and switch it to "Job Status Changed" with the filter set to "Complete" once you're confident things are talking to each other.
When Zapier asks to sign in to ServiceM8, click "Connect a new account". A popup will ask for your ServiceM8 login. Use the owner-level account, not a staff one. Staff accounts often don't have permission to fire webhooks. Authorise the connection, close the popup and wait for the green tick.
Run the test step. Zapier will pull in your last completed job as a sample record. You should see the customer's first name, last name, mobile number, email, and the job description. If any of those fields are blank, you've got a data quality problem at the source, and no amount of automation will fix it. Go back into ServiceM8, fix the missing fields, and run the test again.
If you later add more Zaps for invoicing, scheduling or reporting, give each its own ServiceM8 connection inside Zapier. Mixing them on one connection makes debugging a nightmare when one breaks.
Step 2: Build the trigger and the 24-hour delay
The trigger event is "Job Status Changed" in ServiceM8. Set the filter so the Zap only fires when status equals "Complete". That single filter saves you from sending review requests to customers whose jobs are still in quote, work order or unsuccessful states. Skip it and you will, sooner or later, ask a customer to review work you haven't actually done.
Add a Filter step after the trigger. Filter to only continue if the customer has an email address OR a mobile number. Sounds obvious, but customers without either are real, especially for emergency callouts logged at 11pm. The Zap should fail silently for those rather than throw an error.
Now add a Delay step. Choose "Delay For" and set it to 1 day, 0 hours, 0 minutes. Don't be clever with this. Some guides suggest sending immediately or after two hours. Don't. Field testing in trades businesses consistently shows the 24 hour window produces the highest response rate.
Zapier has a "Delay Until" option that fires at a specific time. It's tempting to set it to "tomorrow at 10am". Don't. If a job completes at 9:30am, the customer gets the message half an hour later, which defeats the point. Always use "Delay For" with a 1-day duration.
Step 3: Generate a personalised request with Zapier AI
Generic templates die in inboxes. "Hi {first_name}, thanks for your business" is the email equivalent of a doorbell ditch. The customer can smell the template at twenty paces and Google's own guidance increasingly punishes obvious copy-paste behaviour.
Add a Zapier AI action. Choose "Conversations" and select GPT-5 as the model. Zapier added GPT-5 to its action library in late 2025. If you're still on GPT-5 mini, that's fine for this use case and cheaper. In the prompt field, paste the following:
"Write a short, friendly SMS message (max 240 characters) and a separate short email (max 90 words) asking [Customer first name] to leave a Google review for [trade type] work I did for them. The job was: [job description]. Mention one specific thing about the work to show I remember the job. Sign off as [your first name] from [your business name]. Plain English, no exclamation marks, no marketing-speak. End the SMS with a placeholder GOOGLE_LINK that I will replace."
Map the bracketed fields to the ServiceM8 trigger data. The output is two short pieces of personalised copy that actually mention the job. The AI mentions the dripping radiator, the dead consumer unit, the loft conversion plumbing. That specificity is what lifts the response rate above the dismal industry baseline.
Run the test. Read the output as if you were the customer. If it sounds robotic, tweak the prompt by adding "Write like a tradesperson, not a marketing copywriter" or "Use British English and avoid the word genuine". You'll iterate the prompt three or four times before it sounds right. That's normal.
Never write "give us a 5-star review" or "leave us a great review" in the prompt or template. Google's policy explicitly bans review steering. Ask for a review. Period. The kind of reviews that come out of an honest ask are the ones that actually help you rank.
Step 4: Deliver via SMS and email with the review link
The delivery step has two branches. SMS is the heavy lifter. Open rates sit around 98 percent and response rates beat email by a wide margin. Email is the backup for older customers who still prefer it. Send both. Belt and braces.
For SMS, use a "Path" in Zapier (or just two parallel actions if you're on Professional). The first path sends the AI-generated SMS via ServiceM8's "Send SMS" action. In the message body, paste the AI output and replace the GOOGLE_LINK placeholder with your short review URL, the g.page/r/... link you grabbed at the start.
For email, add a "Send Email" action. Use Gmail, ServiceM8 email or any SMTP connection. Drop the AI-generated email body in and add the review link as a bold standalone line near the bottom. Don't make the customer hunt for the link. Don't put it in a button graphic that doesn't render in Outlook. Plain text with a clear hyperlink wins every time.
At 5p per SMS plus a fraction of a penny for the email and the AI call, each request costs about six pence. If your conversion rate sits at 20 percent, the realistic ceiling for cold review asks, that's 30p per review. Compare that to the cost of paid local search and the maths is obvious.
Step 5: Monitor the inbox and auto-draft replies
Asking is half the job. Replying is the half nobody automates. Google rewards businesses that respond to reviews, especially within 48 hours, and it punishes profiles that look abandoned. The good news is the second Zap is much shorter than the first.
Create a new Zap. The trigger is "Google My Business: New Review". Authorise Zapier to read your Google Business Profile. The first time, Google will ask for explicit permission to access reviews. Grant it. This is read-only and safe.
Add a Zapier AI action that drafts a reply tailored to the review content. Use this prompt:
"Draft a short reply (max 60 words) to this Google review. If the review is 4 or 5 stars, thank the customer by first name and mention the specific work in their review. If the review is 3 stars or below, acknowledge the issue without being defensive, apologise, and offer to talk on the phone. Sign off as [your first name]. Plain English, British spelling, no emojis, no marketing language."
The output goes into a Slack channel, an email to you, or directly back to Google as a draft via the Google Business Profile API. For the first month, route it to a draft and review each one yourself. After thirty replies you'll trust the AI enough to let it auto-publish four and five star responses. Always keep one and two star replies on manual approval. Those need a human voice.
An AI apology on a one-star review can sound tone-deaf to the customer who wrote it. The best one-star recovery is a phone call, not a public reply. Get the AI to draft, but keep your finger on the send button.
Google's review policy in plain English
Google's review policy was updated in April 2026 with stricter language on solicitation. The short version: ask everyone equally, never offer anything in return, and never write the review yourself or steer the customer toward a rating. Plenty of businesses get away with breaches for a while, but Google's automated detection has improved sharply and a wipe of fake reviews can take you back to zero overnight.
The pipeline above is compliant by design. The trigger asks every completed job, not just the happy ones. The prompt asks for a review, not a five-star review. No discount, no gift card, no incentive of any kind. If you stick to those three rules you're inside the lines.
| Practice | Compliant | Not compliant |
|---|---|---|
| Asking every customer | Yes | Asking only the happy ones (review gating) |
| Direct link to your Google form | Yes | Filtering customers to a private feedback form first |
| Personalised message | Yes | Suggesting wording or attaching a "sample" review |
| Discount for a review | n/a | Banned |
| Asking on-site under pressure | n/a | Banned and counterproductive |
Review gating is the most common breach in trades. The pattern goes: send the customer a feedback form, branch the unhappy ones to a private complaint email, branch the happy ones to Google. Sounds clever. It's banned. Google's detection looks for unnatural rating distributions and the penalty is loss of all reviews, not just the suspect ones.
What tradespeople are saying
Recommended videos
Use this automation to get more Google Reviews without being annoying
Kyle Ack
Automate Google Review Replies with ChatGPT + Zapier
George Evans
Start Here: How to Set Up & Trial ServiceM8
ServiceM8
The ServiceM8 Setup 90% of Tradies Never Do (Full Tutorial)
David List
3 Ways to Ask for Google Reviews Without Sounding Desperate
Super Small Business
5 Local SEO Tips For Small Businesses Getting Started
Ranking Academy
Frequently asked questions
About 45 minutes the first time, including grabbing the Google review link and testing the prompt. The second Zap for auto-drafting replies takes another 20 minutes. After that, you check in once a month for ten minutes and otherwise leave it alone.
Yes for this build. The Free plan caps you at two-step Zaps and doesn't include AI actions. Professional starts at around £24 a month and gives you the multi-step Zaps, the AI actions, and enough tasks per month for most trades businesses. If you're running fewer than 30 jobs a month, the trial period is enough to test the pipeline before committing.
The principle holds. Tradify has a Zapier connector with a "Job Completed" trigger, Jobber has the same, and Powered Now exposes webhooks you can hook into Zapier manually. The 24-hour delay, the AI personalisation and the dual SMS-plus-email send work identically. The setup steps differ slightly. The outcome doesn't.
Not when the message is personal, sent once, and 24 hours after a job they were happy with. The annoyance comes from generic blast messages and multiple follow-ups. The pipeline sends one well-crafted SMS, one email, and stops. If a customer doesn't act within seven days, leave them alone.
Trades businesses running this kind of automation typically see 15 to 25 percent of asks turn into reviews. For 40 completed jobs a month, that's six to ten reviews. Compounded over a year you go from the average of 12 reviews to 80-plus, which is the rough threshold where local search rankings start to lift noticeably.
You can. You shouldn't. Sending while the engineer is still in the customer's drive feels pressuring. Sending the morning after, when the customer has used the boiler, walked across the new floor or run the dishwasher on the new circuit, gets a much higher response rate.
For emergency residential work, yes, with the 24-hour delay. For commercial jobs where the customer is a facilities manager rather than the end user, swap the SMS for an email-only branch. Facilities staff respond better to email than SMS and the conversion rate stays in the same ballpark.
Zapier counts each action as one task. The pipeline above uses roughly five tasks per completed job. At 750 tasks a month on Professional, you're covered up to 150 jobs. If you're doing more than that, upgrade to Team or move the workflow to n8n or Make for unlimited self-hosted runs. The AI marketing workflows guide covers when to switch platforms.
My verdict
Review automation is one of the highest-leverage hours you'll spend this quarter. Forty-five minutes of setup. Six pence per ask. A pipeline that compounds your local search position month after month. Stick to the four rules: every job, 24-hour delay, personalised message, no incentives, and you'll move from the trades average of 12 reviews to the 50-plus that drives real lead growth inside a year. Set it up this week. Mate, it's not the kind of work you put off.
