What the peak-end rule says
The peak-end rule describes how people look back on an experience: they judge it largely by its most intense moment and by how it ended, rather than by adding up every minute. Kahneman, Fredrickson, Schreiber and Redelmeier reported the pattern, and Redelmeier and Kahneman found it again in patients' memories of medical procedures. In both, people paid little attention to how long the experience lasted, which researchers call duration neglect.
Be clear about what that evidence covers. The studies measured how people remember discomfort, not how they rate a plumber, a clinic or an accountant. Applying the rule to customer service is a sensible extension rather than a tested law, so use it to decide where to put your effort and then check the results against what customers actually do.
The first peak: how you answer an enquiry
For a new customer, the enquiry is often the first moment that carries real feeling. They have a problem, they have reached out, and now they wait. A prompt, personal reply that answers their actual question and says what happens next can become an early high point. Silence, an auto-reply that promises nothing, or a request to type the same details again can become the first low.
Write down what happens today when a form arrives at four on a Friday afternoon. Who sees it, how soon, and what does the customer receive? A CRM can route each enquiry to a named person, raise a reminder if nobody has replied, and send a confirmation that sets a clear expectation, such as a call the next business day, which your team then keeps.
Onboarding and delivery: plan the high, remove the low
Once someone says yes, map the steps they go through: paperwork, payment, the first meeting, the work itself, progress updates and handover. Ask two questions about each step. Where could this feel noticeably good? Where does it tend to feel bad? The low points are usually ordinary ones: waiting without news, a surprise charge, or having to chase you for an update.
Fix the low point first. In the original studies the peak that counted was a painful one, so a single bad moment can be the one a customer carries away. Then design one deliberate high point that suits your work, such as a walkthrough of the finished job, a clear before-and-after, or a welcome pack that answers questions people are too polite to ask.
- Days with no reply and no update
- Charges the customer did not expect
- Repeating details already given to someone else
- A handover with no word on what to do next
End well: the last step of working together
Endings are easy to neglect, because by then the team has moved on to the next job. The final invoice arrives without context, files are sent in a rush, and nobody checks that the customer knows how to use what they paid for. Under the peak-end rule, that rushed finish carries extra weight in how the whole job is remembered.
Plan the ending as carefully as the start. Send a short summary of what was done and what changed, include next steps or care instructions, and make the invoice match the quote with no surprises. A check-in email a week or two later, asking whether everything works, closes the loop. That is also a fair moment to ask for a review, which our guide to getting more Google reviews covers in detail.
Where the peak-end rule backfires, and what to try
The rule is easy to misuse. A thank-you gift at the end does not make up for a project that ran late with no explanation, and a warm ending laid over a cold middle can feel hollow. Duration neglect is no excuse for slow service either, because a long wait can become a low point of its own. Use the rule to finish well, not to hide problems.
Measure the effect through what customers do next: repeat bookings, referrals, reviews and replies to your follow-up emails. A simple journey map in your CRM, with the moments you want to improve marked, keeps the work honest. The growth check can show which stage of your customer journey needs attention first, and our email marketing for small business guide covers the follow-up emails themselves.
- Send a test enquiry to your own business and time the reply
- Ask your last five customers which moment stood out, good or bad
- Fix one low point before adding any extras
- Write an end-of-project email with a summary and next steps
- Set a CRM reminder to check in after every finished job
Where customer experience is heading
Reviews, follow-up emails and CRM records now capture more of each customer journey, which makes the peaks and the endings easier to see and harder to hide. Small teams can use that record to spot the moments that keep going wrong and fix them before they turn into a pattern. Businesses that plan their endings on purpose should find repeat work and referrals easier to earn.
- 01CRM alerts that flag a slow reply before the customer has to chase
- 02Automated check-ins after each job, written in a human voice
- 03Review requests timed to the end of the work, not sent at random
Questions & answers
People remember an experience largely by its peak, pleasant or not, and by how it ended, not by the average of every moment. A single bad moment or a rushed ending can therefore colour how a whole job is remembered, while a strong, well-planned finish can leave a good last impression.
No. The middle is where many peaks happen, for better or worse, and a long stretch of poor service still creates low points. The rule tells you where memory puts extra weight. It is not a map of where you can safely cut corners.
Ask recent customers what stood out, read your reviews and complaints for repeated themes, and walk through your own process the way a customer would. Delays without updates, unexpected costs and repeated paperwork come up often. Fix the complaint that keeps coming back before adding anything new.
The findings come from careful studies by Kahneman, Redelmeier and colleagues, but those studies looked at uncomfortable experiences, not purchases. Using the rule in business is a reasonable extension, so test it against repeat bookings, referrals and reviews rather than treating it as a law.
