NPS vs CSAT vs CES: which metric should you use and when?

Teams everywhere run "some survey," but often they aren't sure if it should be NPS, CSAT, or CES—and then they stare at a number with no idea what to change.

All three metrics are useful, but they answer fundamentally different questions. Using the wrong one is like using a thermometer to measure distance: you get a number, but it doesn't tell you where you're going.

By the end of this guide, you’ll know:

• What NPS, CSAT, and CES actually measure.
• When to use each one.
• How to avoid typical mistakes.
• How to combine all three and tie them to AI insights and drivers.

What NPS, CSAT, and CES actually measure

NPS – Net Promoter Score

What it measures: Loyalty and long-term relationship health.

The Question:

"On a scale of 0 to 10, how likely are you to recommend [product/company] to a friend or colleague?"

How it's calculated:

• Promoters (9-10): Loyal enthusiasts.
• Passives (7-8): Satisfied but unenthusiastic.
• Detractors (0-6): Unhappy customers.
• Score: % Promoters – % Detractors.

Typical use: Measuring overall relationship health and loyalty.

CSAT – Customer Satisfaction

What it measures: Satisfaction with a specific interaction or experience.

The Question:

"How satisfied are you with [support interaction / onboarding / recent purchase]?"

The Scale: Usually 1–5 or 1–7.

Typical use: Transactional or touchpoint‑level satisfaction (e.g., "How did this specific ticket go?").

CES – Customer Effort Score

What it measures: How easy or hard it was to get something done.

The Question:

"How easy was it to [complete task]?" or "The company made it easy for me to resolve my issue." (Agreement scale)

Typical use: Measuring friction in key flows like signup, checkout, or support resolution.

| Metric | Main Question | Measures | Best For | Typical Timing | | :--- | :--- | :--- | :--- | :--- | | NPS | "Likely to recommend?" | Loyalty & Relationship | Overall brand health | Quarterly / Lifecycle | | CSAT | "Satisfied with interaction?" | Satisfaction | Specific touchpoints | Immediately after event | | CES | "Easy to complete?" | Effort / Friction | Process optimization | After complex tasks |

When should you use NPS, CSAT, or CES?

Use NPS when...

• You want to know the overall relationship health or loyalty of your user base.
• You run it periodically (e.g., quarterly) or at key lifecycle points (e.g., 90 days after signup).
• You want a single number that leadership can track over time to gauge brand sentiment.

Use CSAT when...

• You want feedback on a specific interaction: a support ticket, an onboarding call, a training session, or a feature launch.
• You care about "How did this particular thing go?" rather than the whole relationship.
• You want to compare experiences (e.g., CSAT for support vs. CSAT for onboarding).

Use CES when...

• You want to measure how much effort customers feel they expend to complete a process.
• You suspect friction: complex signup, confusing billing, or slow support resolution.
• You want to see whether your "simplification" projects are actually making things easier.

Note: You don't have to pick only one. Many successful teams run a combination: NPS for the "big picture," CSAT for support tickets, and CES for their checkout flow.

Common mistakes that make these metrics useless

1. Using only one metric for everything. Example: Using NPS after a single support chat and treating it like relationship NPS. A user might love your agent (high CSAT) but hate your product (low NPS), or vice versa.

2. No open‑ended follow‑up questions. If you collect the score but not "Why did you give this score?", you have no context for improvement. You're left staring at a "42" without knowing if that's good because of your product or bad because of your pricing.

3. Bad timing. Asking CSAT days after the interaction yields inaccurate data. Asking NPS during a known outage or crisis will just tell you what you already know (people are mad).

4. Small samples and over‑reaction. Making big strategic changes based on 5 responses is dangerous. You need enough volume to see real patterns.

5. Staring at the number without connecting it to themes. Reporting "NPS is up 2 points" is nice, but "NPS is up because we fixed the login bug" is actionable.

How to get real value from these metrics

1. Always pair a score with a 'why' question

For each metric question, add a simple follow-up:

"What’s the main reason for your score?"

This creates the raw text that AI can analyze to tell you what's actually happening.

2. Use each metric where it’s strongest

• Relationship NPS at key lifecycle moments (not too often).
• CSAT right after interactions (freshness matters).
• CES on complex journeys and flows (find the friction).

3. Segment smartly

Slice your data by product plan, channel, region, or customer segment. A generic score hides truth—maybe Enterprise users love you (NPS 70) but Freemium users are frustrated (NPS 10).

4. Look at trends, not just snapshots

Track charts over weeks and months. One-off numbers vary; trends tell the story. The goal is to see whether your changes (feature launches, support fixes) correspond to metric movement.

How to see all three metrics and their drivers in one place

This is where FeedPulse AI shines. We help you go beyond the spreadsheet.

Step 1: Connect or upload responses

Import data from Google Forms, CSV/Excel, or Slack exports. FeedPulse AI automatically detects NPS, CSAT, and CES questions from scales and wording.

Step 2: Automatic calculation

For each relevant question, we show:

• NPS: Score + distribution of Promoters, Passives, and Detractors.
• CSAT: Average score + distribution.
• CES: Average effort/ease score.

Step 3: Analyze the "why" behind each metric

Our AI clusters open‑ended responses into positive and negative drivers. Example: You see NPS detractors talking about "long wait time" and "confusing billing," while promoters praise "fast support" and "reliable product."

Step 4: Get a 2–3 line overview per metric

Instead of reading 1,000 rows, read a generated narrative:

"Promoters love your support speed and reliability. Detractors mostly complain about long wait times and confusing billing. Reducing response time and simplifying invoices would have the biggest impact on NPS."

Step 5: Drill down with per‑response labels

Filter by sentiment, intent, emotion, and urgency. Example: Filter to "NPS detractors + high urgency + churn intent" to see exactly who needs immediate follow‑up from your team.

Example: combining NPS, CSAT, and CES in practice

Imagine a SaaS team runs:

1. A quarterly relationship NPS survey.
2. CSAT after every support ticket.
3. CES on their onboarding flow.

They export all three and upload them to FeedPulse AI.

The Platform Shows:

• NPS is flat. (Loyalty isn't growing).
• CSAT after support is high. (Support agents are doing a great job).
• CES for onboarding is poor (High effort).
• Negative Drivers mention "too many steps during setup" much more often than "support response time."

Conclusion: Onboarding friction is the main lever. They prioritize simplifying the setup wizard instead of hiring more support agents.

Choosing the right metric is just the start

Recap:

• NPS = Loyalty.
• CSAT = Satisfaction with specific experiences.
• CES = Effort/Friction.

You get the most value when you combine the right metric, a good follow‑up "why," and AI analysis to surface real drivers.

Ready to see your data clearly?

If you already have an NPS, CSAT, or CES survey in Google Forms or as a CSV export, upload it to FeedPulse AI and see all three metrics, their drivers, and AI‑generated summaries in one place.

---

Related Articles

• Your NPS is 40. So What? — Why the "why" matters more than the score
• Use Feedback Drivers to Prioritize Features — Connect drivers to product decisions
• How to Analyze Open-Ended Responses with AI — Automate the tedious part