Customer Effort Score (CES): Formula, Scale, and When to Use It
What Is Customer Effort Score?
Customer Effort Score (CES) is a survey metric that measures how much effort a customer had to put into an interaction with your company, resolving a support issue, completing a purchase, setting up an account. The standard CES question asks respondents to rate their agreement with a statement like "[Company] made it easy for me to handle my issue" on a 7-point scale from "Strongly Disagree" to "Strongly Agree." The Corporate Executive Board (now Gartner) introduced CES in 2010 based on research showing that reducing effort is a stronger predictor of loyalty than exceeding expectations. Their finding was counterintuitive at the time: delighting customers doesn't build loyalty nearly as much as simply making things easy.
Why CES Matters
The research behind CES found that 96% of customers who have high-effort experiences report being disloyal, compared to only 9% of those with low-effort experiences. Effort drives disloyalty more reliably than satisfaction drives loyalty. That's because negative experiences, being transferred between departments, having to repeat information, needing multiple contacts to resolve an issue, stick in memory and erode trust. CES captures this dimension directly, making it the best metric for identifying friction in customer-facing processes.
How CES Works
The 7-Point Scale
The current version of CES (CES 2.0) uses an agreement-based format:
Statement: "[Company] made it easy for me to [complete specific action]."
| Value | Label |
|---|---|
| 1 | Strongly Disagree |
| 2 | Disagree |
| 3 | Somewhat Disagree |
| 4 | Neither Agree Nor Disagree |
| 5 | Somewhat Agree |
| 6 | Agree |
| 7 | Strongly Agree |
Higher scores mean lower effort (the company made it easy). This positive framing is deliberate, it avoids the double-negative confusion of asking "how much effort did you have to put in?" where a high number means a bad experience.
The Formula
CES = Sum of all scores / Number of responses
If 150 respondents give scores totaling 855, your CES is 855 / 150 = 5.7 out of 7.
Some teams also report CES as the percentage of respondents who selected 5, 6, or 7 (the "easy" group), similar to top-two-box scoring in CSAT. Either approach works, pick one and stay consistent.
Practical Example
An insurance company redesigns its claims filing process and wants to measure whether the new flow is easier. After each completed claim, customers see:
"Acme Insurance made it easy for me to file my claim." Strongly Disagree (1). Strongly Agree (7)
Month one results (new flow): average CES of 5.8, with 78% scoring 5-7. Baseline (old flow): average CES of 4.1, with 42% scoring 5-7.
The redesign nearly doubled the percentage of customers who found the process easy. That's the kind of operational signal CES is built for.
CES vs. NPS vs. CSAT
| Metric | Measures | Best For | Timing |
|---|---|---|---|
| CES | Ease of interaction | Process optimization | Immediately after an interaction |
| CSAT | Satisfaction with experience | Touchpoint quality | Immediately after an interaction |
| NPS | Loyalty / willingness to recommend | Overall relationship health | Quarterly or after key milestones |
CES and CSAT are both transactional metrics, but they answer different questions. A customer can be satisfied (high CSAT) but still feel the process required too much effort (low CES). The support agent was friendly and resolved the issue, but the customer had to call three times to get there. CES catches what CSAT misses.
When to Use CES
- After support interactions: the original and highest-value use case; measures whether resolution was easy
- After self-service experiences: did customers successfully find answers in your knowledge base or had to escalate?
- Post-onboarding: how much effort did it take to get set up and productive?
- After checkout or purchase: identifies friction in the conversion flow
- Following process changes: before/after CES comparison shows whether a redesign actually reduced effort
Common Mistakes
- Using the original CES 1.0 wording: the first version asked "How much effort did you have to put forth?" on a 1-5 scale, but the flipped polarity confused respondents; use the CES 2.0 agreement format instead
- Deploying CES as a relationship metric: CES is designed for specific interactions; don't send it quarterly to your whole customer base (use NPS for that)
- Ignoring the open-ended follow-up: the score tells you effort was high, but not why; always ask "What would have made this easier?" for scores of 1-4
- Measuring effort for the wrong interactions: CES works best for processes where effort varies; asking it after a simple page visit adds noise without signal
- Averaging across wildly different channels: phone, chat, and self-service have fundamentally different effort baselines; segment your CES by channel to get useful data
How Quali-Fi Supports CES
Quali-Fi offers a pre-built CES question type with the 7-point agreement scale, automatic scoring, and the option to trigger an open-ended follow-up for low scores using skip logic. The platform calculates both the average CES and the percentage of "easy" responses (5-7) in real-time dashboards. You can segment CES by channel, agent, product, or any custom field to pinpoint exactly where effort is highest.
Start measuring CES with Quali-Fi →
FAQs
What's a good CES score?
On a 7-point scale, a CES of 5.5 or higher is generally considered good. Above 6.0 is excellent. But the absolute number matters less than the trend, a half-point decline over a quarter signals a process problem regardless of where you started.
Should I use CES or CSAT for support interactions?
Both, ideally. CSAT tells you whether the customer is satisfied with the outcome. CES tells you whether the process was easy. A customer can be satisfied with the resolution but frustrated by the effort required to get there. Together they give a complete picture.
How is CES calculated differently from the original version?
CES 1.0 (2010) asked "How much effort did you personally have to put forth?" on a 1-5 scale where 5 meant highest effort. CES 2.0 flips the framing to "[Company] made it easy..." on a 1-7 scale where 7 is best. The positive framing reduces confusion and correlates better with behavioral outcomes.
How many responses do I need?
For a stable CES average, aim for at least 100 responses per segment. If you're comparing CES across three support channels, you need roughly 100 responses per channel to draw meaningful conclusions.