What is Customer Effort Score (CES)?
Customer Effort Score (CES) is a survey metric that measures how easy it was for a customer to get what they needed — an issue fixed, a question answered, a return arranged. The most widely used version, often called CES 2.0, asks customers how far they agree with "The company made it easy for me to handle my issue" on a 1–7 scale, from strongly disagree to strongly agree.
The idea behind CES is that reducing effort does more for loyalty than delighting customers. People remember having to repeat their order number to three agents, switch from WhatsApp to email to send a photo, or wait two days for a reply, and those moments push them away even if the problem was eventually solved. CES puts a number on that friction.
CES is often run next to the Customer Satisfaction Score (CSAT) and Net Promoter Score (NPS), and they answer different questions. CSAT asks whether the customer was satisfied with one interaction, NPS asks whether they would recommend the brand, and CES asks how hard it was. A chat can score well on CSAT ("the agent was lovely") and badly on CES ("it took three conversations"), which is exactly what makes it useful alongside first contact resolution.
Key takeaways
- Customer Effort Score (CES) asks how easy it was to resolve an issue, usually agreement with "The company made it easy to handle my issue".
- The common CES 2.0 format uses a 1–7 agreement scale; report the average, or the share of 5–7 answers.
- Effort is a strong churn signal: customers who had to work hard are less likely to stay, even when the issue was solved.
- CES measures ease, CSAT measures satisfaction with one interaction, and NPS measures loyalty to the brand.
Figure 1
How easy was it? Watch effort move the score
- Hard work1.0–3.0 agreement (1–7)
- Some friction3.0–5.0 agreement (1–7)
- Easy5.0–7.0 agreement (1–7)
Solved by self-service
6.5 agreement (1–7)
A WhatsApp Flow books the claim inspection in two minutes with no agent involved.
Solved by self-service: 6.5 agreement (1–7) — Easy zone. A WhatsApp Flow books the claim inspection in two minutes with no agent involved.
Why it matters
Why does Customer Effort Score (CES) matter?
Effort is the part of the experience a support team can most directly change: fewer transfers, fewer repeat questions, self-service that actually works, and answers on the channel the customer started in. Tracking CES by journey shows which processes create work for customers, and it gives operations teams a reason to fix tooling and policy, not only agent behaviour.
Example: Insurance claims in Ahmedabad
An Ahmedabad motor insurer surveys customers after claim-intimation chats on WhatsApp. CSAT is a healthy 84%, but CES averages only 4.1 out of 7. Reading the low scores shows why: customers are asked to email photos of the damage and RC book instead of sending them in the chat. The insurer accepts documents and photos directly in the WhatsApp thread and pre-fills the policy number from the CRM. Two months later CES averages 5.6, and fewer customers call the helpline to chase the claim.
How does Customer Effort Score (CES) work?
Pick the moment
Ask after a journey completes — an issue resolved, a return booked, an account change done — rather than after every message.
Ask one agreement question
Use "The company made it easy for me to handle my issue" on a 1–7 scale. On WhatsApp, a list message with seven rows fits in one tap.
Calculate consistently
Report either the average score or the share answering 5, 6 or 7. Choose one and keep it fixed so trends stay comparable.
Segment by journey and channel
Break CES down by tag, whether a bot or deflection path was involved, number of transfers and whether the issue was solved first time.
Fix the hardest journeys first
Read low-score conversations, find the step that caused effort — a channel switch, a document request, a repeat question — and remove it.
Common mistakes with Customer Effort Score (CES)
Mixing scales across surveys
A 1–5 CES in one journey and a 1–7 in another cannot be averaged. Standardise one scale for every CES survey.
Reversing the direction
Some older versions ask "How much effort did you put in?", where low is good. Mixing the two silently flips results; label the direction in every report.
Asking before the issue is resolved
CES after the first reply measures nothing useful. Trigger it when the journey is complete.
Blaming agents for process effort
Most effort comes from policy and tools — document requests, transfers, channel switches. Use CES to fix the process, not to rank agents.
CES FAQs
- What is the difference between CES and CSAT?
- CES measures how easy it was to resolve an issue; CSAT measures how satisfied the customer felt with the interaction. A friendly agent can earn good CSAT while a clumsy process still produces poor CES.
- How do you calculate Customer Effort Score?
- Average the answers on your agreement scale, or report the share of positive answers. On a 1–7 scale, 300 responses with 210 answering 5, 6 or 7 give 70% "easy".
- What is a good Customer Effort Score?
- There is no universal benchmark because scales and wording vary. Track the same question over time and by journey; a rising average or a rising share of 5–7 answers is the goal.
- Can I run a CES survey on WhatsApp?
- Yes. Send a list message with the scale as rows once the issue is resolved, inside the 24-hour window. In India that survey is a service message, charged per delivered message since 1 October 2026.
Best practices for Customer Effort Score (CES)
- Count transfers and channel switches per conversation; they track closely with low CES.
- Let customers send documents and photos in the WhatsApp thread instead of redirecting to email.
- Use a CRM integration so agents never ask for details you already hold.
- Ask CES and CSAT in different journeys rather than stacking two surveys on one customer.