How to Automate Google Review Requests After Every Job

The review ask should fire on its own the moment a job closes — no tech reminders, no office checklist, no memory required. Here's the trigger build, using tools you probably already pay for.

System 4 from the Leveraged Owner Starter Pack

By Leveraged Owner · The 5-Star Review Engine

Every contractor has the same story: "We do great work, we just never remember to ask." The tech finishes, packs up, drives to the next job. The office is invoicing. Nobody sends the review request — not because they don't care, but because the ask lives in someone's head instead of in a system. Heads forget. Systems don't.

The strategy behind this automation — timing, wording, the follow-up — lives in the pillar guide, How to Get More Google Reviews as a Contractor. This post is the build: the trigger, the tools, the exact setup.

The trigger: the job-close event

Everything hangs on one event: the job is marked complete and the invoice is sent or paid. That's the moment satisfaction peaks — the problem is solved, the tech just left, the house is comfortable again. Your automation watches for this event and fires the review request 30–60 minutes later (the delay keeps it from feeling robotic, and gives the customer a moment to enjoy the fixed AC).

Where does the "job closed" signal come from? Your field-service software (field-service software = field service management software — Jobber, Housecall Pro, and similar tools that run your scheduling, dispatch, and invoicing). When the tech taps "job complete" or the office marks the invoice paid, that's the trigger. If you're not on field-service software yet, the trigger can be a simple status change in whatever you use to track jobs — even a spreadsheet row marked "done," though that's the manual version.

Lane 1: Your field-service software already does this (check first)

Before buying anything, check what you own:

Jobber: review-request automations on higher tiers — check your plan's automation settings for "request review after job completion."
Housecall Pro: automated review requests on higher tiers, triggered from the completed-job event.
What to verify: that the trigger is the job-close event (not job creation), that the message includes a direct review link, and that there's a follow-up for non-responders. If any piece is missing, supplement with Lane 2.

If you're already paying for the tier that includes this, turning it on is a 10-minute settings change — the highest-ROI 10 minutes of your month.

Lane 2: The automation-tool build (GoHighLevel / Zapier-style)

If your field-service software doesn't do it, wire it yourself. The build is the same in any automation tool:

Trigger: "Job status changed to Complete" (or "Invoice marked Paid") in your field-service software/CRM. (CRM = customer relationship management software — your customer database.)
Delay: wait 45 minutes.
Condition: only fire if the job type is one you want reviews for (skip callbacks and warranty rework — more on that below).
Action: send the SMS review request with the direct Google review link.
Wait 3 days → condition: if no review detected, send the follow-up nudge.
End. Two touches max from the automation.

The review link: get your direct Google review link from your Google Business Profile (Share → review link). Shorten it if it's ugly. This link must go straight to the review form — every extra click loses reviewers.

The messages

The initial ask, from the tech by name:

Hi [First Name], this is [Tech Name] from [Business Name] — glad we got the [service] sorted today. Would you mind leaving us a quick Google review? It really helps our small business: [Review Link]. Reply STOP to opt out.

The 3-day follow-up:

Hi [First Name], [Tech Name] from [Business Name] again — just a friendly nudge on that Google review if you have 60 seconds: [Review Link]. No worries either way! Reply STOP to opt out.

Who NOT to ask (the exclusion list)

Automation without exclusions will eventually ask the wrong person. Build the skip conditions in from day one:

Callbacks and warranty rework. The customer is annoyed — even if you fixed it beautifully, the review ask lands wrong. Skip.
Jobs with open complaints. If there's an unresolved issue on the ticket, the automation should wait. Asking for a review mid-dispute is how 1-stars happen.
Commercial clients on the same flow. Property managers need a different ask (different timing, sometimes a different surface like LinkedIn). Don't run them through the residential automation.

Note what this list is not: it's not filtering unhappy customers to suppress bad reviews. That's review gating, and it violates Google's policy. These are operational exclusions (wrong job type, open dispute) applied evenly — everyone who got a normal completed job gets the same ask.

The QR code backup (for the no-smartphone-text crowd)

The automated text covers most customers — but not the ones who don't text back, the older customers who prefer paper, or the commercial site contact who never gave a cell number. The backup is physical: a review card the tech leaves behind.

The card is simple — your logo, "Enjoyed our work? It takes 60 seconds," and a QR code linking straight to your Google review form. Print them in bulk (a few hundred costs almost nothing), and make leaving one part of the job-close routine: invoice handed over, card on top. The QR code is generated from your Google Business Profile's review link — the same link the automation texts. Two paths, one destination.

Track which path produces reviews by asking in the review response ("thanks — did you get our text or the card?") for a month. Most shops find the card adds a meaningful lift on top of the automation — mostly from the 60+ customers the texts miss. It's the cheapest review lift in the whole engine.

The "respond to every review" half of the automation

89% of consumers expect the owner to respond to reviews (BrightLocal 2026). The request automation is half the engine; the response habit is the other half. Set a daily 5-minute calendar block: morning coffee, respond to any new reviews. Short, human, specific — "Glad the new water heater's working out, [Name]!" beats "Thanks for your feedback!" every time. The negative-review response frameworks are their own post in this series.

Compliance notes

No incentives tied to positive reviews. Never offer discounts or gifts "for a 5-star review" — it violates Google's policy and can get reviews removed.
No review gating. Don't survey customers first and only send the Google link to the happy ones. Everyone gets the same ask.
Texting rules apply: 10DLC business-texting registration on your business number (1–7 day approval, ~$15–$20 one-time), opt-out language in the first automated text, and observe TCPA (federal telemarketing law) quiet hours (no marketing texts before 8am or after 9pm in the recipient's local time). This is general information, not legal advice.

Related guides in this series

Start with the strategy in the review-engine pillar guide. For the wording deep dive, read How to Ask for Google Reviews: Timing, Wording, and the Text That Works; for five more ask templates, Google Review Request Text Templates. Browse the full blog for everything published.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full review-automation setup guide (standard operating procedure) (trigger setup for Jobber, Housecall Pro, and GoHighLevel), every ask and follow-up script, the exclusion-list configuration, and screen-by-screen setup instructions for all 8 systems.

See the $27 Starter Pack

Stats sourced as labeled: 89% expect owner responses (BrightLocal 2026).