Review request timing and cadence: when and how often to ask
Whether a homeowner leaves a review depends less on what you say than on when you ask. The moment matters, the follow-up matters, and a steady drip matters more than any one-time push.
Most review requests fail for a reason that has nothing to do with the wording: they arrive at the wrong time. Ask the day the homeowner walks their finished kitchen and they respond. Ask three weeks later, after the punch list is forgotten and the feeling has faded, and the request gets ignored. Recency is not only about how you feel; it is about how buyers judge. BrightLocal found that only 20 percent of consumers say a review needs to be from the last two weeks to influence them, down from 25 percent in 2023, with most focusing on reviews from the past month (BrightLocal, 2025). That single fact reframes the whole problem. Old reviews get discounted, so a one-time blast goes stale, and the only durable answer is a steady cadence of well-timed asks.
Ask at the moment of delight, not later
A homeowner is most willing to leave a review at the emotional high point of working with you: the moment the job is done well and they are visibly pleased. The crew clears out, the final walkthrough goes clean, the new addition looks exactly right, and the homeowner says some version of "that's perfect." That sentence is your cue. Their satisfaction is at its peak, the details are fresh, and the goodwill that drives someone to write a public endorsement is fully charged. Wait, and all three decay.
Timing also shapes the content of the review, not just whether it appears. A customer who writes while the experience is vivid recalls specifics, the name of the person who helped, the thing that went right, the worry that got resolved, and specific reviews persuade other buyers far more than vague ones. Ask weeks later and you get "good service" if you get anything at all, because the texture has faded.
The practical rule is to make the ask part of the job, not an afterthought you remember on Friday. Train the team to recognize the moment of delight and trigger the request then, by text on the spot or by an automated message sent within hours, so the request lands while the feeling is still real.
Immediate or delayed depends on your business type
"Moment of delight" does not fall at the same point for every business. For a service that delivers its value on completion, a clean install, a repair, a haircut, the high point is the moment the work is done, so the ask should go out immediately or within a day. For a service whose value reveals itself over time, the customer cannot honestly review on day one because they have not yet experienced the outcome, so the ask should wait until the result is visible.
Getting this wrong cuts response either way. Ask too early on a slow-burn service and the customer has nothing to say. Ask too late on an instant one and the moment is gone. The fix is to map your own delivery to the point where the customer first feels the benefit, then anchor the request to that point rather than to a fixed delay applied to everyone.
The list below is a starting frame, not a law. Test the windows against your own response data, because the right delay is the one that catches your customer at the peak of their satisfaction, which only your numbers can confirm.
Where the moment of delight tends to fall by business type:
- Home services and repair: at completion or within 24 hours, while the fixed problem is fresh
- Salons, dental, and personal care: same day, before the visit fades from memory
- Restaurants and hospitality: within a day of the visit, while the experience is vivid
- Contractors and remodels: at final walkthrough, once the customer can see the finished result
- Professional and recurring services: after the first clear win or milestone, not at signup
- Products with a learning curve: a week or two in, once the customer has used it enough to judge
Why a steady drip beats a one-time blast
The instinct to email your entire customer list once and harvest a pile of reviews is understandable, and it is a mistake. Reviews age in the eyes of buyers. BrightLocal found that 47 percent of consumers rate a platform's "sort by newest" function as highly useful, which means nearly half actively seek out the most recent reviews before deciding (BrightLocal, 2024). A wall of reviews all dated the same month last year signals a business that asked once and went quiet, and a buyer reading it today is looking past those entries for something current.
Search ranking rewards the same behavior. In Whitespark's Local Search Ranking Factors study, review recency ranked among the local pack signals, with a consistent stream of new reviews valued more than an old burst, because a steady flow tells Google the business is active and currently earning praise (Whitespark, 2023). A spike followed by silence does the opposite. The mechanics of both the buyer's judgment and the algorithm's reward point the same way: little and often beats big and once.
A drip also protects you operationally. Asking a few customers a week is sustainable, keeps your average rating responsive to how you are doing now rather than a year ago, and means a single bad stretch does not define your profile forever. The goal is velocity, a predictable number of fresh reviews arriving every week, not a one-time total you can point to.
What a steady cadence delivers that a blast cannot:
- Fresh-dated reviews that pass the recency check buyers and Google both apply
- Steady review velocity that signals an active, currently-praised business
- A rating that reflects your performance now, not a snapshot from last year
- Resilience, so one rough week does not sink an otherwise strong profile
- A sustainable workload your team can actually keep up with every week
- A natural distribution of dates that looks organic rather than orchestrated
One well-timed follow-up reminder changes the math
Most people who intend to leave a review never get around to it on the first ask. They mean to, the message slips down the inbox, and the moment passes. A single, polite follow-up to non-responders recovers a meaningful share of those lost reviews; industry data on review-request flows points to a follow-up reminder recovering roughly 40 to 50 percent more reviews than the first request alone. The reminder costs almost nothing and works because it catches the willing customer who simply forgot.
The discipline is to stop at one. Send the initial request, wait several days, send one reminder to those who have not responded, and then stop. Beyond a second touch, the response curve flattens and the irritation curve climbs, so additional reminders buy you few extra reviews at the cost of looking pushy. One reminder is the sweet spot: it captures the forgetful majority without nagging the uninterested minority.
Sequence the touches across channels where you can. A text request tends to be seen fast, and an email follow-up a few days later reaches people the text missed, so the two together cover more of the list than either alone. The point is not volume of messages; it is giving each willing customer a second, gentle chance before the moment closes for good.
A wall of reviews all dated the same month last year tells a buyer one thing: this business asked once and went quiet.
Best days and times to send the ask
When a request lands during the week affects whether it gets opened. Requests sent on weekends and major holidays tend to underperform meaningfully against midweek sends, because people are away from their routine and the message gets buried by the time they return. Industry send-time data consistently puts the response trough on Saturdays, Sundays, and holidays, where lift can fall well below a midweek baseline. Midweek, roughly Tuesday through Thursday, is the reliable window.
Time of day matters less than day of week, but the same logic applies: aim for hours when people check their phone and inbox without being mid-task, late morning and early evening tend to outperform the start and end of the workday. None of this overrides the moment of delight, though. A request triggered the instant a job is finished beats a perfectly scheduled Tuesday send every time, because relevance trumps timing tricks.
Treat send-time rules as a tiebreaker, not a strategy. Where a request is event-triggered, send it immediately and ignore the calendar. Where you batch reminders to non-responders, lean them toward midweek daytime hours. The cadence below blends both ideas into a workable default you can then refine against your own open and response rates.
A workable default cadence to start from:
- Trigger the first request at the moment of delight, immediately for event-based services
- Send one follow-up reminder to non-responders after three to five days
- Stop after the single reminder to avoid fatigue and opt-outs
- Batch any scheduled sends toward Tuesday through Thursday
- Favor late morning and early evening over the start and end of the day
- Cap total review-related messages per customer to protect goodwill
Avoid over-asking and request fatigue
The opposite failure of asking too late is asking too often. A customer who gets three review requests for one job, or who is pinged every time they interact with you, learns to ignore your messages and may unsubscribe, which costs you the channel entirely. Each extra message past the first reminder recovers fewer reviews and risks more annoyance, so more asking is not more reviews, it is diminishing returns with rising downside.
Set guardrails. Cap the number of review requests any single customer receives for a given job, suppress requests to anyone who recently left a review or opted out, and space repeat asks for returning customers so a regular is not hounded on every visit. The aim is to ask each willing customer clearly, once or twice, and then leave them alone whether they wrote a review or not.
Fatigue is also why the drip must be spread across your customer base, not concentrated on your most loyal few. Rotating the ask across the steady flow of new and recent customers gives you fresh reviews every week without burning out any individual, which is exactly the balance a managed cadence is built to hold.
How WellBuilt tunes review timing and cadence
WellBuilt runs review generation as a managed, measured workstream rather than an occasional push. We start by mapping your delivery to the moment a customer first feels the benefit, then set the trigger for the first request to that point, immediately for completion-based work, delayed where the result takes time to show. The request fires automatically off the event, so it lands while the goodwill is real instead of waiting on someone to remember.
From there we build the cadence: a single well-timed follow-up to non-responders, sequenced across text and email, with send times nudged toward midweek where requests are batched. We set the guardrails too, capping messages per customer, suppressing recent reviewers and opt-outs, and spreading the ask across your customer base so no one is over-asked and the channel stays healthy. The drip is sized to produce a steady weekly flow of fresh reviews, not a one-time spike that ages out.
Then we measure and adjust. We track response rate and review velocity, the two numbers that tell us whether the timing is right and the flow is steady, and we tune the windows against your own data rather than generic benchmarks. If you want a cadence that keeps fresh reviews arriving every week, book a free Blueprint and we will map it to your business.
Key takeaways
- Trigger the first request at the moment of delight, the instant a job is done well, not days or weeks later when the feeling has faded.
- Match the timing to your business: ask immediately for completion-based services, but wait until the result is visible for slow-burn ones.
- Run a steady weekly drip instead of a one-time blast, because buyers and Google both discount old reviews and reward a fresh, consistent flow.
- Send exactly one well-timed follow-up to non-responders, then stop, since the second touch recovers most of the lost reviews and further nagging only causes fatigue.
- Set guardrails, cap messages per customer, suppress recent reviewers and opt-outs, and measure response rate and review velocity, not a one-time total.
SourcesBrightLocal, Local Consumer Review Survey, 2025 · BrightLocal, Local Consumer Review Survey, 2024 · Whitespark, Local Search Ranking Factors, 2023
Questions, answered straight.
How soon after the job should I ask for a review?
As soon as the homeowner feels the benefit, which for most completion-based work means at the final walkthrough or within 24 hours. Satisfaction peaks at the moment the job is done well and the details are fresh, so a request that lands then gets both higher response and more specific reviews. For longer custom builds whose payoff lands at move-in, wait until the result is visible, then ask. The mistake to avoid is a generic delay applied to everyone regardless of when value lands.
Is it better to ask everyone at once or a few customers at a time?
A few at a time, consistently. Buyers discount old reviews, and BrightLocal found nearly half of consumers actively use 'sort by newest,' so a one-time blast ages out and signals a business that went quiet. A steady weekly drip keeps fresh-dated reviews arriving, which both buyers and Google reward. It also keeps the workload sustainable and means one bad stretch does not define your profile. Aim for steady review velocity, not a single large total.
Should I send a follow-up reminder if someone doesn't respond?
Yes, one. Most people who intend to review never act on the first ask, and a single polite reminder to non-responders recovers a large share of those lost reviews at almost no cost. The discipline is stopping after that one follow-up. Beyond a second touch the response curve flattens while irritation and opt-outs climb, so additional reminders cost goodwill for few extra reviews. One reminder, sent a few days after the first request, is the sweet spot.
Does the day or time I send the request matter?
It helps as a tiebreaker, not a strategy. Requests sent on weekends and holidays tend to underperform midweek sends, so batch any scheduled reminders toward Tuesday through Thursday and favor late morning or early evening. But day-of-week tuning never beats relevance. A request triggered the instant a job is finished outperforms a perfectly scheduled Tuesday send, so for event-based services send immediately and ignore the calendar entirely.
Reviews & Social Proof
Want this run for you, not just read about?
Turn happy customers into the proof that wins the next one — more reviews, stronger testimonials, and a reputation that sells while you sleep.