CES: what it is and how to calculate it
Customer Effort Score shows how easy it was for customers to get something done with you: solve a problem, return a product, find an answer. Here is the formula, a calculator, sample questions and how to remove friction.
CES is the share of customers who agree that you made it easy to handle their request: answers of 5, 6 or 7 on a 1–7 agreement scale.
At a glance
Customer Effort Score measures how much effort customers had to put in to get something done. In its current form customers rate a statement such as “The company made it easy for me to handle my issue” on a scale from 1 (strongly disagree) to 7 (strongly agree). The score is the percentage who agree.
The metric was introduced in 2010 by the Corporate Executive Board (CEB, now part of Gartner) in the Harvard Business Review article “Stop Trying to Delight Your Customers”. Its research found that, in service interactions, reducing effort was more closely linked to loyalty than exceeding expectations. An updated version, CES 2.0, followed in 2013.
CES = (Responses of 5–7 ÷ Total responses) × 100
- Count every response to the CES statement.
- Count the responses that agree: every 5, 6 and 7.
- Divide the agree responses by the total.
- Multiply by 100 to get a percentage.
Enter the number of responses for each answer. The score updates as you type.
The original question was hard to read consistently: some customers misread which end of the scale meant “good”. CES 2.0 replaced it with an agreement statement, and that is the version most teams use today.
| Aspect | CES 1.0 | CES 2.0 |
|---|---|---|
| Introduced | 2010 | 2013 |
| Question | How much effort did you personally have to put forth to handle your request? | [Company] made it easy for me to handle my issue. |
| Scale | 1–5, very low effort to very high effort | 1–7, strongly disagree to strongly agree |
| Better score | Lower | Higher |
| Status today | Largely replaced | The standard version |
- measure service, support and self-service interactions
- find friction in processes such as returns, claims or onboarding
- compare channels: phone, chat, email, app and web
- check whether a process change really made things easier
- understand loyalty over the whole relationship: NPS
- measure overall satisfaction with an experience: CSAT
- measure how employees feel about the workplace: eNPS
- decide which of many improvements matters most: MaxDiff
- check each step of a process against a standard: Mystery shopping
[Company] made it easy for me to handle my issue.
[Company] made it easy for me to resolve my issue today.
The website made it easy for me to [task].
What, if anything, made this harder than it should have been?
A good CES depends on the task and the channel: renewing a subscription should feel easier than filing an insurance claim. The most useful comparison is your own trend and the gap between channels and processes that serve the same need.
Watch the neutral answers too. A large share of 4s usually means the experience was neither easy nor clearly hard, and the comments will show what slowed people down. If you use an external benchmark, check its date, sample, scale and whether it uses CES 1.0 or 2.0.
The score says how many customers struggled; the comments say where. Tag each mention of a step, form, wait or hand-off so the friction points become visible.
Contact customers who answered 1 to 3, solve what is still open and tell them what changed. High-effort experiences are the ones most likely to drive customers away. See the closing-the-loop guide.
Customers who have to call back, repeat their story or move from the website to the phone report much higher effort. Fix the first-contact gaps that cause the most repeats.
With CES 2.0 (the agreement statement on a 1–7 scale), higher is better: more customers agree it was easy. With the original CES 1.0 question, lower was better. Always state which version you use.