NPS vs CSAT vs CES
All three measure customer sentiment, but at different levels. Choosing the right one, and acting on it, matters more than the acronym.
Quick answer — What is the difference between NPS and CSAT? NPS measures overall loyalty and willingness to recommend. CSAT measures satisfaction with a specific interaction or experience.
At a glance
| NPS | CSAT | CES | |
|---|---|---|---|
| Stands for | Net Promoter Score | Customer Satisfaction Score | Customer Effort Score |
| Question | How likely are you to recommend us (0–10)? | How satisfied were you with [interaction]? | How easy was it to [do task]? |
| Measures | Overall loyalty to the brand/relationship | Satisfaction with a specific interaction | Friction in a specific task |
| Timing | Periodic (e.g., quarterly) | Right after an interaction | Right after a task |
| Best for | Relationship health trend | Support, onboarding, training quality | Spotting friction in processes |
NPS
Useful as a trend, but weak as a single-account predictor: people who answer are not representative, and a score without the "why" is hard to act on.
CSAT
CSAT is the percentage of respondents who rate an experience as satisfied. Because it follows a specific interaction, it is more actionable for support and onboarding teams, though it only reflects the moment measured.
CES
CES asks how easy something was. It is useful for finding process friction, such as onboarding steps or support resolution, and often correlates with repeat usage.
How CS teams use them
- Send NPS to key stakeholders at relationship level, and watch for a drop in a specific account.
- Use CSAT after onboarding calls and support cases.
- Use CES to refine processes.
- Feed results into the health score, but do not overweight them: they are lagging.
- Always read the comments. See voice of the customer.
Pitfalls
- Low response rates and survey fatigue.
- Surveying only happy customers.
- Treating a score as the goal. The goal is the follow-up action.
- Comparing scores across industries or survey methods.
AI can analyze open-text responses at scale; see sentiment analysis. For the full list of KPIs, read CS metrics.
Designing surveys that get answers
- Keep it to one or two questions.
- Send at a relevant moment, not on a calendar alone.
- Make the open-text follow-up optional but visible.
- Send from a real person where possible.
- Avoid surveying the same contact repeatedly.
A follow-up playbook
| Result | Response |
|---|---|
| Detractor / low score | CSM contacts within 48 hours; log reason; escalate if serious |
| Passive | Ask what would make it a 9 or 10 |
| Promoter | Thank them; consider advocacy or a review request |
Getting more from survey programs
Survey metrics are most valuable as conversation starters. A drop in NPS from a key account is a prompt to call them, not a number to report. The comments often contain the real insight: what customers value, what frustrates them, and what competitors are doing. Reading and tagging those comments regularly yields more value than watching the score move a point or two.
It also helps to match each survey to a decision. If you cannot say what you will do differently depending on the result, you probably do not need the survey. Keep programs short and targeted, respect customers' time, and share results and actions back to those who responded. Over time, that discipline improves both response rates and the usefulness of the data.
Key takeaways
- Treat scores as prompts for conversation.
- Read and tag open-text comments.
- Match each survey to a decision.
- Share results and actions with respondents.
Frequently asked questions
See what CSMs really earn
Compare your pay against real CSM submissions — free, anonymous, takes 2 minutes.