Why most review-asking fails

The standard playbook for getting reviews is 'remember to ask at the end of every job.' This fails for three reasons:

  • Inconsistent. Some techs ask, some don't, some forget. You ask maybe 20% of the time.
  • Wrong moment. Customer is paying you in person. They are not going to pull out their phone, find your Google listing, and write a review right then.
  • No follow-up. Even when customers say 'sure, I'll do it later', they don't unless you remind them.

Result: businesses that rely on 'remember to ask' get 1-3 new reviews per quarter. Businesses that automate it get 15-50.

The automated system that works

Step 1: Trigger from job complete

The moment a job is marked complete in your CRM, the system sends a text to the customer. Not the next morning. Not later that day. The moment the tech closes the ticket.

Step 2: Send a private satisfaction check first

Initial message: 'Hey [Name], thanks for choosing us today. On a scale of 1-5, how did we do?' One tap to reply.

Why this matters: customers who reply 4-5 stars are immediately routed to your Google review page. Customers who reply 1-3 stars are routed to a private feedback form — so you can fix the problem before they post a public complaint.

Step 3: Route 5-star responders to Google

When the customer taps '5', they immediately get: 'Awesome — would you mind sharing that on Google? Takes 30 seconds: [direct link to your Google review form].' The link drops them on a pre-filled review screen, not a search results page.

Step 4: Gentle follow-up at day 3

If they didn't leave a review yet, send one more text: 'Hey [Name], just a quick reminder — would love your feedback on Google if you have a minute. Here is the link again: [link]. No worries if you don't have time.' That's it. Don't pester.

Why timing the request matters

The single biggest variable in review response rate is when you ask. Requests sent within 30 minutes of job complete get 4-6× the response rate of requests sent the next day. Why?

  • Peak satisfaction is the moment the job is done well.
  • Customer still has your name and the experience top of mind.
  • They are not yet distracted by the rest of their day.

Manual systems can't hit this 30-minute window consistently. Automated systems hit it every time.

The private-feedback filter is critical

If you send every customer straight to Google without filtering, you will get more 1-2 star reviews than 5-star ones. Unhappy customers are more motivated to leave reviews than happy ones.

The fix: ask satisfaction privately first. Route happy customers to public reviews, route unhappy ones to a private channel where you can resolve the issue. This is sometimes called 'review gating' — Google's policy permits it as long as you don't withhold negative review opportunities. Routing 1-3 star customers to a private support form is fine; refusing to let them leave a public review is not.

RunBy's review automation implements this filter correctly out of the box.

Tools to build this

DIY

Twilio SMS + a Zapier workflow + your CRM trigger. ~$80/month + 10-20 hours to set up. Maintenance is ongoing.

Standalone review tools

Podium, Birdeye, NiceJob, GatherUp. $200-$500/month. Strong tools, but they only do reviews — no call answering, no follow-up automation, no daily briefings.

Bundled in AI receptionist software

RunBy includes review automation as one of 7 core features at $299/month flat. If you need just reviews, a standalone tool may be lighter. If you need reviews plus the rest of the back-office workflow, bundled wins on price.

What good results look like

Service businesses 90 days after turning on automated review requests typically see:

  • Review response rate: 15-30% (vs. 1-3% manual)
  • New Google reviews per quarter: 15-50 (vs. 1-5 manual)
  • Average star rating: 4.6-4.9 (vs. 3.8-4.4 with random review flow)
  • Local map pack ranking: improvement typically visible in 60-120 days

Related reading