How to Automate Review Requests for Contractors and Stack Up 5-Star Reviews on Autopilot

You finished 40 jobs last month. How many turned into Google reviews? For most contractors, the honest answer is two or three — and half of those came from customers who happened to be extra nice. Meanwhile the shop across town has 380 reviews and sits above you on the map every time someone searches “AC repair near me.” That gap isn’t about the quality of your work. It’s about who has a system for asking and who’s still relying on memory.

Here’s the fix: a trigger that fires a review request the moment a job closes, so you never have to remember again.

Why asking for reviews manually always breaks down

Every contractor knows they should ask for reviews. The problem is where the asking has to happen — in the field, at the end of a long job, by a tired tech already thinking about the next call.

Three things kill it:

• Crews forget. Your tech just spent four hours in a 110-degree attic. “Would you mind leaving us a Google review?” is the last thing on their mind. Even good techs remember maybe one job in five.
• The timing is wrong. When someone does remember, it’s often days later — a text from the owner at 8pm on a Sunday. By then the customer’s warm feeling has cooled and the moment is gone.
• You’re too busy to chase it. You’re quoting the next job, making payroll, putting out fires. Manually tracking who got a request and who didn’t is a spreadsheet nobody keeps up.

The result is lumpy, random review flow. Three reviews one month, zero the next. Google’s local algorithm rewards steady, recent reviews — so lumpy hurts you twice.

The trigger moment that actually matters

The single most important decision in this build is when the request fires. Get this right and everything else is downstream.

The best trigger is the moment the invoice is marked paid — or a completion status your techs only set after the customer signs off. Not the next morning. Not “sometime that week.” Right then.

Why paid, specifically? Because that status change is the closest signal you have to “the customer is satisfied and the work is fresh in their mind.” Someone who just paid without complaint is, statistically, a happy customer. That’s your window.

Aim for the text to land 60 to 90 minutes after the paid event — not the exact second. If the invoice clears at 2pm, a request at 3:30 feels human. A request that arrives while the tech is still loading the van feels robotic and annoys people. A short delay is the sweet spot.

One more rule: text, not email. SMS gets opened and read within minutes; review-request emails sit unread behind a spam filter. Use email only as a backup when you don’t have a mobile number on file.

Building the automation, step by step

Here’s the actual flow. The pieces are the same whether your field software is ServiceTitan, Jobber, Housecall Pro, or a plain CRM.

1. Pick the trigger event in your field software. Find the exact status you want to fire on. In Jobber it’s an invoice marked “Paid.” In Housecall Pro it’s a job marked “Finished” (or the payment event). In ServiceTitan it’s a completed/paid job. This status change kicks everything off.

2. Connect that event to an automation layer. Most field software won’t send a smart, delayed, personalized text on its own. Bridge it to n8n, Make, or Zapier that listens for the paid event. Jobber and Housecall Pro fire native Zapier triggers; ServiceTitan and anything without a clean connector push out via webhook. If you’re on webhooks, test with a real closed job first — sandbox events often carry different field names than live ones, and that mismatch is the number-one reason a flow “works” in testing and sends blank texts in production.

3. Add a delay and a business-hours filter. Insert a 90-minute delay, then a filter: only send between 8am and 7pm local time. A completion at 9pm holds until 8am the next morning. Nobody wants a review request at 10:30 at night.

4. Personalize the message with real job data. Pull the customer’s first name and the service type from the field software into the text. Generic asks get ignored:

Hi Maria — thanks for trusting us with your water heater install today. If we earned it, a quick Google review would mean a ton to our small crew: [direct link]. — Dave, Rivera Plumbing

That takes 15 seconds to set up once and lands completely differently than “Please review us.”

5. Use a direct review link — not your homepage. This is where most contractors lose half their reviews. Don’t send people to your website or profile and make them hunt for the review button. In Google Business Profile, open the desktop dashboard, click Ask for reviews, and copy the short link Google generates (g.page/r/...) — it opens the star box directly. Paste that exact URL into every text. Every extra tap loses people.

6. Log the send. Write each send back to a Google Sheet or the CRM: customer, date, service, whether they responded. This is how you prove the system works and spot the month a broken link quietly tanks your numbers.

