Customer effort score: a better question than satisfaction

Aug 22
3 min read

Updated: 5 days ago

Introduction

Satisfaction surveys tend to produce agreeable numbers and no information. Almost everyone answers somewhere between fine and good, and the score barely moves regardless of what you change.

Asking about effort behaves differently. It produces variation, and the variation points at something specific you can fix.

1. Customer effort score measures how hard you were to deal with

The question is roughly: how easy was it to get what you needed from us? Usually a scale of one to five or one to seven, from very difficult to very easy.

It works because customers are poor judges of quality — they lack the comparison — and excellent judges of inconvenience. They remember waiting, repeating themselves, chasing, and being passed around.

Effort also correlates better with whether someone comes back than satisfaction does. People forgive an imperfect outcome and rarely forgive a difficult process.

2. Ask it after a specific interaction, not about the relationship

This is a transactional measure and it breaks when used as a general one.

Send it after a defined event: an enquiry handled, an order delivered, a problem resolved, a question answered. Ask about that interaction only.

"How easy was it to deal with us this year" produces an averaged impression. "How easy was it to get your issue resolved" produces a number you can attach to a process.

3. Word it about their experience, not your performance

The phrasing determines whether people answer honestly.

Ask how much effort it took them, rather than how well you did. Customers are reluctant to criticise people and quite willing to report that something was inconvenient.

Keep it to one question and one optional comment box. Anything longer converts a two-second reply into a task.

4. Send it immediately, through the channel they used

Effort is remembered accurately for a short time and then smooths over.

Send within hours of the interaction closing, in the same channel it happened in. A reply in the existing message thread will always outperform an email inviting someone to a survey page.

Also keep it to one question visible without opening anything. Each additional click removes a proportion of respondents, and the ones who persist are systematically different from the ones who do not.

5. The comment box is where the value is

The score tells you there is a problem. The comments tell you what it is.

Almost every low score comes with a specific, concrete complaint: had to explain it three times, nobody replied for two days, the form did not work, was transferred twice, could not find the price.

These are process defects, individually cheap to fix. The number is only useful as a way of finding the comments worth reading.

6. Act on the low scores individually and quickly

A low score is an early warning about a specific customer, and it arrives while the relationship can still be repaired.

Have someone read low scores within a day and respond personally. A customer who reported difficulty and then received a call is frequently more loyal afterwards than one who had no problem at all.

That requires a named owner and a threshold — which scores trigger contact — decided before you start collecting.

7. Group the results by process, not by person

The instinct is to look at scores by employee. It is usually the wrong cut and it makes staff defensive.

Group by process instead: enquiries, deliveries, complaints, returns, bookings. The pattern almost always sits in a process — a handover with no owner, a step requiring information you already hold, a system that logs people out.

Fixing the process helps every customer. Coaching the individual who happened to be staffing a broken process does not.

8. Track the trend and keep the sample honest

The absolute number is not meaningful in isolation, and comparisons across industries are worthless.

Track your own figure over time for the same interaction type, and watch it after each process change. That is the only comparison with any information in it.

Also watch the response rate. If it drops, the number is drifting toward whoever is most motivated to answer, which is usually people who had an extreme experience in either direction.

Conclusion

Ask how much effort the customer had to expend, about one specific interaction, immediately afterwards, in the channel they were already using.

Treat the score as a way to surface the comments, respond personally to low scores within a day against a defined threshold, group findings by process rather than by employee, and judge progress on your own trend for the same interaction type while watching the response rate.