The customers who write reviews without being asked are, disproportionately, the ones with a grievance. A hundred quiet, satisfied jobs and one billing dispute can leave a profile that reads three stars — not because the work was three-star, but because only one of those hundred and one people was motivated enough to type. Fixing that is not a marketing project. It is a timing and consistency project.
Why asking is the whole problem
Asking works. Most satisfied customers will leave a review if the ask arrives at the right moment and costs them almost nothing. The trouble is that asking, done by humans, is inconsistent in exactly the wrong direction: it happens in slow weeks, when someone remembers, and it stops in busy weeks — and busy weeks are when the good work is happening. The result is a review page that undersamples your best months and overrepresents whoever was angry enough to find the button on their own.
The trigger is a status change, not a memory
The mechanical fix is to hang the request on an event that already happens in your records. When a job flips to closed in the field-service software, or the invoice flips to paid, the request goes out. Nobody decides, nobody remembers, nobody is too busy. The event that means "the work is done and settled" is the event that fires the ask, which also means the ask scales exactly with the work: forty completed jobs in a hail month produce forty asks, without anyone in the office touching it.
Paid is usually the better trigger than closed. A customer who has paid has, in the plainest possible way, signed off — and it keeps the request from landing in the middle of an invoice question, which is the one moment you do not want to be asking.
One tap from the text to the stars
Every step between the request and the submitted review loses people. If the text says "find us on Google and leave a review," the customer has to search your business name, pick the right listing out of three similar ones, find the reviews section, and find the button — and at each step, some of them reasonably decide dinner matters more. The request should carry a direct link to your listing's review form, so one tap opens the box with the stars right there. The difference between a one-tap link and a scavenger hunt is the difference between a system that produces reviews and one that produces good intentions.
Same day, while the work is visible
The best moment to ask is while the job is still the newest thing in the customer's day — the truck barely out of the driveway, the house cool for the first time in a week, the new panel still the cleanest thing in the garage. Satisfaction is at its peak and the details are fresh, which is also when reviews come out specific: the tech's name, what was fixed, how the crew left the site. Specific reviews are the ones that persuade the next customer. Three weeks later, stapled to a paper invoice, the same request meets a memory that has already moved on.
Ask everyone, or don't bother
Some tools offer to pre-screen: ask the customer privately how the job went, then route the happy ones to Google and the unhappy ones to a feedback form only you see. This is called review gating, and Google's review policies prohibit it — soliciting reviews selectively from customers you expect to be positive is grounds for having reviews removed. The FTC has likewise treated suppressing or screening out negative reviews as deceptive. So the rule here is flat: every completed job gets the same ask, or you run no program at all.
It happens that the honest version is also the credible one. A wall of unbroken five-star reviews reads as curated. A profile with a natural mix — mostly fives, an occasional four, a rare three answered with a professional response — reads like a real business run by adults, which is what the next customer is actually trying to find out.
A steady rhythm beats a burst
Fifteen reviews dated the same week looks like a purchased batch, to readers and to the platforms alike. Reviews that arrive at the pace your jobs finish look like a working business — and recency carries its own weight. A homeowner choosing between two roofers, one whose latest review is fourteen months old and one whose latest is last Tuesday, has learned something real from the dates alone. An event-triggered ask produces exactly that rhythm, because it is the rhythm of the work itself.
What this will not fix
It will not fix bad work; it will surface bad work faster, which is only a gift if you act on it. It cannot manufacture volume you do not have — a shop finishing eight jobs a month will accumulate reviews at eight-jobs-a-month pace, and no honest system changes that. It should hold the ask when a job ends in a dispute, which is a reason to trigger on payment and to keep a human able to pause a send. And because these requests travel as text messages, the standing rules apply: the message names the business, STOP works instantly and permanently, and nothing goes out at ten o'clock at night.
Where to start
Open your own listing and read your last ten reviews — the dates more than the stars. If there are month-long gaps between them while your calendar was full, you have an asking problem, not a reputation problem, and an asking problem is the fixable kind.