How to Build an Automated Review Request System for Field Techs

Why Manual Review Asking Fails in the Field

Ask any tech to remember to request a review and here's what actually happens: they're loading the truck, the next job is already texting them, and the customer walked back inside five minutes ago. The ask either doesn't happen or happens as an afterthought, mumbled on the way to the van. Neither gets you a review.

The problem isn't that techs don't care. It's that review-asking is a task bolted onto a job that already has fifteen other tasks: paperwork, payment collection, photos, cleanup, the next dispatch. Anything that depends on a busy person remembering, at the exact right moment, to do one more thing, fails at scale. It might work for your top closer. It won't work across a crew of eight.

The fix isn't better training. It's removing the human memory step entirely. A system trigger that fires the moment a job status flips to "complete" doesn't forget, doesn't get distracted by the next call, and doesn't skip the customer who paid cash and left in a hurry. Every completed job gets the same ask, every time.

This matters more for field trades than almost any other business type. A dentist's office has the patient sitting in a chair for 45 minutes with staff who can hand them a tablet. A plumber has 20 minutes on-site and a customer who's relieved the leak stopped and mentally already moving on. The window to ask is short and it closes fast once the truck leaves the driveway.

The gap between column one and column three is the entire reason this silo exists. It isn't about writing a better ask. It's about the ask actually happening, consistently, without a human in the loop who might have a bad day.

What an Automated Review Request System Actually Needs

You need four pieces working together: a trigger, a message, a landing spot, and a follow-up. Miss any one and the system leaks reviews.

• The trigger. Something in your workflow has to fire the request automatically. That's usually a job status change in your field service software (job marked "complete" or "invoice paid"), a webhook from your dispatching tool, or in leaner shops, a tech tapping one button on their phone before they leave the driveway.
• The message. A short SMS beats a long email for response rate. Field service customers check texts faster than inbox. Keep it to two sentences: thank them by name, mention the tech or the work by name, one link.
• The landing spot. The link should go straight to your Google review composer, not your homepage, not a review-aggregator page with five platforms to choose from. Every extra click costs you conversions. Some shops use a review-gating step first (a private rating question before the public review link) to route unhappy customers to a private form instead of a public one star. Whether that's worth doing depends on your state, more on that below.
• The follow-up. One ask isn't enough. A second, softer reminder 48-72 hours later after no action catches the customer who meant to do it and forgot. Stop after two asks. A third message reads as nagging and costs you goodwill.

Most contractors running this today use one of three approaches: a dedicated reputation platform (Podium, NiceJob, Birdeye) that plugs into their CRM, a native automation inside their field service software (many of the bigger platforms have this built in now), or a lighter Zapier-style workflow connecting job-complete status to a texting tool. Which one fits depends on what you're already running for dispatch and invoicing, not on which tool has the flashiest dashboard.

The one thing all three approaches share: the trigger has to be a system event, not a person's memory. That's the whole point.

Timing: When to Send the Request

Timing is the single biggest lever in this system, bigger than message wording, bigger than which platform you use. Ask too early and the customer hasn't had time to evaluate the work. Ask too late and the job has faded from memory, or worse, they've had time to notice a problem you could have caught first.

The window that works for most field trades: send the first request within one hour of job completion, same day whenever possible. The work is fresh, the relief of a fixed problem is still active, and the tech's name is still top of mind. For jobs that wrap up in the evening, hold the send until the next morning between 9 and 11am rather than pinging a customer at 8pm.

The follow-up reminder goes out 48 to 72 hours later, only to customers who haven't clicked through. Beyond that window, response rates drop off fast and a third nudge starts to feel like spam.

One timing mistake specific to field trades: sending the request before the invoice is paid. A review request landing in the same breath as a payment reminder reads as transactional and can suppress the response, or worse, prompt a review that mentions a billing dispute. Sequence the ask after payment clears when your billing cycle allows it. If you invoice net-30 or use progress billing, don't wait for full payment. Trigger off job completion, not final invoice.

Review-Gating: What's Legal and What's Not

Review-gating means filtering customers before they reach the public review form, usually by asking a private rating question first ("How was your experience, 1-5 stars?") and routing low scores to a private feedback form instead of Google. This is where a lot of contractors get nervous, and rightly so. The rules changed.

As of the FTC's rule on fake and deceptive reviews (effective 2024), review-gating that suppresses negative reviews specifically because they're negative is prohibited if it's not applied evenly. In plain terms: if your system routes 1 and 2-star respondents to a private form while pushing 4 and 5-star respondents straight to Google, that's selective suppression and it's the kind of practice the FTC rule targets. Google's own review policies have long prohibited this too, calling it out as a terms-of-service violation that can get reviews stripped or your listing suspended.

What's still fine: asking every customer, regardless of how they answer, to leave a public review, while separately and transparently offering a way to reach you directly if something went wrong. The distinction is intent and evenness. A generic "how did we do, and if anything wasn't right, call us" line that goes to everyone is not gating. A branching workflow that only shows the public review link to happy customers is.

The practical move for most contractors: send everyone the same public review link. Add a separate, always-visible line (in the same text or on the same page) inviting anyone with a concern to call or text the office directly. That gives unhappy customers a real channel without hiding their experience from the platform, and it keeps you inside both Google's terms and the FTC rule.

