Reviews per 100 completed jobs
Normalizes review volume against workload, so slow months do not hide progress.
For a plumbing company, Google reviews drive the map pack, Local Services Ads ranking and the homeowner's decision at 7 a.m. with a flooded laundry room. Most shops do good work every day but ask for reviews inconsistently, often only when a tech remembers or a manager runs a push.
A consistent review workflow asks every customer at the right moment, usually shortly after the job is completed and paid, through a channel they actually read. It also catches problems early, so a frustrated customer reaches a manager before they reach Google. A manager still writes or approves every public reply to a review.
When a job is marked complete and paid in your field software, a review request is scheduled, typically within a few hours by text.
Messages mention the tech by name and the type of work, using your approved template, so they read like a note from the company rather than a mass blast.
Customers who reply with a complaint or low rating are flagged to the service manager for a call, while everyone keeps the same direct path to leave a public review.
Repeat customers and members get an occasional, separate referral prompt, timed after a positive experience rather than with every invoice.
Drafted replies to new Google reviews are reviewed and posted by a manager, thanking customers and addressing complaints calmly. Replies go out within a day or two.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
Normalizes review volume against workload, so slow months do not hide progress.
Shows which techs leave customers happy enough to post, and where coaching helps.
Tracks how quickly flagged complaints get a personal call.
Measures whether structured referral asks produce booked work.
For example, on the same afternoon a tech clears a kitchen drain in Wheat Ridge and another replaces a garbage disposal in Golden. Both customers get a text two hours later naming their tech. The first leaves a five-star review. The second replies that the tech left a mess under the sink. The service manager sees the flag, calls that evening and sends someone to clean up the next morning. This illustrative scenario shows the routing, not a measured result.
In the first 30 days we would measure your current review rate per completed job and by tech, review how requests are sent today, and check your Google Business Profile setup. Then we would agree on timing, templates and the complaint routing rule for a pilot.
Asking for feedback and following up on complaints is fine. What Google does not allow is review gating, meaning only sending happy customers to the review link. We would design the flow so every customer can leave a public review, while complaints also get a fast personal response.
Some field platforms include review request features, and dedicated tools like Podium and NiceJob go further. Whether you need a separate tool depends on volume, how you want to handle replies and what you already pay for. We would review your current setup before recommending anything.
Google says review count and rating are among the factors for Local Services Ads ranking, alongside things like responsiveness. We would not promise a ranking change, but a steady flow of genuine reviews generally supports both the ads and the regular map listings.
Illustrative defaults for a plumbing company. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Review and referral requests: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.