GoodMarksThe satisfaction curve and why it matters
Customer satisfaction after a service experience is not a static state. It follows a curve: it peaks at the moment of completion — when the problem is solved, the job is done, and the relief or pleasure of the outcome is fresh — and it decays from there.
The decay is not dramatic. A customer who was highly satisfied will not turn negative by the next day. But the motivation to take action — to translate that satisfaction into a public review — does decay meaningfully. A satisfied customer who is prompted to leave a review within an hour of job completion is in a different emotional and motivational state than the same customer receiving that prompt three days later.
This is the core insight behind timing: review requests are not notifications. They are interventions into a window of motivated willingness that opens after a positive service experience and closes gradually over time.
What behavioral research tells us
The psychological framework that explains review request timing comes from research on peak emotional states and memory. Nobel laureate Daniel Kahneman's work on the "peak-end rule" established that people evaluate experiences primarily based on how they felt at the emotional peak and at the end, not on an average across the duration.
For a service interaction that goes well, the emotional peak and end often coincide: the moment the job is complete, the problem is resolved, the customer feels the relief or satisfaction most acutely. That is the window when the motivation to reciprocate — to share the positive experience — is at its highest.
As time passes, several competing factors erode that motivation:
First, the emotional signal fades. The satisfaction remains, but the sharpness of the feeling that motivates action diminishes. By 72 hours later, the memory of the experience competes with dozens of other experiences the customer has had since.
Second, inertia accumulates. The mental cost of opening a link, finding the review page, and writing a few sentences feels larger when the emotional context has faded. In the immediate aftermath of a successful service, the activation energy for the same action is low.
Third, other demands intervene. A review request that arrives at a convenient moment on the same day is more likely to be acted on than one that arrives during a Monday-morning work crunch three days later.
Timing by service type
The optimal timing window varies by service type, governed primarily by how long the customer needs before they can evaluate the outcome.
Immediate-result services: Haircuts, car washes, oil changes, food service, most cleaning services. The outcome is visible at the moment of completion. Review requests sent within 30 minutes of service completion perform best. Same-hour SMS request rates are significantly higher than next-day email rates for these categories.
Same-day verification services: HVAC repair, appliance repair, electrical work. The customer needs to verify the repair is working before they can enthusiastically endorse it. Sending a review request immediately after the technician leaves — before the customer has run the air conditioner through a hot afternoon — risks either a premature review or a delayed one (customer intends to review once they've verified, then forgets). A 2–4 hour delay after completion is appropriate here.
Extended-cycle services: Landscaping projects, remodeling, legal matters, medical procedures. The outcome is evaluated over days or weeks. Early review requests in these categories risk reviews that reflect initial impression rather than ultimate satisfaction. A 24–48 hour delay lets the customer absorb the outcome while still keeping the request within the effective window.
Subscription and recurring services: HVAC maintenance agreements, regular cleaning services, lawn care. The timing question is different here — not when to ask after a single service, but how often to ask across an ongoing relationship. Asking after every visit creates fatigue. Asking after the first visit, and then again after six months, balances frequency with the relevance of a repeat relationship signal.
The channel multiplies the timing effect
Timing alone does not determine review request effectiveness. The channel through which the request arrives interacts with timing: a well-timed request in a low-completion channel loses much of its timing advantage.
SMS and app-based notifications have the highest open rates of any digital communication channel — consistently above 95% within minutes of delivery. This means that a well-timed SMS request reaches the customer during the window of willingness reliably. An email with the same timing may sit unread for hours.
The combination of right timing and right channel is multiplicative, not additive. A same-hour SMS request during the peak of satisfaction captures the customer's motivation at its highest point through the highest-completion channel. The result is a significantly higher review conversion rate than either factor alone would produce.
Avoiding timing mistakes
Asking too early: Sending a review request as the technician is packing up, before the customer has had a moment to absorb the completed result, can feel presumptuous. The customer is still in operational mode (signing paperwork, asking follow-up questions). A brief buffer — 15 to 30 minutes after job close — feels more natural.
Batching requests: Some businesses send weekly or monthly review request batches. This strategy loses most of the timing advantage. By the time a customer who had a great experience two weeks ago receives a review request, the motivation window has largely closed.
Asking multiple times: A customer who receives a review request, doesn't act on it, and then receives two more requests over the following week is being treated as a sales lead, not a satisfied customer. Single, well-timed requests outperform follow-up sequences for most service trades. If a follow-up is warranted, one is sufficient.
The operational implication
The practical implication of timing research is that review collection must be automated at the job-close event, not scheduled in a separate workflow. Any system that requires a human to remember to send a request after a job is complete will produce inconsistent timing and, therefore, inconsistent results.
The automation question is not complex: trigger a review request when a job is marked complete in the field management system, at the appropriate delay for the service type, through the highest-completion channel the customer has on file. Done consistently, this approach produces the highest possible review conversion rate from the customer base that already exists.