This isn't a gray area worth gambling on. A caught pattern of selective gating can mean a wiped review history or an FTC inquiry, both of which cost far more than the handful of negative reviews you were trying to filter out. Ask everyone the same way. Handle bad experiences by being reachable, not by hiding the ask.

Scripts and Templates That Get Responses

The message itself matters less than the trigger and timing, but a bad script still tanks conversion. Three rules cover most of it: personalize with the tech's name, keep it under two sentences, and put the link with almost nothing between the greeting and the ask.

• Standard SMS (same-day repair): "Hi [First Name], this is [Company] following up on today's [service type] with [Tech Name]. If you have 30 seconds, a quick Google review helps us out a ton: [link]"
• Install/project completion: "Hi [First Name], thanks for choosing [Company] for your [project type]. We'd love to hear how it went: [link]. Anything not right? Call us direct at [phone]."
• Follow-up reminder (48-72hr, no response): "Hi [First Name], just a quick reminder if you have a minute: [link]. Thanks again for trusting us with the job."
• Recurring service (after 2nd+ visit): "Hi [First Name], you're a few visits in with [Company] now. If we've earned it, a review would mean a lot: [link]"

What to avoid: generic "we value your feedback" corporate phrasing, multiple links to multiple platforms in one message (pick one, Google, and ask for that), and any wording that implies the review is optional in tone but mandatory in follow-up frequency. Three texts asking for the same review reads as pressure, not gratitude.

Email works as a secondary channel for customers who don't text-enable easily (some commercial accounts, some older residential customers), but treat SMS as primary. Field service customers respond to texts inside minutes. Email response windows stretch to days, by which point the job has faded.

One more mechanical detail worth getting right: the tech's actual name in the message. "John completed your service today" outperforms "Our technician completed your service today" by a meaningful margin, because it turns an abstract company interaction into a specific person the customer just spent an hour with. If your field service software captures the assigned tech per job (most do), pull that field into the template automatically rather than hardcoding a generic line.

Rolling It Out Without Breaking Your Field Ops

The rollout mistake we see most: buying a reputation platform, connecting it to nothing, and hoping techs remember to trigger it manually. That's the same failure mode as manual asking, just with an extra subscription fee attached.

Start with the trigger, not the tool. Look at what your dispatch or invoicing software already does when a job closes out: does it fire a webhook, update a status field, or send a completion notification anywhere? That event is your hook. Most modern field service platforms (ServiceTitan, Housecall Pro, Jobber, and similar) either have native review-request automation built in or support a Zapier/webhook connection to a texting tool. Check what you already pay for before buying something new.

Roll it out to one crew or one service line first. Run it for two weeks, watch the response rate, and read every review that comes in for tone and accuracy before opening it up shop-wide. This catches script problems (wrong tech name field, broken link, timing that fires at odd hours) before they touch your whole customer base.

1. Audit your current job-completion workflow. Find the status change or event you can hook into.
2. Pick one tool: native automation in your field service software, a dedicated reputation platform, or a lightweight Zapier/texting combo.
3. Write two scripts: first ask and follow-up. Personalize with tech name and job type fields.
4. Test on one crew for two weeks. Track requests sent, click-through, and reviews posted.
5. Fix what's broken (timing, wording, broken links), then expand to the full team.
6. Set a monthly check: response rate, review volume, and star average trending in the right direction.

Once it's running, the system needs almost no ongoing labor. That's the entire point: it replaces a task nobody was reliably doing with a workflow that happens whether anyone remembers or not. The maintenance is a monthly glance at the numbers, not a daily task on anyone's plate.

What Good Looks Like: Benchmarks to Track

Once the system is live, three numbers tell you whether it's working: request-to-response rate, average time-to-review, and star-rating trend. Track these monthly, not daily. Daily swings from a small sample size will make you chase noise.

Request-to-response rate is requests sent divided by reviews received. A well-timed automated system in the 15-30% range is healthy for most field trades. Anything under 10% usually points to a timing or wording problem, not a bad customer base. Anything you're claiming above 40% sustained is worth double-checking against Google's own review count on your listing, because it likely means duplicate counting somewhere in your funnel, not an unusually generous customer pool.

Average time-to-review tells you whether your timing window is right. If most reviews land within 24 hours of the request, your first-ask timing is working. If most reviews trickle in only after the 48-72 hour follow-up, your first message may be arriving at a bad moment (mid-job, during dinner, before payment) and needs adjusting.

• Track monthly: requests sent, response rate, average star rating, time-to-review.
• Watch for: a specific tech or crew with a noticeably lower response rate (often a coaching opportunity, not a system problem).
• Red flag: a sudden spike in 1-star reviews right after launching the system. Usually means the ask window includes unresolved callbacks or incomplete jobs.

Don't treat this as a set-and-forget system that never gets revisited. Scripts go stale, staff turnover changes which tech names populate the message field, and what worked at 20 jobs a month behaves differently at 200. A quarterly script refresh and a monthly numbers check keeps it tuned. Beyond that, the labor cost of running this system should trend toward zero, which is the entire reason to automate it in the first place.