How to automate review requests after every job (without breaking Google's rules)

It's ten past four on a Thursday. Three jobs done — a hot water swap, a switchboard tidy, a leaking mixer — and all three customers were happy with the work. You asked none of them for a review. You almost never do. Not because you don't rate them, but because the end of a job is you packing the ute, taking a call about tomorrow morning, and working out whether you'll beat the traffic home.

That's the whole problem, and it's why "remember to ask" has never once fixed it. So here's how to automate review requests instead: one goes out after every single job, in your words, whether you thought about it or not — and it does it without tripping over Google's rules, which most of the advice on this topic quietly does.

How do you automate review requests after every job?

Automating review requests means wiring one trigger — a job marked complete, or an invoice sent — to one message. The system texts that customer your Google review link the same day, sends a single reminder if nothing comes back, then stops. Every customer gets asked, not only the ones you expect to be happy.

There are only four moving parts, and once they're set you never touch them again:

1. A trigger — the moment the system knows the job is finished.
2. A wait — an hour or two, so the text doesn't land while you're still in their driveway.
3. A message — short, named, with a one-tap link.
4. A stop rule — one reminder, then it leaves them alone for good.

Getting the trigger right, even without job software

If you run ServiceM8, Tradify, simPRO, AroFlo or Jobber, the trigger already exists: the job status flipping to Complete, or the invoice going out. That status change is the signal every automation hangs off.

If your system is a notebook on the dash and a phone in your pocket, you still have a trigger — the invoice. You send one for every job you finish, which makes it the most reliable "job done" marker in your whole business. Fire the review text off the back of the invoice going out and you've got the same automation without buying anything new.

Two traps worth knowing before you pick. Job booked is far too early — you're asking someone to review work you haven't done. Invoice paid feels tidy but can sit unpaid for three weeks, by which time the customer has forgotten which tradie you were. Job finished, or invoice sent, is the window where they still remember your name and the taps still feel new.

Then add one rule that saves you grief: one request per job, and skip anyone you've already asked in the last few months. Regulars on a maintenance run don't want a review text every fortnight, and Google only keeps one review per customer anyway.

Don't filter who gets asked — that's against Google's rules

Nearly every review-automation guide tells you to build this the same way: send a private "how did we go, one to five?" message first, push the fours and fives to your Google link, and quietly route the ones and twos into an internal feedback form. It sounds sensible. It's called review gating, and it breaks Google's policy.

Google's own content policy is not subtle about it. Merchants must not:

Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.

The same policy bans offering "payment, discounts, free goods and/or services" for a review, so the $20-off-your-next-service trick is out too. What Google does allow is asking — every customer, the same way, without a sweetener. Getting caught gating can cost you the reviews you collected that way, and the ranking they were holding up.

There's a commercial reason to skip the filter, too. A profile of nothing but flawless fives reads like it was bought. A run of genuine reviews with the occasional four, and a calm owner's reply underneath the one that went sideways, is what actually convinces the person deciding between you and two other quotes. And if a customer is unhappy, you want to hear about it from them directly — ring them, sort it, and let the review land where it lands.

The message, the timing, and the one reminder

Send it as a text. A review-request email arrives underneath twelve other emails and dies there; a text gets read in the time it takes to walk to the kettle. Same day, an hour or two after you've packed up, while they're still pleased the hot water's back.

Keep it to three things — their name, the actual job, and the link:

Hi Sarah, thanks for having us out today — glad the hot water's sorted. If you've got 20 seconds, a quick Google review makes a big difference to a small local business: [your link] — Dave, Northside Plumbing

Grab that link from your Google Business Profile under "Ask for reviews" so it opens the star box straight away. No searching, no logging in, no hunting for your business among four others with a similar name.

Then set the guardrails, because an automation with no manners will cost you more than it earns. One reminder about three days later, softer and shorter, and after that the system never mentions it again. Nothing before 8am or after 7pm, and hold Sunday sends until Monday. Your business name in every message so nobody's staring at an unknown number. And if anyone replies "stop", it stops — permanently, no exceptions.

Making it run when you're on the tools

All of this is straightforward. It's also exactly the kind of thing that survives two good weeks and then dies the first time you're flat out, which is when you needed it most. The tradies quietly owning the map pack in their suburb didn't out-discipline you — they took themselves out of the loop entirely.

It's the same mechanic behind automating your quote follow-ups and chasing late invoices: pick the trigger once, write the message once, and let something else do the remembering. An AI team member can send the request after every completed job in your wording, watch for the replies, and draft your response to each review as it lands — including the awkward one. You can set that up for your own business in about five minutes, for a one-off price rather than another monthly subscription. If you want the wider picture first, start with the plain-English guide to AI for tradies, or the detail on getting more Google reviews as a tradie.

The reason your competitor has 180 reviews and you have nine usually isn't the work. It's that one of you turned asking into a system, and the other one is still relying on a memory that's already full of tomorrow's jobs.

Common questions

When should you send a review request after a job?

The same day, an hour or two after you finish. The customer is still pleased with the result and can picture exactly who you are. Leave it three days and the moment has passed. Send one reminder about three days later, then stop.

Is it OK to only ask happy customers for a review?

No. Google's content policy says merchants must not discourage negative reviews or selectively solicit positive ones, which is what filtering by sentiment does. Ask every customer the same way. If someone was unhappy, ring them about it rather than hiding the link.

Should review requests go by text or email?

Text, almost always. It gets opened within minutes, where a review-request email lands in a crowded inbox and stays there. Keep email as the fallback for the customers you only ever had an email address for.

Do I need job management software to automate review requests?

No. Any reliable "job finished" signal works, and for most sole traders that's the invoice going out. If you already run ServiceM8, Tradify or similar, use the job-complete status instead — it fires a bit earlier.