TLDR:
- CSAT measures satisfaction with a defined experience; NPS measures stated recommendation intent.
- Neither metric is universally better.
- High CSAT with low NPS can point the investigation beyond the measured touchpoint.
- High NPS with low CSAT can highlight local journey friction.
- Conflicting scores are prompts for investigation, not proof of cause.
- Comments, journey context and segments make the gap more useful.
Turn customer feedback into action.
See how Resonate CX helps you uncover insights, prioritise what matters, and improve CX.
What should a CX team do when CSAT is 92% but NPS is falling? Or when NPS remains strong while customers keep rating one important journey poorly?
That is where CSAT vs NPS becomes more useful than a simple metric comparison.
CSAT measures satisfaction with a specific experience or touchpoint. NPS measures stated willingness to recommend and, in a relationship programme, usually reflects the wider customer relationship. When the two scores move differently, the gap should not be averaged away or treated as an automatic diagnosis. It should trigger an investigation.
This article focuses on what conflicting CSAT and NPS results may indicate, what teams should check before drawing conclusions, and how to connect both measures with customer comments and journey context.
CSAT vs NPS: What Each Metric Measures
CSAT and NPS are different lenses on customer experience.
CSAT is usually used after a defined interaction such as onboarding, delivery or support. It answers a focused question: was the customer satisfied with this experience?
NPS asks how likely a customer is to recommend an organisation, product or service. In a relationship programme, it is commonly used as a broader signal of advocacy.
Resonate CX already has an article covering the fundamentals of CSAT and NPS and when to use each. This article goes further: how should teams interpret the situation when the measures tell different stories?
When CSAT Is High but NPS Is Low
High CSAT with low NPS may mean the measured interaction is performing well while something elsewhere in the relationship is weakening recommendation intent.
Imagine customers consistently rate onboarding support highly, yet relationship NPS is falling.
Do not ask the onboarding team to “fix NPS” simply because they own a visible touchpoint. Widen the investigation. Product fit, reliability, perceived value, policies, digital friction or another journey may be influencing the broader relationship.
Customer comments can narrow the search. If onboarding comments praise the team while NPS comments repeatedly mention price or product limitations, the scores may simply be describing different parts of the experience.
The low NPS does not prove the cause. It tells the organisation where to investigate next.
When NPS Is High but CSAT Is Low
High NPS with low CSAT can happen when customers still value the overall relationship but experience friction in one process.
A customer may trust the brand and be willing to recommend it while disliking a new billing workflow. Low CSAT may therefore be concentrated around one journey, channel, location or recent operational change.
A strong relationship score should not become permission to ignore a weak touchpoint.
It can also clarify ownership. A billing or digital team may own the immediate CSAT issue, while the wider NPS programme sits with CX or leadership.
That distinction matters. Connecting metrics should make responsibility clearer, not turn every customer experience issue into an organisation-wide NPS problem.
When Both CSAT and NPS Change
When CSAT and NPS move in the same direction, the story may look obvious. It still needs evidence.
Suppose onboarding CSAT falls while relationship NPS also declines. Onboarding may be contributing to the wider problem, but two falling scores do not prove causation.
Check whether the same customer groups are represented, whether timing aligns, whether response volumes changed and whether comments show similar themes. Product, pricing, policy or operational changes may also have occurred.
The same principle applies when both metrics improve. A simultaneous rise may be encouraging, but teams should still establish what changed before crediting one initiative with the result.
CSAT vs NPS: Which Metric Should You Use?
Neither CSAT nor NPS is universally better. The right metric depends on the business question and the journey stage being measured.
Use CSAT when you need to understand satisfaction with a defined experience, such as support, delivery or onboarding. Use NPS when you need a broader view of stated recommendation intent across the relationship.
Many organisations need both without expecting them to move together.
A useful rule is to decide the business question first and choose the metric second.
If a team wants to know whether a redesigned support process is improving the experience, CSAT may be closer to the question. If leadership wants to understand whether customer advocacy is strengthening across the broader relationship, NPS may provide the more relevant signal.
The metric should follow the decision you need to make.
A Practical CSAT vs NPS Investigation Matrix
| CSAT | NPS | What it may suggest | Where to investigate |
| High | Low | Strong touchpoint, weaker wider advocacy | Other journeys, value, trust, segments |
| Low | High | Local friction inside a stronger relationship | Process, channel, location or journey |
| Falling | Falling | Potentially connected issues | Shared customers, comments, operational changes |
| Rising | Flat | Local improvement may not affect wider advocacy | Reach of change, journey importance |
| Flat | Falling | Relationship issue may sit outside measured CSAT moments | Unmeasured journeys, product, price, policy |
These are investigation prompts, not diagnoses. The pattern helps teams decide where to look next; it does not establish the root cause.
Check the Measurement Before Blaming the Experience
Not every conflict between CSAT and NPS comes from customer behaviour. Sometimes the measurement changed.
Before acting, compare the survey audience, timing, response volume, question wording, channels and reporting periods behind both measures.
A post-interaction CSAT survey may reach a different population from a quarterly relationship NPS programme. A new SMS channel may change who responds. A rewritten question or sharp fall in response volume may also affect the trend.
Rule this out before redesigning a journey. Part of the apparent conflict may come from methodology.
This is especially important when leaders are looking at month-on-month dashboards. A movement is only useful when the measurement behind it remains sufficiently consistent to support the comparison.
How to Investigate Conflicting CX Metrics
Connect the score with customer comments, journey context, customer segments and relevant behavioural or operational information.
Comments can surface recurring concerns that a rating cannot explain. Journey context shows which experience surrounded the feedback. Segmentation can reveal whether one location, customer type, product or channel is driving the difference. Behavioral information can show what else changed during the same period.
None of these signals should be treated as automatic proof of cause.
AI can support the investigation by organising open-text feedback and surfacing themes, sentiment and recurring patterns. Human judgement is still needed to decide what those patterns mean and what action they justify.
The objective is not to make CSAT and NPS agree. It is to understand why the customer evidence looks different across the two measures and identify the most useful next question.
What to Look for in a CX Measurement Platform
A useful CX measurement platform should keep CSAT and NPS distinct while making it straightforward to investigate them together.
Look for journey-based measurement, clear metric definitions, comments beside scores, segment and location reporting, response-volume visibility, text analytics, customer context, role-relevant reporting and benchmarking where supported.
A useful platform test is:
“NPS is falling while onboarding CSAT is improving. Show us how our team would investigate that.”
This is more revealing than a demonstration where every dashboard metric happens to move in the same direction.
A platform should help teams move from the headline number into the customers, comments, journeys and segments behind it. It should support investigation without presenting correlation as proven cause.
How Resonate CX Helps Teams Connect CSAT and NPS
Resonate CX helps teams connect CSAT and NPS with the customer feedback and context needed to investigate what may be influencing each measure.
AI-Powered Surveys can capture richer context through relevant follow-up questions. AI-Powered Text Analytics organises open-text feedback into topics, themes and sentiment. Robyn AI gives authorised users a natural-language way to explore available CX information and investigate trends and patterns.
Customer Journey Mapping can help teams connect feedback with the moments being measured, while CX Benchmarking can add industry, location and time-based comparison context where supported.
These capabilities support investigation. They do not make conflicting scores explain themselves or turn an AI-detected pattern into a proven root cause.
The practical value is being able to move from “these two scores disagree” to a clearer investigation of which customers, journeys and themes deserve attention.
Frequently Asked Questions
What is the main difference between CSAT and NPS?
CSAT measures satisfaction with a defined experience or touchpoint. NPS measures stated willingness to recommend an organisation, product or service and is often used as a broader relationship signal.
Can CSAT be high while NPS is low?
Yes. Customers can be satisfied with one interaction while having concerns about the wider relationship, product, value or another part of the journey.
Can NPS be high while CSAT is low?
Yes. Customers may value the overall relationship while being dissatisfied with a specific interaction or process.
Which is better, CSAT or NPS?
Neither is universally better. Choose according to the business question and journey stage. CSAT is generally more useful around defined experiences, while NPS is better suited to broader recommendation intent.
Should CSAT and NPS be averaged together?
No. They answer different questions and should remain separate. Teams can review them together to investigate customer experience without combining them into one score.
When CSAT and NPS Disagree, Follow the Evidence
Conflicting CX scores are not a reporting problem to smooth away. They are a reason to ask a more precise question.
High CSAT with low NPS may push the investigation beyond the measured touchpoint. High NPS with low CSAT may focus attention on a journey that needs work. When both move, teams still need to check customers, timing, comments and methodology before deciding the movements are connected.
Keep the metrics separate. Connect the evidence around them.
Resonate CX helps teams bring customer scores, comments, themes and journey context together so differences between CSAT and NPS become a useful starting point for investigation rather than another dashboard debate.
See how Resonate CX can help your team connect CX metrics with the customer evidence behind them. Request a demo.
Run an AI-powered CX program beyond surveys
See our platform in action. A live demo tailored to your organization’s needs.










