Customer Effort Score (CES): Formula, Questions, and Benchmarks

Customer effort score (CES) is a customer experience metric that measures how easy it is for a customer to get something done with your company. You ask one question right after an interaction, such as a support chat, a checkout, or an onboarding step. Low effort protects loyalty, while high effort quietly pushes customers toward your competitors.

Many teams collect CES but struggle to pick a scale, read the score, or decide what to fix. In this guide, we’ll cover the formula, survey questions, benchmarks, and a simple way to turn scores into action.

What is customer effort score (CES)?

Customer effort score (CES) is a survey metric that measures how much effort a customer spent to finish a task, solve a problem, or get a request handled. Companies collect it with a single question right after the interaction, so the memory is fresh.

CES at a glance:

• What it measures: The ease of one specific interaction, not the whole relationship.
• Typical question: “The company made it easy for me to handle my issue.”
• Typical scale: Seven points, from strongly disagree to strongly agree.
• Best moment to ask: Right after a support contact, purchase, sign-up, or self-service task.

The Corporate Executive Board (CEB), now part of Gartner, introduced the metric in a 2010 Harvard Business Review article, Stop Trying to Delight Your Customers. Researchers Matthew Dixon, Karen Freeman, and Nick Toman studied more than 75,000 customers who used service channels. Their conclusion was blunt: reducing effort builds loyalty more reliably than delighting customers does.

How CES 1.0 and CES 2.0 differ

Two versions of the CES question circulate today, and mixing them breaks your trend line. CEB launched CES 2.0 in its 2013 book The Effortless Experience to fix wording problems in the first version.

Why does customer effort matter?

Customer effort matters because it predicts loyalty better than delight does. In the original CEB study, 96% of customers who had a high-effort service interaction became more disloyal, compared with 9% of those who had a low-effort one, according to Harvard Business Review.

The business case goes beyond that one statistic:

• It finds silent churn.
  Most frustrated customers never complain. They just leave, and a CES question gives them an easy way to say what went wrong.

• It points to fixable problems.
  Satisfaction scores tell you how people feel. Effort scores tell you which step felt hard, which is easier to repair.

• It separates must-haves from delighters.
  A smooth basic experience is a baseline expectation, a point the Kano model explains well.

• It links to cost.
  Repeat contacts, channel switching, and escalations all raise the cost of service.

Treat the 96% figure as strong evidence of direction, not a promise. It comes from service interactions in one research program, so measure your own customers before you set targets.

How do you calculate customer effort score?

You calculate CES by averaging all responses, or by reporting the share of customers who chose the top ease options. Pick one method and keep it fixed so your trend stays comparable from quarter to quarter.

Average method

The average method is the most common approach for a seven-point scale. Here is a worked example with ten responses: 7, 6, 6, 5, 7, 4, 6, 3, 5, 6.

1. Add every score: 7 + 6 + 6 + 5 + 7 + 4 + 6 + 3 + 5 + 6 = 55.
2. Count the responses: 10.
3. Divide the total by the count: 55 ÷ 10 = 5.5.

Formula: CES = sum of all scores ÷ number of responses.

Top-box percentage method

The top-box method reports the share of customers who chose the two highest ease points, 6 or 7 on a seven-point scale. In the same ten responses, six customers chose 6 or 7, so the top-box CES is 60%.

Executives often find a percentage easier to read than an average. It also hides less, because a few very low scores cannot drag down a strong majority.

Net score method

Some teams use a net score on a five-point scale, similar to how NPS works.

• Positive responses: Customers who chose “easy” or “very easy.”
• Negative responses: Customers who chose “difficult” or “very difficult.”
• Formula: Percentage positive minus percentage negative.
• Example: 55% positive and 25% negative gives a CES of +30.

Which CES question and scale should you use?

Use the CES 2.0 agreement statement on a seven-point scale unless you have a reason to change it. It is the most widely used format, and it gives you enough range to see small shifts.

