Customer Effort Score

Customer Effort Score asks one question: how much effort did you personally have to put in to handle your request? A customer rates the interaction — a support ticket, an onboarding step, a contract renewal — on a scale, usually 1 (very low effort) to 5 or 7 (very high effort). The insight behind CES, published by CEB in 2010, is blunt: customers don't reward companies for delighting them, they punish companies for wasting their time. A five-minute password reset that should have taken thirty seconds does more damage to retention than a five-star support call does good.

How Customer Effort Score Is Calculated

CES is reported as a mean score on the raw scale, or normalized into a percentage of "low effort" responses (top-two-box on a 7-point scale, meaning 1s and 2s). The formula for the percentage version:

CES % = (Number of low-effort responses ÷ Total responses) × 100

A company running the 7-point CEB scale and collecting 1,000 post-interaction surveys, with 640 customers marking 1 or 2, reports a CES of 64%. On the raw-mean version, if those same 1,000 respondents average 2.1 on the 7-point scale, that's the headline number — lower is better, which trips up people used to NPS and CSAT where higher is better.

Worked Example: Reading a CES Distribution

Top-two-box CES here is 64%. That sounds healthy until it's benchmarked: SaaS support teams median around 65–70% low-effort responses on well-run tickets, so this org is average, not exceptional — and the 18% sitting neutral is the group most likely to churn quietly, because "neutral effort" customers rarely bother leaving a review or a complaint before they leave the product.

When Sales and CS Teams Use Customer Effort Score

CES lives mostly with Customer Success and support leadership, but it shows up in two sales-adjacent places. First, renewal risk: a CSM walking into a quarterly business review with a customer whose last three CES responses were 5+ has a weaker hand than customer health score alone would suggest, because effort scores move before health scores do. Second, RevOps uses CES as a leading indicator feeding churn rate and renewal rate models — a rep or CSM whose accounts consistently post high-effort scores after implementation is a better predictor of a soft renewal than a satisfaction survey filled out once a year.

Common Customer Effort Score Gaming Patterns and Limitations

CES gets gamed at the point of collection. Support teams send the survey immediately after a ticket closes, while the resolution is still fresh and positive, and skip surveying tickets that got reopened three times or escalated to a manager — the hardest interactions, which would report the worst effort scores, never get measured. Reps and support agents also prime the response by literally asking "that was easy, right?" before triggering the survey link, which is a leading question dressed up as a courtesy.

The bigger limitation is scope: CES measures a single interaction, not the relationship. A customer can report "very low effort" on a support ticket and still churn six weeks later over pricing, a missing feature, or a competitor's better fit — none of which the CES question ever asked about. It also says nothing about why effort was high. A score of 5 could mean the product is confusing, the support agent was undertrained, or the customer had unreasonable expectations, and without qualitative follow-up, CES collapses three different problems into one number that looks precise and isn't.