Customer Effort Score (CES) explained
CES measures how much work a customer had to do to get their issue resolved. It is a stronger predictor of repeat contacts and churn than CSAT — and therefore a more directly operational metric for contact centre management. Reducing effort reduces callbacks, which reduces volume, which reduces headcount.
The CES question and scale
Standard CES question (CEB/Gartner formulation)
“The company made it easy for me to handle my issue.”
Strongly disagree
Neutral
Strongly agree
How to report CES
Option 1: Average score (1–7). Higher = lower effort. Target: 5.5+
Option 2: % high effort (scores 1–3). Lower is better. Target: below 15%
Consistent scale definition
Some operations use “How much effort did you have to put in?” on a 1–5 low-to-high scale (reverse direction). Define clearly and hold constant. Mixing directional conventions breaks trend analysis.
CES vs. CSAT vs. NPS — when to use each
What drives high effort in contact centres
Channel switching
The single biggest effort driver: starting on web, being redirected to chat, then transferred to voice, then asked to call back. Each transfer resets the customer's context — they must re-explain the issue. Operations with high channel-switching rates consistently produce CES scores in the 2–3 range.
Repeat contacts for the same issue
Customers who contact twice about the same problem report significantly higher effort than first-contact resolvers — even if the second interaction itself was smooth. FCR failure is a direct CES failure. The first call experience creates a negative effort expectation that colours the second.
IVR friction
Complex IVR menus, irrelevant options, and misrouting add effort before the agent even connects. A customer who navigates 4 IVR levels and still speaks to the wrong team has a very high effort experience even if the eventual resolution is good. Max 4–5 IVR options per level; most-common options first.
Repetition of information
Being asked to repeat account details, order numbers, or the reason for calling to multiple agents is one of the most consistently cited high-effort experiences. Screen-pops from CRM, agent handover notes, and call recording briefing before transfer directly reduce this.
Wait time (perceived vs. actual)
Customers tolerate wait time better when they know it will end: position-in-queue announcements, estimated wait times, and callback offers all reduce perceived effort even with identical actual wait times. The effort is in the uncertainty, not the time itself.
Process complexity
Having to send a document, visit a branch, wait for a letter, or perform multiple steps outside the contact itself all add effort. Process redesign that completes resolution within the contact reduces CES — regardless of how the agent performed.
How CES improvement affects contact volume and staffing
Worked example: 10,000 contacts/month, CES improvement scenario
68%
Current FCR
32% of contacts are repeat callers
3,200/month
Repeat contacts
0.32 × 10,000
−1,200/month
After FCR to 80%
1,200 fewer contacts to handle
A 12-point FCR improvement (68%→80%) eliminates ~1,200 repeat contacts per month. At 5-minute AHT, that is 6,000 agent-minutes = 100 agent-hours per month saved. At 85% occupancy and 160 productive hours per agent per month, that is approximately 0.7 FTE equivalent — or enables the same team to absorb additional new volume without additional headcount.
CES questions
What is the Customer Effort Score (CES)?
CES measures how much effort a customer had to expend to resolve their issue. Typically measured on a 1–7 scale where 7 = strongly agree that the company made it easy. Developed by CEB (now Gartner) and shown to be the strongest predictor of repeat contacts and churn in contact centre interactions.
What is a good Customer Effort Score for a contact centre?
On a 1–7 scale: 5.5+ is strong. As a % high-effort (scores 1–3): below 15% is best-in-class; above 35% indicates systemic problems. Benchmark by contact type — transactional contacts typically score higher (easier) than complaint or technical contacts.
Why does CES predict repeat contacts better than CSAT?
Because effort is the primary driver of callback behaviour. A customer who resolved their issue with difficulty is likely to contact again — they may not have received a genuinely complete resolution. CSAT can be high even for incomplete resolutions (an empathetic agent produces good CSAT while leaving the issue unresolved). CES captures resolution completeness and ease more directly.
How does reducing customer effort affect contact centre staffing?
Reducing effort reduces repeat contact volume. A 10-point FCR improvement eliminates approximately 10% of total contacts. Under Erlang C, this reduces agent headcount requirement by roughly 7–9% (non-linear). IVR effort reduction increases containment, deflecting contacts entirely — each additional containment percentage point reduces agent volume proportionally.
Related guides
CSAT explained
CSAT and CES compared
First call resolution (FCR)
FCR as the operational CES driver
Self-service deflection
IVR design and effort reduction
CC metrics guide
Full metrics reference
FCR impact calculator
Model headcount saving from FCR improvement
Quality management
QA focus areas for effort reduction