> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/tutorials/customer-effort-score.md).

# Customer Effort Score (CES)

Measure how easy it is for customers to interact with your product or service

Customer Effort Score (CES) is a customer service metric that measures user experience with a product or service. Customers rank their experience on a seven-point scale ranging from "Very Difficult" to "Very Easy."

#### When to Use CES

CES surveys are best used immediately after a specific service or product interaction:

* After a support ticket is resolved
* After account creation or onboarding
* After a trial period signup
* After a key product interaction

#### CES vs. Other Metrics

| Metric   | Best For                                             |
| -------- | ---------------------------------------------------- |
| **CES**  | Measuring effort for a specific interaction or event |
| **CSAT** | General satisfaction across various topics           |
| **NPS**  | Overall brand loyalty and likelihood to recommend    |

CES differs from CSAT in that it must refer to a specific event or circumstance, rather than general satisfaction. It differs from NPS which asks a broader question about recommending your company.

#### Setting Up a CES Survey

1. Go to **Surveys → New Survey**.
2. Create a question with the question: "How easy was it to \[complete the action]?"
3. Use a **rating** question type with a 1–7 scale.
4. Label the scale endpoints: 1 = "Very Difficult", 7 = "Very Easy".

#### Interpreting Your Score

On a standard seven-point scale:

* **5 or higher** — Good score, indicating a low-effort experience
* **Below 5** — Consider changes to reduce friction in that interaction

Higher scores represent a better user experience, as they indicate the customer found the interaction easy to complete.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/tutorials/customer-effort-score.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.