Customer satisfaction metrics: measuring recovery, not operations

What customer satisfaction metrics measure

Customer satisfaction metrics quantify how customers feel about their experience with you. The standard set is CSAT, which asks how satisfied someone was with a specific interaction, NPS, which asks how likely they are to recommend you, and CES, which asks how much effort the interaction cost them. Support teams add operational measures like first response time and resolution time.

They are useful and you should track them. The caution is that in e-commerce they mostly measure the quality of your recovery, not the quality of your operation.

Every order is a promise. Keeyu keeps the promise. Satisfaction metrics tell you how people felt about how you handled a promise you already broke.

The survivorship problem

CSAT is typically triggered by a support interaction. That means it samples customers who contacted you, and it scores the conversation rather than the underlying event.

An agent who responds in four minutes, apologizes well and refunds promptly will score highly on a ticket that exists only because an order never left the warehouse. The score says the recovery was good. It says nothing about the fact that the order failed.

Taken to the extreme, a team can improve CSAT quarter after quarter while the operation gets worse, because they are getting better at apologizing to more people.

The customers who never appear

The larger gap is the people who never contact you. Some share of customers who have a bad experience simply do not come back and never file a ticket or a survey. They are invisible to every satisfaction metric you run.

At Papinelle I found complaint tickets running at 110% of order volume, essentially all about orders. That was the visible portion. Nothing in the satisfaction reporting captured the customers who had the same experience and quietly stopped buying.

The operational counters worth adding

Put these next to CSAT, because they measure the event rather than the conversation:

• Exception rate: share of orders that hit an operational break
• Customer-detected rate: share of those the customer discovered before you did
• Time to detection: how long a break sits before anything notices
• Time to resolution from the break, not from the ticket
• Unresolved returns: received but not refunded inside your promised window

Customer-detected rate is the one I would put on the wall. It is a direct measure of whether you are running proactively or reactively, and it cannot be improved by getting better at apologizing.

What moves when the operation holds

At EHP Labs, proactive detection cut reactive tickets 55% and resolution time from 45 minutes to 5, alongside 116% net revenue retention and zero churn over 18 months. The satisfaction scores followed, but the causal chain ran through fewer broken orders rather than better replies.

If your CSAT is strong and your repeat purchase rate is weak, you are probably measuring recovery quality on an operation that is failing more than you think.

Where this sits

This is proactive e-commerce operations: detect the break across store, warehouse and carrier, decide the remedy, act before the customer feels it. Detect. Decide. Act. The customer gets what they want, on time, as promised, and never has to rate how well you said sorry.

See how our customers run this or book a demo.

Related reading

For the experience layer, read customer experience management. For retention, see customer retention strategies. For the operational picture, read post-purchase operations.