What is the Customer Effort Score (CES)?
The Customer Effort Score (CES) measures how easy it was for customers to get something done: ask a question, return an item, set up an account. Customers say how far they agree that it was easy, on a scale from 1 to 7. Your CES is the percentage who gave a 6 or a 7.
Why measure effort?
The Customer Effort Score comes out of research by the Corporate Executive Board (CEB, now part of Gartner). In 2010, Matthew Dixon, Karen Freeman and Nick Toman wrote it up in the Harvard Business Review under a provocative title: Stop Trying to Delight Your Customers. Their argument: in customer service, you win loyalty less by surprising customers with extras than by making things easy for them. The idea that you must "delight" customers had, in the authors' view, become so entrenched that hardly anyone questioned it.
Anyone who has had to give their customer number three times, or ended a web chat only to have to phone anyway, knows the feeling. The outcome can be fine and the contact can still leave a bad taste. A satisfaction question sometimes misses that; a question about effort catches it exactly.
The CES question: two versions
The first version asked customers how much effort they personally had to put in to get their issue handled, on a scale where a low number meant little effort. That runs against intuition: on almost every other question, high is good.
In The Effortless Experience (2013) the researchers therefore set out a second version: a statement customers agree or disagree with, on a scale from 1 to 7. A widely used wording:
[Company] made it easy for me to handle my issue.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- Does not count 1–5
- Easy: counts towards CES 6–7
Adapt the end of the statement to the task you're measuring: to return my order, to book an appointment, to set up my account. The more specific it is, the more useful the result.
How to calculate CES
Again there are two methods. You can report the average score, or the percentage of customers who agree (or strongly agree) with the statement, that is, who gave a 6 or a 7. The percentage is easier to read and to compare:
A worked example
An online shop asks customers whether it was easy once they've completed a return. 120 customers respond:
| Score | Responses |
|---|---|
| 7, strongly agree | 30 |
| 6 | 36 |
| 5 | 22 |
| 4 | 12 |
| 3 | 9 |
| 2 | 6 |
| 1, strongly disagree | 5 |
| Total | 120 |
- CES as a percentage: 30 + 36 = 66 of 120 customers found it easy, so a CES of 55%.
- Average score: 628 ÷ 120 = 5.23 on a scale of 1 to 7.
The bottom end is worth a look here too: 20 customers (17%) gave a 3 or lower. What went wrong for them? That's where the improvements are.
When to use CES
CES suits tasks: moments when a customer wants to get something done. Think of:
- resolving a question or complaint with customer service;
- a return, a change or a cancellation;
- onboarding: creating an account, installing something, logging in for the first time;
- a form or application process on your website.
Ask straight after the task, and measure each task separately. An average CES across everything won't tell you which process is causing friction. For the overall relationship with a customer, NPS is the better fit; for satisfaction with the outcome, CSAT. NPS vs CSAT vs CES explains how they combine into a complete picture.
What is a good CES?
Because CES is measured per task, and different scales and methods are in use, there's no generally useful norm. A cancellation will rarely feel as smooth as a purchase. So compare:
- the same task over time, for example before and after you change your returns process;
- different channels for the same task, such as chat, phone and the online form;
- different steps in the customer journey, to see where most of the effort sits.
Pitfalls
Mixing versions. A CES on the old scale (low is good) and one on the new scale (high is good) can't be compared, and a report that puts them side by side will mislead its readers. Choose the statement version and stick with it.
A vague statement. "[Company] makes things easy for me" without a task measures a general feeling, not a process. Name the task.
Only measuring those who succeeded. Customers who gave up halfway had the most effort of all. Try to reach them too, for instance with a question after an abandoned application.
Measuring effort without asking what was hard. A low CES tells you something is grinding, not what. Was it the wait, being transferred, the form, having to repeat details?
After the score: ask what was hard
With CES the follow-up question matters even more than with other scores, because effort is so concrete. Customers can usually point to exactly where it went wrong: "I had to give my order number twice", "the form wouldn't accept my postcode". So ask: what made it difficult? or what would have made it easier?
How ScoreStory does it. ScoreStory measures CES with a statement on a 1 to 7 scale and shows the score as the percentage of participants who gave a 6 or a 7: the share who found it easy. Vox, the AI interviewer, then asks where the friction was and follows up on the exact moment. Answers are grouped into themes automatically. More on the product page.
Frequently asked questions
Is a high CES good or bad?
It depends on the version. In the current version, a statement such as 'the company made it easy for me' on a 1 to 7 scale, higher is better. The original version asked how much effort something took, and lower was better. So always say which scale you use.
What's the difference between CES and CSAT?
CSAT asks how satisfied someone is. CES asks how easy something was. A customer can be happy with the answer and still have had to work hard to get it, which is why the two complement each other well.
Can you use CES for employees?
Yes, it works just as well for internal processes: how easy was it to submit your expenses, request a laptop or get through your first week? Adapt the statement to the task.
Sources
- Stop Trying to Delight Your Customers, Matthew Dixon, Karen Freeman and Nick Toman, Harvard Business Review, July–August 2010
- The Effortless Experience: Conquering the New Battleground for Customer Loyalty, Matthew Dixon, Nick Toman and Rick DeLisi, Portfolio, 2013
Measure the score, then ask why
ScoreStory asks for one score and then holds a short conversation about the reasons behind it. Your first 10 interviews are free, with no credit card and no end date.