Reputation · The Review-Timing Leak
You're Asking For Reviews at the Worst Possible Moment
In This Article
The job just finished. The customer is standing there looking at it, genuinely happy. Somebody — you, or the text bot — fires off the review ask. Then: nothing. Or worse, three days later a review lands, and it's three stars, and it's not even about the work. It's about the invoice, or the reschedule, or something that happened after you'd already earned the five.
Here's the part that doesn't get said out loud: it's not that they refused. It's that you asked at the wrong moment, and the moment that would have worked already passed.
That's the Review-Timing Leak: real satisfaction, earned honestly, that never turns into a review — not because the customer didn't feel it, but because the ask arrived after the feeling that would have carried it. Most owners already ask (see how to actually get more Google reviews for the script). This isn't about whether you ask. It's about when.
The leak: it's not the ask, it's the beat
"We do great work but nobody leaves reviews" is one of the most common things a local business owner says — and almost always, the work isn't the problem. The ask isn't the problem either. Something in between is.
Every job has a beat where the customer feels the result the most — and a string of other beats after it where something less pleasant happens: paying, waiting on paperwork, a follow-up question, the next thing on their calendar crowding back in. The review ask usually gets attached to one of those later, less pleasant beats. Not on purpose. Just because that's when the workflow gets around to it.
So the real question isn't "how do we get more reviews." It's: when, exactly, does the ask actually land?
Why satisfaction has a shelf life
Satisfaction isn't a number that sits still once a job is done well. It has a shape. It rises through the work, peaks at one specific beat — the reveal, the handoff, the moment they actually see or feel the result — and then it resets the second something less pleasant happens next. Psychologists have a name for the general pattern (the peak-end rule); you don't need the term, just the shape of it: people remember, and act on, how an experience felt at its high point and its ending — not the average of the whole thing.
Ask inside that peak, and you're catching the feeling that's actually there. Ask after the next friction beat resets it, and you're asking a customer to manufacture enthusiasm for a memory that's already moved on. Same job. Same quality of work. Completely different odds of getting a review.
The two wrong moments
Almost every missed review comes from one of two timing mistakes — and most businesses are making one of them without knowing it.
Too early into a friction beat — asking at payment
A plumber finishes the repair, walks the customer through it, then hands them the invoice and asks for a review in the same breath as the total. The work was five-star. The moment wasn't — paying is a small loss even when the price was fair and expected. Tie the ask to that beat, and you're asking at the one part of the visit nobody enjoys.
Too late after the peak fades — the batch text, days later
A med-spa's generic "how was your visit?" text almost never fires the same day — it waits for whatever the next batch send happens to be, however many days out that lands. By then the glow of the result has faded into ordinary life — or worse, an unrelated hiccup (a billing question, a reschedule) has already reset the feeling. The text arrives looking like every other automated message the customer ignores that week. It's not read as a personal thank-you. It reads as noise.
Notice neither of these is a "they don't care" problem. Both are "the ask showed up at the wrong beat" problems — which means both are fixable without changing anything about the work itself.
The Peak Window
Call it the Peak Window: the specific beat where the customer can see or feel the transformation, and no friction event has intervened yet. Keys handed back. The final walkthrough. The after-photo turned around to show them. Checkout, but only if nothing's left to sign or explain.
The ask has to be ready to fire inside that window — in person if you can, or a text sent in the same minute if you can't, with the link already one tap away. Not "we'll follow up." Not a batch send later tonight. Right there, while the feeling is still the one they actually have.
This is a different leak from the Golden Hour — that's about how fast you respond once a customer is already upset, a recovery-speed problem. This is the opposite end: catching praise at its high point before it has a chance to fade. It's also different from a review response playbook, which is about what you do with a review once it's already posted. This piece only covers the moment before any of that — whether the review gets written in the first place.
Where your Peak Window actually falls
The beat looks different by trade, but it's always the same kind of moment: the customer sees the result, before anything else happens.
| Business type | The Peak Window |
|---|---|
| Home service (plumbing, HVAC, electrical) | The walkthrough — showing them the fix working, before the invoice |
| Contractor / remodeler | The reveal — pulling back the plastic sheeting, the final look |
| Auto repair | Handing back the keys, engine running, before they see the bill |
| Salon / med-spa | The mirror moment — right after the result, before checkout |
| Photographer | The first look at the gallery or a preview shot, not the invoice email |
| Any project-based service | The moment they say "wow" out loud — that's the window, wherever it falls |
You don't need a new review platform to fix this — you need the same ask, moved earlier. If you already have a working text or link (see the ask script and follow-up mechanics), the only change is when it fires: at the reveal, not at the invoice, and not on a delay.
What this isn't
- Not a script problem. If your ask script already works, keep it — see how to get more Google reviews for the actual wording and text/email setup. This page only covers when it fires.
- Not a reply problem. Responding to reviews you've already gotten is its own leak — see the review response playbook.
- Not a complaint-recovery problem. Speed after a customer is already upset is a different leak entirely.
- Not pressure. Moving the ask earlier doesn't mean rushing the customer — it means asking while the feeling that earns you a five-star review is still the one they're having.
The self-audit
Before changing anything, look at your last five completed jobs. For each one, find the moment the ask actually went out — and find the moment the customer's satisfaction was actually highest. Are they the same moment, or is there a gap?
Imagine every customer who left your shop this month got the ask inside that window — right at the reveal, one tap, nothing to remember later — instead of a text three days from now that arrives after the feeling already moved on. Now pivot: you don't need a new review system to close that gap. You need the exact same ask, moved to the moment it was always supposed to happen.
Frequently Asked Questions
Right at the reveal — the moment the customer sees or feels the finished result and before anything else happens. That's the keys handed back, the final walkthrough, the after-photo shown, the checkout with nothing left to sign. Ask there, in person or with a one-tap link already in hand, before any friction event resets how they feel.
Before, if you can sequence it that way, or in the same breath as the reveal rather than attached to the invoice. Paying is a friction moment, not a warmth moment — even happy customers feel a small loss when money leaves their account. Asking right as the bill lands ties your review request to the one part of the visit nobody enjoys.
Satisfaction doesn't sit still — it peaks at one moment and fades as ordinary life crowds back in. "I'll do it later" is sincere in the moment and gone by the next distraction. It's not that they didn't mean it. It's that the ask arrived after the feeling that would have carried it.
In person, at the reveal, beats a text sent later — but a text sent immediately, in the same minute as the reveal, works almost as well. The failure mode isn't the channel, it's the delay. A text that lands two or three days later is competing with everything else that happened since, not with the job you did.
Inside the same visit, ideally the same minute as the reveal — not hours later, not the next day, not on a batch send that fires whenever the next scheduled batch happens to go out. If the ask can't happen live, the fallback text should go out the moment the job is marked done, not queued for a later send.
