The most-used CX metric in the world. What CSAT measures, how to calculate it correctly, what drives high scores, and the operational disciplines that actually move it.
Customer Satisfaction Score (CSAT) is a customer experience metric that measures how satisfied a customer was with a specific interaction, purchase, or experience. Customers are typically asked "How satisfied were you with [the interaction]?" on a scale of 1 to 5, with the score reported as the percentage of customers who chose 4 or 5.
The simplicity of CSAT is its strength and its trap. Strength: it is fast, intuitive, easy to deploy after any customer interaction. Trap: it is easy to game, easy to misinterpret, and easy to over-rely on without understanding what it does not tell you.
The operations that use CSAT well share a small set of disciplines. They segment relentlessly. They pair it with other metrics (NPS for loyalty, CES for friction). They tie it to operational changes, not just dashboard reports. And they treat CSAT trends as more meaningful than CSAT snapshots — because a 78 that has been climbing for three quarters is healthier than an 85 that has been flat for two years.
This hub covers what CSAT is, how to measure it correctly, what drives high and low scores, where it commonly misleads, and how to combine it with other CX metrics into a measurement program that actually drives decisions.
What CSAT is and how to measure it correctly.
Why most CSAT plateaus are diagnostic, not bad luck.
The structural reasons CSAT stalls and the operational moves that restart improvement.
FCR is one of the strongest upstream drivers of CSAT.
Effort is what makes customers dissatisfied. CES is the diagnostic CSAT alone cannot give you.
How CSAT fits into a complete customer experience measurement system.
The relationship-level loyalty metric that pairs with CSAT.
The broader operational discipline CSAT lives within.
Where CSAT belongs in the operational dashboard alongside FCR, AHT, CES, NPS.
Most CSAT plateaus trace to a small number of operational causes — and they are identifiable. We help operations diagnose what is keeping the number stuck and build the changes that restart improvement.