Whatever you pick, label at least both endpoints in words. Keep the direction fixed, with higher numbers meaning an easier experience, and add one open-ended follow-up such as “What made this difficult?”

When should you send a CES survey, and what should you ask?

Send a CES survey within minutes of a specific interaction, triggered by that event rather than by a calendar. Effort fades from memory fast, and a survey that arrives days later measures a vague impression instead of the experience.

Use these six triggers and sample questions as a starting point:

• Support interaction: Trigger it when a ticket closes, or a chat ends. Wording to try: “The company made it easy for me to handle my issue.”
• Purchase or checkout: Place it on the order confirmation page. A fitting question: “How easy was it to complete your purchase today?”
• Self-service: Fire it when a help article or chatbot session ends. You could ask: “How easy was it to find the answer you needed?”
• Onboarding: The moment account setup finishes works best. Keep it simple: “How easy was it to get set up?”
• Website or app task: Fit it after a task such as a password reset. One option: “How easy was it to complete this task?”
• Delivery or service visit: Follow up once the appointment or delivery ends. Example: “How easy was it to schedule and receive your service?”

How do you design a CES survey that customers finish?

A good CES survey is short, well timed, and tied to a single interaction. Most completion problems come from asking too much, too late, or too often.

1. Ask one rating question.
   Add one open-ended follow-up at most.

2. Match the channel to the moment.
   Use an in-app prompt after a digital task, and email or SMS after a call or visit.

3. Trigger by event.
   Connect the survey to your help desk, store, or product so it fires automatically.

4. Cap the frequency.
   Limit how often one customer can receive a survey so you avoid fatigue.

5. Record the context.
   Store the channel, agent, product, and segment with each response so you can slice results later.

6. Close the loop.
   Follow up with low scorers while the issue is still fresh.

What is a good customer effort score?

On a seven-point scale, an average of 5.0 or higher is generally acceptable and 6.0 or higher is strong. These are practitioner rules of thumb, not published standards. Industry benchmark tables vary widely and rarely name a source, so treat them with care.

How do you benchmark CES without industry data?

Your best benchmark is your own history, split by touchpoint. A single company-wide score hides the fact that checkout may score 6.2 while returns score 3.8.

• Set a baseline per touchpoint for one full quarter before you set targets.
• Compare like with like. A password reset and a billing dispute will never score the same.
• Track the trend, not just the level. A steady gain over two or three quarters signals real improvement.
• Segment the results. Region, device, plan, and channel often reveal effort that the average hides.

CES vs NPS vs CSAT: What is the difference?

CES measures the ease of one interaction, NPS measures the likelihood to recommend your brand, and CSAT measures satisfaction with an interaction or product. They answer different questions, so they work best together.

You can read more about the formula behind the loyalty metric in this guide to Net Promoter Score calculation.

How do you choose between them?

Pick the metric that matches the decision you need to make.

• Choose CES when you want to simplify a process, such as support, onboarding, or checkout.
• Choose NPS when you want to track long-term loyalty and word of mouth.
• Choose CSAT when you want to rate how an interaction or product felt.
• Use all three when you want to see whether an easy process also produces happy, loyal customers. Our comparison of NPS vs CSAT vs CES explains how.

What do high-effort and low-effort experiences look like?

High-effort experiences make customers repeat themselves, switch channels, or wait. Low-effort ones let them finish in one pass. The three scenarios below are illustrative, not real company data.

Software onboarding

A project management app asks new admins to invite teammates, connect an email account, and import data.

• Signal: Onboarding CES sits at 4.1, and three setup steps trigger support tickets.
• Cause: Open-text answers repeatedly mention the import tool.
• Fix: The team rebuilds the import as a guided wizard and re-measures the next quarter.

Retail returns

A clothing retailer scores 6.2 on checkout but 3.8 on returns. The contrast shows the problem sits in one process, not in the brand.

• Before: Customers print a label, repack the item, and wait for an email approval.
• After: Customers pick a drop-off point in the app, and a QR code replaces the printed label.

Insurance claims

