NPS vs CSAT: what each measures, when to use which, and why reading the verbatim matters more than the metric you choose.
NPS (Net Promoter Score) measures loyalty and advocacy — how likely a customer is to recommend you, on a 0-to-10 scale, scored as promoters minus detractors. CSAT (Customer Satisfaction) measures satisfaction with a specific interaction — how satisfied were you, usually on a 1-to-5 scale, reported as the percentage who answered positively. NPS is relational and forward-looking; CSAT is transactional and immediate. They answer different questions and are strongest used together.
The debate teams get stuck in — “should we use NPS or CSAT” — is usually the wrong frame. The more useful question is which one fits the decision in front of you, and then, for either, whether you are reading the comment that explains the score. A CSAT of 82 percent and an NPS of 30 are equally useless if no one has read why.
Key takeaways
NPS and CSAT are built for different moments. CSAT captures the temperature of a single interaction while it is fresh: did this support chat, this delivery, this onboarding step satisfy you. NPS steps back and asks about the whole relationship: taken together, would you put your reputation behind us. A great support interaction can lift CSAT while a pricing frustration keeps NPS low, and both readings are true. Choosing one and ignoring the other blinds you to half the picture.
What they share is the part most programs neglect: the comment. Both metrics pair a number with a “why,” and both are usually collected with the why left unread. Sopact calls the alternative the Verbatim Thread: the comment behind either metric read against your codebook on arrival, themed and cited, and kept on the same persistent record as the score. Whichever metric you choose, the reason travels with it, the model behind Sopact’s feedback tools.
Satisfaction measurement moved through three eras. First, separate surveys: a CSAT tool for touchpoints, an NPS tool for the relationship, and two piles of unread comments. Then dashboards that trended each score and offered word clouds, deepening the silo between the two. The current era reads the verbatims behind both onto one customer record, so a low CSAT on onboarding and a low NPS overall can be seen as the same customer’s connected story.
The one test that separates the eras: ask whether you can see, for one customer, their CSAT on a specific interaction, their overall NPS, and the comments behind both, on one screen. Two separate tools cannot; they keep the transactional and relational signals in different systems. Reading both onto one record is what turns two scores into one understanding.
Use CSAT when the decision is about a specific touchpoint: is our support fast enough, did the new onboarding flow land, is checkout painful. It is immediate, high-frequency, and easy to tie to a team that owns the interaction. Use NPS when the decision is about the relationship and the trajectory: are we earning loyalty, is churn risk building, would customers advocate for us. It is lower-frequency and better for executive and strategic views.
Most mature programs run both: CSAT to manage operations touchpoint by touchpoint, NPS to manage the relationship over time. The failure mode is running both as disconnected surveys in different tools, so no one can see that the customers giving low CSAT on billing are the same ones dragging down NPS. Keeping both on one record is what the broader continuous feedback practice is for.
Use CSAT to improve specific interactions and NPS to track the overall relationship; if you can only run one, choose the one matched to the decision you actually need to make — but in both cases, read the verbatim, because an unread score of either kind cannot be acted on. The metric is a smaller choice than the reading. A team drowning in touchpoint problems needs CSAT; a leadership team worried about retention needs NPS; both need the comments read.
The output that makes either metric worth running is a score with its ranked reasons attached, per segment, traceable to the comments. Because Sopact reads the verbatim behind both CSAT and NPS on arrival and keeps them on the Verbatim Thread, you can run the metric that fits the decision without giving up the diagnosis — the how to analyze survey data standard applied to whichever metric you choose.
NPS and CSAT differ in what they measure, when to ask, and what decision they serve — but they share the need to read the comment behind the number. The table makes the split concrete.
| Dimension | NPS | CSAT |
|---|---|---|
| What it measures | Loyalty and advocacy, overall | Satisfaction with a specific interaction |
| Typical scale | 0–10, promoters minus detractors | 1–5, percent positive |
| When to ask | Periodically, on the relationship | Right after a touchpoint |
| Best for | Strategy, churn risk, executive view | Operations, fixing specific touchpoints |
Either way, the reason behind the score is read the same way — see NPS verbatim analysis, and the tooling on CSAT survey software and NPS survey software.
An NPS number is a lagging summary; the reason a customer gave it is in the comment, and only if someone reads the comment while it still matters. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment a response arrives, improve while there is still time to act. On a feedback program that means a detractor’s reason is themed the day it lands and routed to someone who can close the loop, not filed for a quarterly readout.
The Loop is also what makes an NPS finding defensible: every driver and theme traces to the exact comment it came from, the standard detailed in Loop traceability, so “price is the top detractor driver” is backed by the sentences, not a hunch.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
The fastest way past the NPS-or-CSAT debate is to read the comments behind the score you already collect. Export a set of responses with their verbatims, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended survey responses
Here are our NPS comments with each respondent's score: [ATTACH]. Theme every comment against our codebook, cite the sentence behind each theme, and show the top five themes among detractors, passives, and promoters separately.
Academy walkthrough → Analyze sentiment and its drivers
For these NPS verbatims: [ATTACH], score sentiment per comment, then show the specific drivers behind the detractor comments — the recurring reasons, each with a quoted example — so I know what to fix, not just the score.
Academy walkthrough → Connect quant and qual data
Here are our NPS scores and open-ended comments on the same respondent IDs: [ATTACH]. Show which themes explain the detractor scores, quote a comment for each, and list the specific respondents worth a personal follow-up.
Academy walkthrough → Analyze NPS across waves
Here are two waves of NPS from the same respondents on the same IDs: [ATTACH]. Track each respondent's movement between waves, show who moved from detractor to promoter and who slipped, and surface the comments that explain the biggest moves.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading feedback on arrival and tying every comment to the person who gave it.
NPS measures loyalty and advocacy on a 0-to-10 recommend scale, scored as promoters minus detractors; CSAT measures satisfaction with a specific interaction, usually on a 1-to-5 scale reported as percent positive. NPS is relational, CSAT is transactional. Sopact reads the comment behind either on the Verbatim Thread, so the score comes with its reasons.
Use CSAT to improve specific touchpoints and NPS to track the overall relationship; if you can run only one, choose the one matched to the decision you need to make. In both cases, read the verbatim, because an unread score cannot be acted on. Sopact reads the reasons behind both on arrival.
Yes, and most mature programs do: CSAT to manage operations touchpoint by touchpoint, NPS to manage the relationship over time. The failure mode is running them as disconnected surveys in different tools. Sopact keeps both on one customer record so the transactional and relational signals connect.
Neither is universally better; they answer different questions. CSAT is stronger for fixing a specific interaction, NPS for tracking loyalty and churn risk. The bigger determinant of value is whether you read the comment behind the number, which Sopact does for both on arrival.
NPS uses a 0-to-10 recommend scale and reports promoters minus detractors, giving a result between minus 100 and plus 100. CSAT typically uses a 1-to-5 satisfaction scale and reports the percentage of positive responses. Sopact keeps either calculation tied to the themed comments behind it.
Send CSAT right after a specific interaction while it is fresh, and send NPS periodically to gauge the overall relationship. Sending both is common; keeping them on one record is what lets you see that a bad touchpoint CSAT and a low relationship NPS belong to the same customer.
The verbatim. An unread CSAT and an unread NPS are equally inert, while either metric with its comments read produces ranked, actionable drivers. Sopact’s Verbatim Thread reads the reason behind whichever metric you choose, so the choice of metric becomes the smaller decision.
Next: read the reasons behind either score in NPS verbatim analysis, or compare the tools on CSAT survey software.
