CSAT, NPS, and CES are often discussed as if one metric has to win. In practice, they answer different questions.
CSAT tells you whether a customer was satisfied with a specific interaction. NPS tells you how likely a customer is to recommend your company. CES tells you how easy it was for a customer to complete a task.
If you are building a feedback program, start with the question you need to answer, then choose the metric. Gleap’s customer feedback surveys can collect all three, but the value comes from using each one at the right moment.
Quick Comparison
| Metric | What it measures | Best used for | Typical question |
|---|---|---|---|
| CSAT | Satisfaction with a touchpoint | Support tickets, onboarding calls, feature experiences | ”How satisfied were you with this experience?” |
| NPS | Loyalty and recommendation intent | Relationship health, account sentiment, executive reporting | ”How likely are you to recommend us?” |
| CES | Customer effort | Onboarding, self-service, support resolution, setup tasks | ”How easy was it to complete this?” |
Each metric becomes more useful when paired with an open text follow-up. The score shows direction. The comment explains why.
When to Use CSAT
Use CSAT after a specific interaction: a support conversation, a resolved ticket, a training session, or a feature workflow.
CSAT is helpful because it is close to the experience. If satisfaction drops after support interactions, you can investigate response quality, handoffs, issue complexity, or documentation gaps. If CSAT drops after a feature launch, you may have a usability or education problem.
CSAT is less useful for measuring long-term loyalty. A customer can be satisfied with one support answer and still be at risk of churn.
When to Use NPS
Use NPS when you want a relationship-level signal. It is best for understanding overall sentiment by account, segment, lifecycle stage, or cohort.
NPS should not be sent after every interaction. It works better on a controlled cadence or after meaningful milestones, such as onboarding completion or several weeks of product usage.
The most useful part of NPS is often the follow-up question. Ask why the customer gave that score, then group responses by theme. For a deeper measurement system, connect NPS to the broader customer experience metrics you already track.
When to Use CES
Use CES when friction is the main question. SaaS products ask customers to do work: configure settings, invite teammates, import data, set up integrations, find answers, and adopt workflows.
CES helps you find where that work feels harder than it should. It is especially useful after:
- Onboarding steps.
- Integration setup.
- Self-service help flows.
- Support resolution.
- Billing or account management tasks.
If CES is low, the fix may not be more support. It may be simpler UX, better defaults, clearer docs, or more contextual help from a knowledge base.
How to Combine the Three Metrics
A healthy CX program uses the metrics together:
- CSAT: “Was this interaction good?”
- CES: “Was this workflow easy?”
- NPS: “Do customers trust and recommend us overall?”
Imagine a customer gives high CSAT after a support chat but low CES for the setup process. Your support team did well, but the product workflow still needs improvement.
Or imagine NPS drops among new customers while CSAT remains strong. That can point to onboarding, time-to-value, pricing expectations, or product-market fit rather than support quality.
This is why metrics should feed product, support, and customer success conversations together. Tools like Kai can help teams summarize feedback themes, but the team still needs to decide what action the pattern deserves.
Common Mistakes
Do not over-survey. Sending every metric to every user creates fatigue and weak data.
Do not compare scores without context. A CSAT score after a critical outage and a CSAT score after a simple billing question are not the same kind of signal.
Do not ignore open-text responses. The score is the headline, not the diagnosis.
Do not collect metrics without owners. Every survey should have a team responsible for reviewing, acting, and closing the loop.
Final Recommendation
If you are just starting, choose one relationship metric and one operational metric. For many SaaS teams, that means NPS for relationship health and CSAT after support tickets.
Add CES when you are ready to improve specific workflows like onboarding, integration setup, or self-service support. Over time, CSAT, NPS, and CES together create a clearer picture: how customers feel, how loyal they are, and how hard your product makes them work.