Share article
Picture two companies. One boasts every quarter about a Net Promoter Score of around 45 and talks about it in meetings like it’s a school report card. The other asks just one thing after every support call: “How satisfied were you with how this was resolved?” Both companies are measuring something about the customer. But they’re asking completely different questions, so they get completely different answers.
In the two decades since it was created, Net Promoter Score (NPS) has earned its place as the crown metric of CX (customer experience). It’s simple, comparable across companies, and investors love it. But precisely because it’s so universal, it’s also a fairly blunt instrument. It measures how a customer feels about the brand as a whole, not what just happened to them. This is where CSAT (Customer Satisfaction Score) comes in: a metric that’s less impressive on a slide for the board, but in many situations, far more precise.
What CSAT actually measures
CSAT asks one specific thing, at one specific moment: “How satisfied were you with [the purchase / the support call / the delivery]?” Usually on a scale of 1–5 or 1–10, sometimes using emojis or star ratings. It’s what’s known as a transactional metric, measuring satisfaction with a single interaction rather than the overall relationship with the company.
This is a crucial difference from NPS, which is a relational metric, asking how favourably a customer feels towards the company as a whole, regardless of what happened yesterday on a support chat. So if you want to know whether your new onboarding process is working, or whether the latest change to your complaints form has annoyed customers more than before, NPS won’t help you. CSAT will, because it’s sensitive to change and can be measured immediately after an interaction, while the experience is still fresh.
I’ll admit I long underestimated how much this distinction matters. CSAT is most useful exactly where you need fast feedback on a specific step of the customer journey: after a purchase, after a support ticket is resolved, after onboarding is completed, after a product installation. Anywhere you’re asking “did this work?” rather than “do you like us?”
CSAT, NPS, or CES? Three questions, three answers
There’s a third metric worth mentioning: CES (Customer Effort Score), which asks how easy or difficult it was for the customer to get something resolved. A typical question reads: “The company made it easy for me to handle my issue,” with an agreement-scale response.
CES was born in 2010, when Matthew Dixon, Karen Freeman and Nicholas Toman of the research firm CEB (now part of Gartner) published a Harvard Business Review article with the provocative title “Stop Trying to Delight Your Customers.” Their analysis of almost 97,000 customers revealed something that turned conventional wisdom on its head at the time: there was practically no difference in loyalty between customers whose expectations were exceeded and those whose expectations were merely met. What actually predicted loyalty was effort: 96% of customers who had a high-effort interaction became disloyal, compared with just 9% of those with a low-effort one. Later Gartner research found that CES is roughly 1.8 times better at predicting loyalty than CSAT, and about twice as good as NPS, specifically in the context of service and support interactions.
So when should you reach for which?
NPS makes sense as a periodic temperature check on the relationship, quarterly or twice a year, when you want to know how overall loyalty is developing and whether your CX initiatives are working in the long run. CSAT belongs with specific interactions, where you want fast, sensitive feedback on quality, and ideally where satisfaction can be influenced in the short term (a new process, retrained agents, a product change). CES belongs wherever ease is the topic, primarily in customer support and service processes, where you want to know how much effort the whole thing cost the customer.
The important thing is not to try to track all three metrics with equal intensity everywhere. Realistically, most CX teams don’t have the capacity for that, and three half-heartedly tracked metrics are worse than one you actually do properly. A proven approach is to treat CSAT and CES as operational metrics at individual touchpoints, with NPS as the strategic compass sitting above it all.
How to calculate CSAT properly
This is where I want to be a bit pedantic, because this is exactly where most of the confusion around CSAT comes from. The standard formula is:
CSAT (%) = (number of satisfied responses ÷ total number of responses) × 100
A “satisfied response” doesn’t mean the average of the scale, though, it means what’s called a top-box (or top-two-box) approach: on a 1–5 scale, you count responses of 4 and 5; on a 1–10 scale, usually 7–10. So if 78 out of 100 respondents answer with a 4 or 5, your CSAT is 78%.
This has one important implication: CSAT isn’t an average mood, it’s the proportion of people who cleared a certain satisfaction bar. Two companies could theoretically have the same “average” on the scale, yet very different CSAT scores, depending on how the responses are distributed.
As for the numbers themselves, available benchmarks put the average CSAT across industries at around 78%. A score above 80% is generally considered strong; below 70% is a signal that something needs addressing immediately. Industries vary significantly, though: consulting services sit at around 84% according to the data, while e-commerce and retail sit around 82%. So before judging your own number as “good” or “bad,” you need to know your industry’s benchmark, not some generic figure from the internet.
Typical mistakes that can badly distort CSAT
This is the part I’d want anyone working with CSAT to read twice, because it’s surprisingly easy to do a lot of damage here even with the best of intentions.
The first problem is non-response bias. Satisfied customers respond to surveys more readily than dissatisfied ones, because frustrated customers often leave (or stop being customers) before the survey even reaches them, or they simply ignore it, since they don’t have the energy to fill in another form after something has annoyed them. The result is a systematically inflated CSAT that doesn’t reflect the reality of the whole customer base, just the portion that still bothered to respond.
The second problem is central tendency: people avoid extremes on a scale and gravitate towards the middle. On a 1–5 scale, most responses fall into the 3–5 range, because the bottom two options are psychologically tied to a strongly negative rating and require the respondent to actively choose something unpleasant.
The third mistake relates to what happens to the data after it’s collected: many teams only look at the extremes, “very satisfied” versus “very dissatisfied”, and ignore neutral responses, even though the neutral group is often the largest one. A neutral customer isn’t the same as a satisfied customer who’s simply not complaining, it’s a segment still waiting to be swayed one way or the other.
The fourth mistake is timing. Asking about satisfaction too long after an interaction means the customer is responding based on what they remember or how they feel in general, rather than what actually happened. A survey sent a week after a ticket is resolved measures something different from one sent five minutes after the call.
And the last, perhaps most insidious mistake: treating CSAT as a universal success metric that can be compared across completely different touchpoints without segmentation. CSAT after a complaint and CSAT after a routine purchase measure fundamentally different situations with different emotional weight, and merging them into a single dashboard number leads to decisions with no grounding in reality.
The takeaway
NPS is a great compass for overall direction, but it’s blind to detail. CES is the best predictor of loyalty where ease of resolving a problem is what matters. And CSAT, when used honestly and with the right context, is a tool that can pinpoint exactly where in the customer journey something is breaking down or, just as often, going right. It’s not as flashy a number as NPS, and it doesn’t sound as clever as CES in a board presentation. But for the everyday improvement of specific processes, it’s often exactly the tool you need.
