A plumber finishes a boiler swap, wipes his hands, and drives to the next job. The customer is thrilled and would happily say so, yet no review request ever reaches her phone, so the five-star review that could have won next week's work is never written.
That gap is where a review request workflow earns its keep. It is a small habit that quietly compounds: every happy customer nudged, at the right moment, on the channel they actually read. Most UK businesses skip it. The ones who automate it climb the Google Map Pack while their rivals wonder how. The full system lives inside the wider DigiSurf CRM playbook, but the review step alone pays off fastest.
The 30-minute version
You can build the first version of this in one sitting. Order matters, so resist jumping ahead thinking you already know the timing. Most owners guess it wrong.
- Block 30 minutes and put your phone on silent.
- Pick the trigger: job marked complete, invoice paid, or 24 hours after the visit.
- Write two short messages, one text and one email, each asking for the review with the Google link dropped straight in.
- Send by SMS first, fall back to email for anyone who has not replied after three days.
- Set a monthly reminder to read what came back and reply to every review, good or bad.
Get the SMS timing right and reply rates jump. Send at 9pm on a Sunday and they sink.
The mistakes that cost the most
Three patterns turn a good idea into wasted effort.
- Sending once, then forgetting. A workflow that fires for a fortnight and then quietly breaks is worse than never starting. Check it monthly, the same way you would any other CRM automation you lean on.
- Asking at the wrong moment. A request landing before the job feels finished reads as pushy. Tie it to completion or payment, not a fixed day.
- Treating it as a bolt-on. The review step works best beside the rest of your follow-up, the same engine that can chase unpaid invoices without a chaser or deliver a guide the second someone opts in. Run them together and each one lifts the others.
Let the software do the asking
Doing this by hand works for a week, then one busy Friday kills it. The point of automation is that it never forgets. Built inside GoHighLevel automation set up for the UK, the review request fires the moment a job is marked done, waits for your chosen delay, and follows up if the customer goes quiet, all without you touching your phone.
That is exactly what we wire into our CRM software for clients. If you would rather we simply switched it on for you, the pricing sits on one honest page with nothing hidden.
What the numbers say
This is one of those jobs where small, well-timed changes beat big ones, because most competitors never send a single review request. Follow the same mobile-first best practices that lift any customer message, get the SMS timing and wording right, and the marginal win is large in the 95% of UK markets where nobody else bothers.
VWO Mobile UX Best Practices shows how much phone-first design shapes whether a message gets read and acted on, and the HMRC Capital Allowances Manual confirms the UK context for treating this kind of software as a business tool. Skim both for the raw detail.
Related cluster posts
From the same pillar, these dig into the neighbouring pieces of the follow-up puzzle:
