Introduction
Customer Satisfaction Score (CSAT) is a metric that measures how satisfied customers are with a specific product, feature, interaction, or experience, usually by asking a single question ("How satisfied were you with...?") on a short scale and reporting the share of positive responses. It is the most direct and most widely used experience metric, sitting alongside NPS and Customer Effort Score, and its simplicity is both its strength and its trap. This article covers how CSAT is calculated, when to ask it, what moves it, and how to read it alongside its sibling metrics.
What is CSAT?
CSAT is a satisfaction metric collected by asking customers to rate their satisfaction with something specific, typically on a five-point scale from very dissatisfied to very satisfied (sometimes three, seven, or ten points), and usually reported as the percentage of respondents who chose the top one or two options. "78% CSAT" means 78% of people who answered rated the experience 4 or 5 out of 5. The metric is transactional by design: it is asked about a moment (a support conversation, a checkout, an onboarding session, a feature) close to when it happened, which makes it precise about that moment and silent about the relationship as a whole. That is the division of labor with NPS, which asks about loyalty at the relationship level, and with Customer Effort Score, which asks how hard something was.
Calculating and Reporting It
The top-box convention (share of 4s and 5s on a five-point scale) is the most common, and it is a choice: it treats a 3 as not satisfied, discards the distribution, and can hide a polarized split. Alternatives report the mean score or the full distribution. Whichever is chosen, it must stay fixed, because the definition change is the most common cause of a false trend. Report the n alongside the score (a 90% CSAT from eleven responses is an anecdote with a percentage), and segment by touchpoint, since a blended CSAT across support, product, and billing tells nobody what to fix.
When and How to Ask
1. Ask immediately after the experience.
CSAT is a memory of a moment; the further from the moment, the more it measures general mood. The post-chat prompt, the end-of-onboarding screen, the message after the delivery.
2. Be specific about the object.
"How satisfied were you with today's support conversation?" measures support; "How satisfied are you with us?" measures everything and nothing.
3. Attach a why.
A single open question after the rating is where the actionable content lives; the score tells you a touchpoint slipped, the verbatims tell you what to change. Recorded video answers to the follow-up, collected in a short Ballpark study with the affected customers, turn a dropped score into a diagnosis.
4. Keep the scale balanced and labeled.
Equal positive and negative options, every point labeled, the rating-scale fundamentals.
5. Watch who answers.
Post-interaction surveys are answered by the delighted and the furious; the middle stays silent. Response rates and a comparison with operational data keep the score honest.
What Moves It, and What It Misses
CSAT responds to the immediate experience: speed, resolution, clarity, courtesy. It is sensitive to timing (asked after a resolved ticket versus an unresolved one), to who is asked, and to the framing of the question, all of which can be gamed, the KPI hazard in full. It misses the cumulative relationship (a customer can be satisfied with every interaction and still leave), it says nothing about ease or loyalty on its own, and it is a self-report with the usual politeness inflation. Read it as the health of individual touchpoints, tracked consistently, paired with a why, and triangulated against behavior like repeat contact and churn.
The Short Version
CSAT measures satisfaction with a specific moment, asked right after it, reported as a fixed-definition share of positive responses with its n and its reasons attached. It is the most direct of the experience metrics and the most local: excellent for spotting which touchpoint slipped, blind to the relationship as a whole. Keep it specific, keep it consistent, attach the why, and read it beside NPS, effort, and behavior.
Further reading
For experience metrics and their use:
Articles:
1. What Is CSAT? - Qualtrics
Calculation conventions, question design, and benchmarks for customer satisfaction scores.
2. The One Number You Need to Grow - Harvard Business Review
The article that launched NPS, useful for understanding how relationship metrics differ from transactional ones like CSAT.