Zurück
Customer Effort Score (CES): Formula, Questions, Examples

Matthieu Saussaye

Customer Effort Score (CES) is a survey metric that measures how easy it was for a customer to get something done with your company, such as resolving an issue, completing a purchase or setting up a product. It is usually one question asked right after the interaction, answered on a 1-7 agreement scale: "The company made it easy for me to handle my issue."
The essentials:
What it measures: friction in a specific task, not overall loyalty or satisfaction.
When to ask: immediately after a touchpoint (support chat, checkout, onboarding step, returns).
How to score: average rating, percentage who agree (5-7 on a 7-point scale), or a "net easy" score (easy minus difficult).
Why teams use it: effort is concrete and fixable. A high-effort score points at a specific process.
What it misses: on its own, why the task was hard. Always pair it with an open follow-up question.
CES is one of three core CX metrics alongside CSAT and NPS. Our overview of customer satisfaction metrics compares them briefly; this guide covers CES in depth.
CES vs CSAT vs NPS
The three metrics answer different questions and belong at different moments of the relationship.
Metric | Question | Scale | Measures | Best moment to ask |
|---|---|---|---|---|
CES | "[Company] made it easy for me to handle my issue." | 1-7 agreement (or 1-5) | Effort in a specific task | Right after a support contact, purchase or setup step |
CSAT | "How satisfied were you with [interaction]?" | 1-5 or 1-7 satisfaction | Satisfaction with an interaction or product | After a transaction or delivery |
NPS | "How likely are you to recommend [company] to a friend or colleague?" | 0-10 | Overall relationship and advocacy | Periodically (quarterly, after milestones) |
A practical split: use NPS to track the relationship (see our Net Promoter Score guide), CSAT to grade an interaction, and CES to locate the friction inside the processes that drive both.
Where CES comes from
The metric was introduced by the Corporate Executive Board, now part of Gartner. Its research was published in Harvard Business Review in July 2010 as "Stop Trying to Delight Your Customers" by Matthew Dixon, Karen Freeman and Nick Toman. The argument: in customer service, going above and beyond does less for loyalty than removing the hassle that makes customers work hard to get help. Today the most widely used wording is the agreement statement "The company made it easy for me to handle my issue" on a 1-7 scale, as described in Fin's CES glossary.
Customer effort score survey questions
Pick one main CES question and keep it identical everywhere you use it, so scores are comparable across channels. Here are wordings grouped by touchpoint.
Customer support
"[Company] made it easy for me to handle my issue." (1 Strongly disagree - 7 Strongly agree)
"How easy was it to get your issue resolved today?" (1 Very difficult - 7 Very easy)
"How many times did you have to contact us about this issue?" (1 / 2 / 3+), a behavioral effort check
Purchase and checkout
"It was easy to find the product I was looking for."
"Completing my purchase was easy."
"How easy was it to choose the right plan for you?"
Onboarding and product use
"Setting up [product] was easy."
"How easy was it to [complete key task] the first time?"
"I could find what I needed without asking for help."
Returns, billing and account changes
"Returning my order was easy."
"Updating my payment details was easy."
"Cancelling or changing my plan was straightforward."
Follow-up questions (always add one)
"What made it [easy / difficult]?" (open)
"What is one thing we could have done to make this easier?" (open)
"Which step took the most effort?" (list of steps from your process, plus "Other")
The open follow-up is where the actionable detail lives. See our guide to open-ended questions for how to phrase it without leading.
How to calculate customer effort score
There is no single standard formula. These three methods are common; choose one and state it whenever you report CES.
Method | Formula | Example (100 responses, illustrative) | Result | Pros / cons |
|---|---|---|---|---|
Average | Sum of ratings / number of responses | Ratings sum to 540 | 5.4 out of 7 | Simple, sensitive to small shifts; harder to explain to non-researchers |
% easy (top-3-box) | Responses of 5, 6 or 7 / total × 100 | 68 respondents chose 5-7 | 68% | Easy to communicate; ignores movement within the scale |
Net easy | % easy (5-7) minus % difficult (1-3) | 68% easy, 14% difficult | +54 | Mirrors NPS logic; neutral 4s drop out |
Worked example
An illustrative distribution of 200 responses on a 1-7 scale: 1 = 6, 2 = 8, 3 = 16, 4 = 30, 5 = 40, 6 = 54, 7 = 46.
Average: (6×1 + 8×2 + 16×3 + 30×4 + 40×5 + 54×6 + 46×7) / 200 = 1,036 / 200 = 5.18
% easy: (40 + 54 + 46) / 200 = 70%
% difficult: (6 + 8 + 16) / 200 = 15%
Net easy: 70 − 15 = +55
What is a good CES?
Be wary of universal benchmarks. Scales, wordings and calculation methods differ between companies, so a "5.5" from one firm is not comparable with a "5.5" from another. The useful benchmarks are internal: the same question, same scale and same method across channels, teams and time. Track the share of "difficult" answers (1-3) as closely as the average; that tail is where churn risk concentrates.
Choosing a CES scale
Scale | Labels | Good for | Watch out for |
|---|---|---|---|
1-7 agreement | Strongly disagree to Strongly agree | Most common in support research; enough points to show movement | Needs all points or at least endpoints labelled |
1-5 ease | Very difficult to Very easy | Short in-app prompts and mobile screens | Less room to detect small improvements |
3-point or emoji | Difficult / Neutral / Easy | Very high-volume, low-attention moments (kiosks, chat close) | Coarse; hard to track trends |
Whatever you choose, keep the direction consistent (higher = easier) and label the endpoints. Mixing directions across surveys is a common source of misread dashboards. Our Likert scale guide covers labelling and point counts in more detail.
Pros and cons of CES
Pro: actionable. A low score maps to a specific process you control.
Pro: short. One question plus one follow-up keeps response rates up at transactional moments.
Pro: early warning. Rising effort in one channel shows up before it reaches relationship metrics.
Con: narrow. It says nothing about price, product quality or brand.
Con: not standardized. Benchmarks across companies are unreliable.
Con: silent on causes unless you ask and analyze the open follow-up.
When to send a CES survey
Immediately after the interaction while the experience is fresh: in-app after a task, in the chat window at close, or by email within hours.
Once per interaction, not per message. Throttle so the same customer is not asked repeatedly in a week.
At process milestones: after onboarding is completed, after the first invoice, after a return is refunded.
Not for the overall relationship. "How easy is it to do business with us?" blends many touchpoints and is hard to act on.
How to act on CES results
Segment by touchpoint and channel. A company average hides the one process that is broken. Compare chat vs phone vs email, and each self-service flow.
Read the difficult tail. Pull every 1-3 response and its open comment.
Code the reasons. Group open answers into themes ("had to repeat information", "transferred", "could not find the option", "waiting for a callback"). Counting themes turns comments into a prioritized fix list.
Link to behavior. Join CES to repeat contacts, refunds or churn to see which effort drivers cost the most.
Fix and re-measure. Change one process, keep the question identical, and compare before and after on the same touchpoint.
Common CES mistakes
Mistake | Why it hurts | Better approach |
|---|---|---|
Changing scale or wording between channels | Scores cannot be compared | One wording, one scale, one formula everywhere |
Asking days later | Customers misremember effort | Ask within minutes or hours |
No open question | You know it was hard, not why | Add "What made it difficult?" after low scores |
Reporting only the average | Masks a growing group of very frustrated customers | Report % difficult alongside the mean |
Using CES as a loyalty metric | It measures a task, not the relationship | Pair with NPS or retention |
Turn effort scores into a fix list
A CES number tells you where effort is high. The reason sits in the comment box, which most customers leave short or empty. SmartInterview asks the CES question and then follows up with AI on vague or low-score answers ("Which step was hard?", "What happened next?"), by voice or text, in the customer's language. Answers are coded into effort themes automatically, so you can see which friction points come up most often in each channel.
Set up a CES survey for one touchpoint and see what customers actually struggled with. Start free.
Frequently Asked Questions
What is a customer effort score?
Customer effort score is a metric that measures how easy it was for a customer to complete a task or resolve an issue with your company. It is usually based on one question after the interaction, rated on a 1-7 agreement scale.
How do you calculate customer effort score?
The most common method is the average of all ratings. Other teams report the percentage of respondents who chose 5, 6 or 7 on a 7-point scale, or a net easy score: the percentage who found it easy minus the percentage who found it difficult.
What is a good customer effort score?
There is no reliable universal benchmark, because companies use different scales, wordings and formulas. Compare your score with your own past results on the same touchpoint, and aim to shrink the share of customers answering 1-3.
What is the CES question?
The widely used wording is "The company made it easy for me to handle my issue," answered from 1 (strongly disagree) to 7 (strongly agree). Alternatives include "How easy was it to resolve your issue today?" on a very difficult to very easy scale.
What is the difference between CES and CSAT?
CES measures how much effort a task took; CSAT measures how satisfied the customer was. A customer can be satisfied with a friendly agent yet still report high effort because they had to call three times.
Is a high or low customer effort score good?
On the standard agreement scale, a high score is good, because it means customers agreed the task was easy. Some teams instead ask how much effort was required, where a low score is good, so always check the scale direction.
When should you send a CES survey?
Right after the interaction you want to measure, such as when a support ticket is closed, a purchase is completed or an onboarding step is done. Delays weaken recall and lower response rates.


