metrics
Customer effort score (CES)
What is customer effort score, and why measure effort?
Customer effort score (CES) asks one thing after an interaction: how easy was it to get what you needed? Usually a single agree-scale statement ("the company made it easy to handle my issue"), it shifts the question from "are you delighted?" to "did we get out of your way?" - on the theory that reducing effort keeps people more reliably than trying to wow them.
Also known as: customer effort score, ces, effort score, ease of use score
Prefer to watch?
Watch the recap 0:53
The demo
Same idea as a satisfaction score, but pointed at the thing that actually drives people away: effort. Rate how easy the task was, and see what CES is really asking.
“The service made it easy to handle my issue.”
What this demo shows (text version)
A customer effort score question asks how much you agree that the service made it easy to handle your issue, on a 7-point scale from strongly disagree (it was hard) to strongly agree (it was easy). You pick a point, and the demo reframes what's being measured: not how delighted you are, but how much work the experience demanded of you.
CES exists because effort - extra steps, waiting, repeating yourself - is a stronger driver of churn than a lack of delight, especially for support and transactional tasks. So a low-effort score can be an earlier warning than a satisfaction figure. Like the other single-number metrics it's shallow: pair it with an open "what made it hard?", watch the trend, and triangulate with CSAT, NPS and behaviour. (Illustrative, not real data.)
CES measures ease, not delight - and for transactional, problem-solving moments (support, checkout, onboarding) ease often predicts loyalty better than satisfaction does, because high effort is what drives people away. It's a fast single-question pulse on "how hard did we make this?". Like CSAT and NPS it's shallow and needs a "why?" follow-up, and it fits effortful tasks, not the whole relationship.
Rate the effort and the score reframes the whole question: not "did you love it?" but "did we make you work for it?". High effort is the quiet churn driver - the extra step, the repeated explanation, the hunt for the button - so a low-effort score is often a better early-warning signal than a happy face.
CES exists because reducing effort tends to retain customers more reliably than delighting them does - especially in service and support, where people don't want a magical experience, they want their problem gone with minimum friction. So instead of measuring happiness, CES measures the work you imposed: the steps, the waiting, the repetition, the thinking.
It's at its best on specific, effortful, transactional moments - resolving a support issue, completing checkout, finishing onboarding - asked immediately after, while the effort is fresh. It's a poor fit for measuring an overall relationship or an experience where effort isn't the point (browsing for pleasure), where satisfaction or behavioural metrics serve better.
The cautions mirror the other one-number metrics. A single score tells you ease was high or low but not where the effort came from, so always pair it with an open "what made it hard?". Watch the trend rather than the absolute, and triangulate with CSAT, NPS, task success and drop-off. CES points to friction; the follow-up tells you where to cut it.