Sound familiar? · Reviews

Why won't my customers leave reviews?

Most of your customers would leave a review. Almost none of them have been asked at the right moment with a link in their hand. The problem is not willingness. It is the ask.

Updated October 14, 2026 Kaizen CRM

The short answer

Customers do not leave reviews because the ask is late, unowned, and hard to act on: "find us on Google" a week later is a chore, while a text with a direct link while the technician is still in the driveway is a thirty-second favour most people will do. Most customers are willing; only a fraction are ever asked, and fewer at the right moment. Automate the request at job close, route unhappy customers to you first, and a steady weekly trickle of reviews becomes a moat within a few months.

You know this is you when

You have been in business for years and have fewer than fifty reviews.
Reviews arrive in bursts when someone remembers to ask, then nothing for months.
The ask, when it happens, is "if you get a chance, we are on Google."
A competitor with worse work and more reviews keeps winning the map.
Your most recent review is from last winter.

88%

of consumers trust online reviews as much as personal recommendations

KAIZEN CATEGORY RESEARCH · MORE DATA →

What it is costing you

For a service business, the review count next to your name is the first quote every prospect reads. A homeowner choosing in July looks at the map and reads the three most recent reviews. A business collecting two a month has a rolling wall of current proof; one collecting eight a year is being judged on what somebody wrote last winter. Same work, same technicians, completely different conversion from the same listing.

The cost is paid on every lead you generate. A thinner review profile lowers the conversion rate of all your marketing at once, which means every channel costs more per job than it should, and the competitor with 340 reviews is winning jobs they never had to be better to win.

Why it keeps happening

Review requests fail for boring reasons. Nobody owns the ask, so it happens when someone remembers, which is after the enthusiasm has faded. It arrives as "find us on Google," which asks the customer to do the work of finding you. And it is sent once, if at all, with no gentle reminder for the many customers who meant to and forgot.

Timing is most of it. The moment of maximum goodwill is the moment the job finishes well: the customer is relieved, the technician is still there, the problem is visibly solved. A request in that window gets a yes; the same request three days later gets a "sure, when I get a chance," which means never.

And fear of the bad review stops a lot of asking. Owners imagine inviting criticism. In practice, unhappy customers leave reviews whether or not you ask; happy ones only do so if you do. The ask shifts the ratio in your favour, especially if the unhappy ones are routed to you privately first.

How to fix it

01
Ask at job close, automatically, with a link
The moment a job is marked complete, the customer gets a short text: thanks for having us, and if you have thirty seconds, here is a direct link to leave a review. No one has to remember, and no customer has to search for you.
02
Route by sentiment
Ask "how did we do?" first. Delighted customers go straight to the review link. Anyone unhappy is routed to you privately, a chance to fix it before it becomes a public one-star. The public profile fills with the customers you served well.
03
Send one gentle reminder
Most customers who meant to leave a review did not. A single follow-up three days later, for anyone who did not click, roughly doubles the response. More than one and it reads as pestering.
04
Let it compound
A steady drip of weekly reviews compounds exactly as the philosophy says: in a year you are the obvious choice on the map, and every channel converts better because of it. Kaizen sends the ask, routes the sentiment, and logs the outcome on the record, so review velocity becomes a number you watch rather than a favour you remember.

See the fix running, on your business.

A 30-minute walkthrough with Mel, built around too few reviews. No deck: the product, using scenarios from your trade.

Book a walkthrough

Common questions

Is it allowed to ask for reviews?

Asking is fine and expected. What platforms prohibit is offering incentives for reviews, asking only customers you know are happy while suppressing others (review gating), or writing them yourself. Asking everyone and routing unhappy customers to a private conversation first is a service-recovery step, not gating, provided they can still review publicly if they choose.

What should the request say?

Short, personal, specific, and with the link in it. "Thanks for having us today, Sarah. If you have thirty seconds, a quick review here helps us more than you would think: [link]." The technician's name in the message raises the response rate noticeably.

How many reviews should I be getting?

A useful target is a review from one in every four or five completed jobs. A business doing sixty jobs a month should be adding twelve to fifteen reviews a month. If you are adding two, the ask is the problem, not the customers.

How does Kaizen handle reviews?

The request sends at job close with a direct link, sentiment routing sends unhappy customers to you first, one reminder follows for non-responders, and the outcome lands on the customer record. Review velocity becomes a report instead of a memory task.

In your trade, specifically

The same leak reads differently in every business. These are the versions written for the trades it hits hardest.

Keep reading

Review Automation Software → How to get more Google reviews Google Business Profile for contractors Handling unhappy customers