How to run it
Ask one question, keep the scale fixed, and send it fast.
- Trigger the survey within 24 hours of a resolved interaction. - Use a seven point agreement scale on a statement about how easy the company made it to handle the issue. - Report top two box percentage as the headline and keep the raw distribution available. - Segment by interaction type, since onboarding effort and support effort have different causes and different owners.
Never edit the wording once it is live. A rephrased question produces a different number, and the trend line that made the metric useful disappears with it.
CES against the other two scores
| Metric | Question it answers | Best use |
|---|---|---|
| CES | How hard was this to get done | Fixing process friction after a specific interaction |
| CSAT | Was the customer happy with that interaction | Coaching individuals and measuring service quality |
| NPS | Would they recommend the company | Tracking relationship strength at the account level |
Reading it without overreacting
A single high-effort response is one bad afternoon. The signal lives in the pattern, specifically in repeated high-effort responses from the same account or the same workflow. Those two cuts point at different fixes. Repeated friction in one account is a relationship problem. Repeated friction in one workflow across many accounts is a product problem, and no amount of customer success attention will resolve it.
Response rate deserves its own attention. Falling response rates on a previously engaged account are a disengagement signal in their own right, which matches ORM's reading of deal risk, where the earliest warning is the absence of a signal rather than a negative one.
Where it fits in retention forecasting
CES works as a modifier in an account score rather than as the score itself. It arrives episodically, only from customers who answered, and it says nothing about the accounts that stopped contacting you entirely. Pair it with usage and support behavior so the score covers both the customers who speak up and the ones who do not, then validate the combination against actual renewal outcomes before letting it influence net revenue retention targets or the renewal side of sales forecasting.
Frequently Asked Questions
How is customer effort score calculated?
Ask one question after an interaction, usually whether the company made it easy to handle the issue, on a seven point agreement scale. Report the percentage of responses in the top two boxes, or the mean if you prefer a continuous value. Keep the same wording and scale permanently, since any change breaks comparison with prior periods.
What is the difference between CES and CSAT?
CSAT asks whether the customer was satisfied with an interaction. CES asks how hard they had to work. Satisfaction reflects tone and courtesy, which a good agent can deliver even while the underlying problem stays unsolved. Effort reflects the process, which is what determines whether the customer hits the same wall next month.
When should the CES survey be sent?
Within a day of resolution, while the process is still fresh. Sending it weeks later measures memory rather than experience. Send it after a resolved interaction rather than after every ticket update, or the response rate collapses and the sample skews toward the most irritated customers.
Does CES belong in a customer health score?
Yes, weighted by who answered. A high-effort response from an executive sponsor carries more renewal risk than the same response from an occasional user. Weight the input by role and by recency, and pair it with behavioral signals rather than treating it as a standalone verdict.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like customer effort score into prescriptive action for your team.
Schedule a Demo