# CES: what it is and how to measure customer effort

> Customer Effort Score measures how easy a specific task felt; the calculation depends on the version and scale you name.


**Customer Effort Score (CES) estimates how easy it was to complete a task or resolve an interaction.** There is no single formula that applies interchangeably to every version. This article uses CEB’s CES 2.0: an ease statement rated on a 1–7 agreement scale, reported as the percentage of respondents who agree (5–7). It describes perceived friction in that task; it does not measure overall satisfaction or willingness to recommend.

## What question measures customer effort?

CEB proposed this CES 2.0 statement: **“The company made it easy for me to handle my issue.”** The respondent rates their agreement from 1 (strongly disagree) to 7 (strongly agree). The wording and scale appear in CEB’s original *Blinded by Delight* material (p. 11; [public copy of the document](https://asociaciondec.org/wp-content/uploads/2016/08/Blinded-By-Delight.pdf)). Keeping the question unchanged helps comparisons; if you adapt it to another task, name that task and keep the adapted wording consistent across the series.

“CES” is also used for other questionnaires, scales, and summaries. Some articles and tools average numeric responses; an earlier CES formulation used a different question and scale direction. The CEB CES 2.0 method shown here counts the share of agreement responses from 5–7. Do not combine its results with a scale where 1 means “very easy,” or label the average as this percentage. First define the question, endpoints, scale direction, and reporting method.

## How do you calculate CES 2.0?

**CES 2.0 = agreement responses (5–7) ÷ valid answers to the question × 100.** The denominator includes every valid 1–7 answer, including neutral (4) and disagreement (1–3). People who were invited but did not answer are excluded and reported separately. CEB, the organization that developed CES, describes this agreement-percentage calculation; it is not a universal standard for every metric called CES.

### An example with 80 valid responses

Imagine asking how easy it was to update billing details and receiving 80 valid CES 2.0 responses:

| Response | Number of responses |
|---|---:|
| 1 | 4 |
| 2 | 5 |
| 3 | 8 |
| 4 | 10 |
| 5 | 18 |
| 6 | 22 |
| 7 | 13 |
| **Valid total** | **80** |

Agreement responses are 5, 6, and 7: **18 + 22 + 13 = 53**. So **CES 2.0 = 53 ÷ 80 × 100 = 66.25%**. Do not divide by the 53 favorable answers; use all valid answers to the same item.

## What should you do with the result?

The 66.25% tells you what share of these 80 respondents agreed that the company made the billing update easy. It does not tell you how each of the remaining 27 respondents experienced the task or establish whether the process is good or bad against a universal benchmark. Keep the 1–7 distribution too: the percentage groups the three favorable categories and hides differences between neutral and disagreement.

For this example, ask respondents who chose 1–4 whether they encountered a difficulty and, if so, where: could they not find the option, were they unsure which details to enter, or could they not save the change? Check the flow with a few people and prioritize a repeated, verifiable obstacle. In a later measurement, keep the task, wording, scale, channel, and survey timing consistent. A score change after an update does not by itself prove the update caused it.

CES answers a different question from [CSAT](/en/guides/customer-satisfaction-score/) and [NPS](/en/guides/net-promoter-score/). CES focuses on friction during a task; CSAT records satisfaction with a touchpoint or outcome; NPS asks about recommendation. A task can feel easy even when its outcome disappoints, or feel satisfying despite requiring several steps. Combining the metrics may add context, but one does not replace the others.

*The 80 responses and billing-update task are fictional. The calculation follows the CEB CES 2.0 convention; it does not describe customer data.*

The cover is an AI-generated illustration.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