If you already run automated appointment reminders, this uses the same plumbing — you’re just firing on a different trigger at the other end of the job.

The follow-up nudge and the unhappy-customer escape hatch

Two additions separate a decent setup from one that actually stacks reviews.

The follow-up nudge. Most people who would leave a review just get busy and forget the first text. Add a second message 3 days later — but only to people who haven’t responded. A softer touch:

Hi Maria, no worries if you’re swamped — if you’ve got 30 seconds, we’d be grateful for a quick review: [link]. Either way, thanks again!

Gating on “no response yet” is the hard part: unless you’re using a review platform that detects the new review, you can’t reliably tell who left one. Two workarounds that actually hold up — (a) route everyone through a “rate us 1-5” step first (below) and only nudge the ones who never tapped, or (b) send the nudge to anyone who didn’t click the review link, tracked with a shortened URL. Cap it at one nudge. A third message crosses into nagging and gets you blocked.

The unhappy-customer escape hatch. This is the part most “get more Google reviews” guides skip, and it’s the most important for protecting your rating.

Instead of blasting a naked Google link to everyone, send a one-question message first:

Quick one, Maria — how did we do today, 1 to 5?

• 4 or 5: the automation immediately replies with the Google review link. Happy customer, public review.
• 1 to 3: the automation routes them to a private feedback form and pings you by text or email.

Now the frustrated customer vents to you privately — where you can fix it — instead of on your public profile. You catch problems before they become one-star reviews and funnel the genuinely happy people toward Google.

One caution: don’t over-engineer the gate into something Google would call review-gating. You’re allowed to ask everyone for feedback and share your review link — what you can’t do is suppress negative reviews or condition the link on a positive rating in a way that discourages honest ones. The safe framing: everyone gets a path to leave feedback; you’re just deciding which door opens first, and unhappy customers can still find your profile on their own.

What breaks in the real world

A few things sink these builds:

• Wrong phone numbers. A landline or a typo in the mobile field means the text silently fails and you never know. Add a check: if the number isn’t a valid mobile, fall back to email and flag it in your log.
• Firing before the customer is happy. If your crew marks jobs “complete” before the final walkthrough, you’ll text people mid-frustration. Fire on paid, or on a status techs only set after sign-off.
• Double-texting on multi-visit jobs. A three-day install shouldn’t trigger three requests. Add a rule: one review request per customer per 90 days. Key it off phone number or email, not job ID.
• Sending from an unknown number. Use a consistent business texting number and sign every message with your name and company. Strange numbers get ignored or reported as spam — and carrier spam flags follow that number around.
• Buying or incentivizing reviews. Never offer a discount for a review. It violates Google’s policy and can get your reviews stripped. You’re asking, not paying.
• Set-and-forget-forever. Check the log monthly. Google occasionally changes review-link formats and field-software updates break integrations. Five minutes a month keeps it alive.

The numbers that make this worth building

Say you close 40 jobs a month and currently convert 5% to reviews — 2 reviews. A well-built flow with a follow-up nudge routinely converts 25–35% of completed jobs. On 40 jobs, that’s 10–14 reviews a month instead of 2.

Over a year, that’s the difference between adding roughly 24 reviews and adding 140. Steady, recent reviews — many mentioning the service and city in the customer’s own words — are one of the strongest signals in Google’s local map ranking.

And it compounds: higher ranking → more inbound calls → more completed jobs → more automated review requests → higher ranking still. Once the trigger is wired, that loop runs without you touching it. Pair it with something that catches the inbound demand — like missed-call text-back — so the extra calls turn into booked work instead of voicemails.

The honest takeaway

This works best if you’re doing at least 20–30 completed jobs a month and already track job status in field software or a CRM. That’s the raw material the automation needs. If you’re doing a handful of jobs and know every customer by name, a personal text from you might genuinely outperform automation for now.

But if you’re finishing dozens of jobs a month and leaving reviews to chance, you’re handing free ranking to the competitor who built the system. The reviews are already earned — you’re just failing to collect them.

First concrete step, today: open your field software and find the exact status name that means “job is paid or signed off.” That one field is the trigger everything else hangs on. Once you know it, you can wire the flow — or we can build it end to end, from the trigger to the follow-up nudge to the unhappy-customer routing, so you never think about asking for a review again.