A US auto insurer notices that customers upload photos in one portal and documents in another. Each step reduces ease. Combining the steps into one claim portal changes the picture.

How do you analyze CES results and decide what to fix first?

Start by combining score, volume, and customer comments, because a low score only matters when enough customers feel it. This process turns raw ratings into a ranked fix list.

1. Split scores by touchpoint, channel, and segment. Never read a single blended number.
2. Flag the low scorers. Treat any touchpoint below your baseline as a candidate.
3. Read the comments. Group open-text answers into themes such as wait time, repeated information, or confusing steps.
4. Count the volume. A rare problem with a bad score ranks below a common one with a mediocre score.
5. Assign an owner and a deadline for each fix, and re-measure after the change ships.

A simple priority matrix

How can you reduce customer effort?

You reduce customer effort by removing steps, handing issues off less often, and answering questions before customers ask. The biggest wins usually come from a short list of levers.

• Resolve on first contact.
  Give agents the authority and information to finish the job in one conversation.

• Cut channel switching.
  If a customer starts in chat, do not force a phone call to finish.

• Build useful self-service.
  Write help articles from real support questions, and test them with new users.

• Tell customers what happens next.
  Proactive updates stop the “where is my order” contact.

• Delete steps.
  Remove form fields, approvals, and logins that exist only for internal convenience.

Quick wins versus structural fixes

Quick wins, such as rewriting a confusing help article, show up in scores within weeks. Structural fixes, such as merging two systems, take months but move scores further. Run both tracks so you have progress to report while the larger work ships.

What are the pros and cons of customer effort score?

Customer effort score is simple and actionable, but it covers only one dimension of the experience. Use it for what it does well, and pair it with other metrics for the rest.

Pros:

• Predicts loyalty and repeat behavior better than satisfaction alone in the original CEB research.
• Takes a few seconds to answer, so response rates stay healthy.
• Points directly to the process that needs fixing.
• Works across support, sales, onboarding, and digital journeys.

Cons:

• Says little about price, product quality, or competitors.
• Shows that something was hard, but not why, unless you add an open-ended follow-up.
• Misses emotional moments where effort is not the point.
• Needs a companion metric such as CSAT, so see this guide on how to measure customer satisfaction.

What are the most common CES mistakes?

The most common CES mistakes are collection errors, not math errors. Most of them make the score look better or worse than reality.

1. Mixing CES 1.0 and 2.0 wording in the same trend line.
2. Flipping the scale direction between surveys, so a 6 means different things.
3. Surveying too late, after the customer has forgotten the experience.
4. Reporting one company-wide number that hides weak touchpoints.
5. Skipping the open-ended question, which leaves you with scores but no causes.
6. Surveying only people who finished the task, which ignores customers who gave up.
7. Collecting scores without acting, which wastes the effort and trains customers to ignore your surveys.

How can you measure customer effort score with QuestionPro Customer Experience?

QuestionPro Customer Experience lets you run CES surveys alongside NPS and CSAT and route low scores to the right team. The platform focuses on three capabilities that matter most for effort measurement.

• Score plus reason in one step: AskWhy pairs a rating with the customer’s reason and comment, so you see what made an interaction hard without a second survey.
• Sentiment on open-text answers: Open-end sentiment analysis surfaces tone and urgency across thousands of comments, which speeds up the theme-grouping step.
• Closed-loop follow-up: Closed-loop feedback turns low scores into tracked tickets with automated follow-up workflows.

Teams that want one place for these metrics can start with QuestionPro Customer Experience.

Why customer effort score works best as one signal

Customer effort score earns its place because it is specific, fast, and fixable. It will not tell you whether customers love you, but it will tell you where you make them work.

Treat it as one signal in a broader picture. The easiest experience wins when the product is also good, and building customer loyalty still takes more than removing friction.

Three habits keep the metric useful:

• Measure each touchpoint on its own and keep the scale direction fixed.
• Pair every score with a reason, so you know what to change.
• Re-measure after each fix to confirm that effort really dropped.

Frequently Asked Questions (FAQs)