
NPS, CSAT, and CES each measure something different: loyalty, satisfaction, and effort. Here is how to choose the right one by touchpoint, and why the score you track matters less than understanding what drives it.
Use NPS for the overall relationship, CSAT for a specific interaction, and CES for how much effort a task took. Choose by touchpoint, not by preference. The metric you pick matters far less than understanding the themes driving it, which is where analyzing the feedback behind the score changes what you can act on.
Most teams asking "NPS vs CSAT vs CES" are really asking two questions at once: which number should we put on the dashboard, and which one will tell us what to fix. Those are not the same question, and confusing them is why so many CX programs track a score for years without ever moving it.
The short answer is this: use the metric that matches the touchpoint. Net Promoter Score (NPS) measures the overall relationship and likelihood to recommend. Customer Satisfaction (CSAT) measures how satisfied someone was with a specific interaction. Customer Effort Score (CES) measures how hard a customer had to work to get something done. Pick the one that fits what you are trying to learn at that moment. But the metric you choose matters far less than understanding what drives it. All three are lagging indicators. The leading indicators are the themes buried in the open-text feedback attached to every score. Thematic exists to surface those drivers, which is the half of the question the metric debate leaves out.
Below is a straight comparison of the three metrics, when each one is the right choice, and why the score you pick is only as useful as your ability to explain what is moving it.
NPS, CSAT, and CES are not competitors. Each is one way to measure customer satisfaction, and they answer different questions at different points in the customer journey.
None of them is sufficient on its own. Used together, chosen by touchpoint, they give a fuller picture of how customers feel, where friction sits, and what to prioritize. The mistake is treating the choice between them as the strategic decision. It is not. The strategic decision is what you do with the reasons behind the number.
| Metric | What it measures | Typical question and scale | When to use it | Common pitfall |
|---|---|---|---|---|
| NPS | Overall relationship and likelihood to recommend | "How likely are you to recommend us to a friend or colleague?" on 0 to 10. Score is percent Promoters minus percent Detractors, from -100 to +100. | Relationship health tracked over time, board-level reporting, benchmarking across the business | A single number that hides why it moved. Easy to track, hard to act on without the verbatims. |
| CSAT | Satisfaction with one specific interaction | "How satisfied were you with this experience?" usually on 1 to 5. Score is the percent of 4 and 5 responses. | Right after a defined touchpoint: a purchase, a support ticket, an onboarding step | Inflates near the top of the scale and rarely explains the gap between a 4 and a 5. |
| CES | How much effort a task took the customer | "[Company] made it easy to handle my issue" agree or disagree, usually on 1 to 7. Score is the average. | Immediately after a support interaction or self-service task where friction is the risk | Narrow by design. Tells you a task was hard, not which part of it or why. |
Use NPS when you need a relationship signal you can trend and benchmark. It is the right metric for a quarterly executive view, for comparing regions or product lines, and for tying customer sentiment to growth over time. Be honest about its limits. A 2007 study in the Journal of Marketing found NPS performed no better than other loyalty and satisfaction measures at predicting company growth, and Bain, which created NPS, later introduced an accounting-based "earned growth" measure precisely because the survey number alone was not enough.
Use CSAT when you want fast, specific feedback on a single moment. It is the cleanest read on whether one interaction landed. Satisfaction scores are intuitive to non-analysts and easy to collect at volume, which makes CSAT a good day-to-day operational metric for support and product teams. Its weakness is precision: a 4 out of 5 rarely tells you what would have made it a 5.
Use CES when friction is the thing you are trying to remove. CES is the most predictive of the three for repeat behavior in support contexts. The original research found that 94% of customers reporting low effort said they would repurchase, while 96% of those with high-effort experiences became disloyal. If your risk is customers giving up because something is too hard, CES is the sharpest instrument.
Here is what the standard "use all three" advice leaves out. Whichever metric you track, the number is an outcome. The theme in the open-ended comment next to it is the driver. Scores quantify the result. Themes explain what caused it. If you only watch the score, you are reading the symptom and guessing at the cause.
This is where analyzing the feedback itself, at scale, changes the return on any metric you pick. Thematic reads every open-text response behind the score, groups it into themes, and quantifies each theme's impact on the score, so a CX team can see that stock availability, not price, is what is costing them points.
The proof is in what happens when teams act on the driver instead of the score:
In each case the metric was almost incidental. What moved the business was knowing which theme to fix.
Work through these questions before you commit to a metric:
Once you have chosen, put your real effort into the last question. A metric you cannot explain is a metric you cannot improve. Thematic can also generate predicted NPS, CSAT, and effort scores from unstructured feedback such as calls and chats, so touchpoints that never carried a survey still produce a score you can act on.
Use NPS for the overall relationship, CSAT for satisfaction with a specific interaction, and CES for how much effort a task took. Choose by touchpoint, not by preference, and do not expect any single number to run your program on its own. The metric you track matters far less than your ability to explain what is driving it. Pick the one that fits the moment, then measure the themes behind it. That is the number that actually moves.
Thematic turns fragmented feedback into one consistent source of customer truth — so every team acts on the same customer story. Up and running in days, not quarters.

Transforming customer feedback with AI holds immense potential, but many organizations stumble into unexpected challenges.