A CSAT survey measures how satisfied a customer was with one specific interaction, product, or service. You ask a single question ("How satisfied were you with...?") on a 1 to 5 scale, then calculate the customer satisfaction score as the percentage of customers who answered 4 or 5. If 80 people respond and 60 pick 4 or 5, your CSAT is 75%. Most teams treat 75% to 85% as good.
CSAT is the oldest and simplest of the three big experience metrics, and its simplicity is both the strength and the trap. It is easy to run and easy to read, but it is also easy to run badly: ask at the wrong moment, and a high score tells you nothing useful. This guide covers the exact question, the formula, benchmarks you can actually trust, and how CSAT fits alongside NPS and CES.
What is a CSAT survey?
A CSAT survey is a short, transactional survey that measures a customer's satisfaction with a single, specific experience: a support conversation they just finished, a delivery they just received, an onboarding call they just had. It is fired right after the moment it asks about, while the experience is fresh, and it reports one number: the percentage of respondents who rated the interaction positively.
The word that matters is transactional. CSAT is not about how the customer feels about your company overall, and it is not about loyalty. It is about one event. That narrow focus is what makes it useful for operations: a low CSAT on "your last support ticket" points at the support queue, not at some vague brand feeling you cannot act on.
The CSAT survey question
The standard CSAT question is: "How satisfied were you with [the specific interaction]?" answered on a 5-point scale from "Very dissatisfied" to "Very satisfied." Some teams use a 1 to 7 or 1 to 10 scale, but 1 to 5 is the most common and the easiest to calculate against. You add one open-text follow-up ("What is the main reason for your rating?") so the number comes with a reason attached.
A few rules keep the score honest and comparable:
- Name the specific interaction. "How satisfied were you with your recent support conversation?" beats "How satisfied are you with us?" The specific version is the one you can act on.
- Ask immediately. CSAT decays fast. Sent an hour after the interaction, it captures the moment. Sent a week later, it captures a mood.
- Keep the scale consistent. Pick one scale (1 to 5 is fine) and never change it, or your trend line becomes meaningless.
- Always include the open text. The rating tells you the level. The comment tells you the cause, and the cause is the only part you can fix.
How to calculate CSAT
To calculate your CSAT score, count the customers who gave a positive rating (4 or 5 on a 5-point scale), divide by the total number of responses, and multiply by 100. The formula is: CSAT = (number of satisfied responses / total responses) x 100. "Satisfied" almost always means the top two boxes (4 and 5), not just the very top one, because a 4 is a genuinely happy customer.
Here is a worked example. Say you send a post-support survey and collect 120 responses:
| Rating | Responses | Counts as satisfied? |
|---|---|---|
| 5 (very satisfied) | 58 | Yes |
| 4 (satisfied) | 32 | Yes |
| 3 (neutral) | 16 | No |
| 2 (dissatisfied) | 9 | No |
| 1 (very dissatisfied) | 5 | No |
Satisfied responses are 58 + 32 = 90. Total responses are 120. So CSAT = (90 / 120) x 100 = 75%. You do not need a CSAT calculator for this; it is one division and a multiply. The harder part is deciding what counts as satisfied and never changing it, because the moment you fold the neutral 3s into "satisfied" to lift the number, you have broken your own trend line.
What is a good CSAT score?
A good CSAT score is generally 75% to 85%, with anything above 90% considered excellent and anything below 70% a signal that something in the experience needs work. Benchmarks vary a lot by industry, though, so the number that matters most is your own trend over time, not another company's headline figure. Compare yourself to last quarter before you compare yourself to anyone else.
As rough industry reference points that show up consistently across published benchmarks:
| Sector | Typical CSAT range |
|---|---|
| Ecommerce and retail | 80% to 90% |
| Software and technology | 70% to 80% |
| Financial services and insurance | 75% to 85% |
| Telecom and utilities | 65% to 75% |
Treat these as context, not targets. A 78% in software is fine; a 78% in ecommerce might mean you are losing to competitors sitting at 88%. And a rising 72% is a healthier sign than a flat 84%, because the trend tells you whether your fixes are working.
When to send a CSAT survey
Send a CSAT survey right after a discrete interaction you want to measure, not on a calendar. The classic triggers are the close of a support ticket, the completion of onboarding, a delivery, or the first use of a new feature. Each of those is a moment with a clear owner, so a low score routes straight to the team that can do something about it.
The mistake that quietly ruins CSAT programs is surveying everyone about everything all the time. Survey fatigue tanks your response rate and biases who answers (usually the angriest and the most delighted, with the quiet majority missing). Pick the two or three moments that matter most, survey those consistently, and leave the rest alone. A high response rate on three well-chosen triggers beats a trickle across a dozen.
CSAT vs NPS vs CES
CSAT, NPS, and CES measure different things and answer different questions, which is why mature programs run more than one. CSAT measures satisfaction with a specific interaction, NPS measures loyalty to the whole relationship, and CES measures how much effort a task took. None replaces the others; they sit at different points in the journey.
| Metric | Question | Scale | Best for |
|---|---|---|---|
| CSAT | How satisfied were you with this? | 1 to 5 | A specific interaction, right after it happens |
| NPS | How likely are you to recommend us? | 0 to 10 | Overall loyalty, checked at relationship milestones |
| CES | How easy was it to get this done? | 1 to 7 | Effort in a process, a strong churn predictor |
A practical split: run CSAT on individual support and delivery interactions, run the customer effort score survey on multi-step processes like onboarding or a return, and run the NPS survey at relationship checkpoints like renewal. If you want the full question wording for each situation, our customer satisfaction survey questions and templates gives you copy-paste versions by survey type, and the broader voice of customer program guide shows how all three feed one listening system.
Why your CSAT score is not improving
If your CSAT is stuck, the usual reason is that nobody acts on the low scores. A survey with no follow-up is a thermometer no one reads: it records the temperature and changes nothing. The fix is a closed loop. Someone reads the detractor comments each week, groups them into themes, routes each theme to the team that owns it, and reports back what changed. That is the whole difference between a metric and an improvement engine, and it is the same pattern we lay out in the guide to building a customer feedback loop that actually closes.
The second common reason is that the score is measuring the wrong thing. A high CSAT on "your support agent" can sit right next to a low CSAT on "resolving your issue," because the agent was lovely and the problem still is not fixed. Split your triggers so a friendly-but-useless interaction cannot hide behind a warm rating. And watch the comments more than the number: the reasons are where the fixable operational problems live, which is why CSAT belongs alongside your other support metrics and KPIs rather than on its own dashboard.
Start with one trigger and one owner
You do not need a survey platform to run CSAT well. Pick the single interaction that matters most (a closed support ticket is the usual best first choice), ask one satisfaction question plus one open-text follow-up right after it happens, and give one person the standing job of reading the low scores each week and routing them to whoever can fix the cause. Report the percentage satisfied and the top three complaint themes. That is a complete CSAT loop. Prove it works on one trigger, then add a second. Almost every problem CSAT surfaces turns out to be an operational one, which is the throughline in our foundational piece on why customer experience is won in the back office: the score is where you notice it, but the process underneath is the only place you can fix it.