CES = the average rated effort required to complete an interaction
Typically a 1 to 7 agreement scale on a statement such as "the company made it easy for me to handle my issue".
Why effort rather than satisfaction
The argument behind CES is that reducing friction retains customers more reliably than exceeding expectations does. Customers rarely leave because nobody delighted them; they leave because something was repeatedly hard.
That makes CES a more actionable signal than CSAT for support and onboarding, because effort points at a specific process step and satisfaction points at a mood.
The scale direction trap
Two conventions exist and they are opposites:
- Agreement with "made it easy": high is good.
- Rated effort required: high is bad.
Teams switch between them, sometimes inside one dashboard, and the series inverts without anyone noticing. Write down which one you use and state the direction on every chart.
Where to ask
CES is a transaction measure like CSAT, so ask immediately after the interaction. It works best on:
- Support resolution.
- Onboarding milestones.
- Self-service tasks, where effort is the entire experience.
It works badly as a relationship measure. For that use behaviour: retention rate or a validated health score.
The follow-up is the value
As with CSAT and NPS, the number tracks a trend and the verbatim says what to fix. A high-effort score with the comment "I had to explain the problem three times" names a routing problem that no aggregate score would surface.
The traps
- Inverting the scale direction between periods.
- Using it as a relationship or churn measure.
- Publishing without the response rate.
- Comparing to external benchmarks across different scales.
Where this sits
CES is Measurement in the Tenbound Pipeline Architecture Standard, and it is a support and onboarding diagnostic rather than a revenue metric. Its practical value is that it points at a step rather than at a feeling.