Most advice on reviews stops at "ask for them." The harder, more valuable question is one of rhythm: how often to ask for Google reviews, at what moment, and through which channel — without your outreach starting to feel like spam. For Local Services Ads advertisers this is not a soft branding issue. Since Google Business Profile (GBP) linkage became mandatory and LSA reviews began flowing through GBP, the star rating and count on your paid listing come straight from the reviews you gather. A cadence that quietly annoys customers, or one that produces suspicious bursts, works against the exact asset it is supposed to build.
This article is about cadence specifically — timing, frequency, and spacing — not the internal team workflow of who clicks which button. The goal is a request pattern that a real, busy, well-run business would naturally produce.
Ask at the peak-satisfaction moment
The single biggest lever on response rate is not frequency at all — it is timing the first ask to the moment satisfaction is highest. For most home services that is right at job completion: the drain is running, the unit is cooling, the customer just watched your technician clean up and explain the work. That feeling fades fast. A request that lands at completion or within a couple of hours captures a warm, specific memory; the same request a week later competes with everything else in the customer's life and reads as an afterthought.
Timing the ask well means you need fewer touches overall. When the first request hits at the right moment, a large share of the people who will ever review you do it then — which is what lets the rest of your cadence stay light.
How often to ask for Google reviews per job
Here is the honest answer on frequency: one clear ask, and at most one gentle reminder — then stop. That is the whole cadence for a single job. A first request at peak satisfaction, and if there is no response, a single low-key nudge a few days later for the people who meant to and forgot. A second reminder rarely converts anyone who ignored the first two; it mostly converts goodwill into irritation.
The reminder is not a repeat of the ask. Its job is to be easy to act on and easy to ignore — a short, friendly "in case it's helpful, here's the link" rather than a second sales pitch. If it still goes unanswered, that customer is done. Chasing a third and fourth time is how a review program starts to feel desperate, and desperation is the opposite of the calm confidence a strong reputation should project.
| Touch | Timing | Channel | Message intent |
|---|---|---|---|
| Ask #1 | At completion or within ~2 hours | Whatever the customer already used (text if they texted, email if they emailed) | Thank them, make the single request, hand over a direct one-tap link |
| Reminder (optional) | 3–5 days later, only if no response | Same channel as the first ask | One brief, low-pressure nudge with the link — easy to act on, easy to ignore |
| After that | — | — | Stop. No third touch for this job. |
Match the channel to the customer
Cadence is not only about how many times you ask; it is about asking where the customer already lives. If the whole job was booked and coordinated by text, a text review request feels like a continuation of the conversation. If everything happened over email, email is natural and a sudden text can feel like a channel you were not invited into. The rule of thumb: reach people through the channel they already used with you, and do not open a new one just to ask for a review.
This also keeps you off the wrong side of messaging etiquette. A single, expected text after a job the customer texted you about is normal. An unexpected text to someone who only ever emailed can read as intrusive — and repeated unexpected texts are exactly the pattern people label as spam.
Personalized single asks beat blasts
A review request that names the specific job — "thanks for trusting us with the water heater today" — outperforms a generic template, and it also spaces itself naturally, because it goes out as each job finishes. That is very different from exporting three weeks of customers and blasting them all on a Friday. The blast is easier to run, but it produces two problems at once: the messages are impersonal, and the reviews all arrive in a clump.
Personalization and cadence are linked. When each ask is tied to a real, recent job, the timing takes care of itself and the message is relevant. When you batch, you lose both.
Steady velocity beats bursts
Review velocity — a consistent trickle of new reviews over time — is widely understood to support local performance, and steady is the operative word. A profile that earns a handful of reviews every week, month after month, tells a believable story: a real business serving real customers at a normal pace. A profile that sits quiet for two months and then gets twenty reviews in three days tells a different, less believable story, and unnatural spikes are exactly the kind of pattern review platforms scrutinize.
The practical takeaway reinforces everything above. If you ask once per job, at the right moment, as jobs complete, your velocity is automatically steady — it mirrors your actual work volume. You only get bursts when you stop asking for a while and then try to catch up all at once. Consistency is not just safer; it is the natural byproduct of doing the simple thing every time.
The compliance backbone: ask everyone
None of this cadence matters if the underlying policy is wrong, so state it plainly: ask every completed customer, regardless of how you expect the review to go. The tempting shortcut — only inviting the customers who seem happy — is review gating, and it is a mistake on two levels. It manufactures a rating that does not represent real experience, which can run afoul of FTC deception standards and violates Google's own review policies; and it quietly starves your profile of the honest signal that makes a good rating durable. A steady, well-timed cadence sent to everyone is both the compliant path and the one that builds a reputation that holds up. This is general information, not legal advice — for your specific situation, consult a qualified attorney.
Put it together and the cadence is almost boring in its simplicity: one warm ask at the peak moment, one optional nudge, through the customer's own channel, personalized to the job, sent to everyone, every time. Boring is the point. It is what a trustworthy business looks like, and it is what keeps your outreach from ever feeling like spam.
Frequently asked questions
How often should I ask for Google reviews?
Per completed job, ask once at the moment the work is done and satisfaction is highest, then send at most one gentle reminder a few days later if there is no response. After that, stop for that job. Across your customer base, keep a steady flow of these single asks rather than firing large batches, which reads as more natural to both customers and Google.
Is it against the rules to ask every customer for a review?
No. Asking every completed customer the same way is the compliant approach. What creates risk is the opposite — filtering the ask by expected sentiment so only customers you think are happy get invited. That practice, called review gating, can violate FTC deception standards and Google's own review policies. Ask everyone, regardless of how you think the review will turn out.
Can asking too often get my Google Business Profile flagged?
Over-asking annoys customers and can suppress your response rate, and sudden large bursts of reviews can look unnatural. A calm cadence of one clear ask plus one optional reminder per job, spread out as jobs complete, avoids both problems. Steady velocity is safer and more durable than spikes.