CSAT (Customer Satisfaction Score) is a simple metric for measuring satisfaction with a specific experience. Alongside NPS, it is one of the most widely used ways to surface the voice of the customer — but plenty of CSAT programs degrade into "we have numbers nobody acts on."
This article walks through five steps for running a CSAT program at the level where it actually drives decisions.
What CSAT is
CSAT measures how satisfied a customer was with a specific service or experience. The classic form:
"How satisfied were you with our support today?" (Very dissatisfied 1 — 2 — 3 — 4 — 5 Very satisfied)
The score is usually reported as "% of responses that were 4 or 5." Above 80% is good, above 90% is exceptional.
NPS vs. CSAT
The two get conflated. They are for different things.
| Dimension | NPS | CSAT |
|---|---|---|
| Measures | Loyalty (likelihood to recommend) | Satisfaction with an experience |
| Timing | The whole relationship / on a cadence | Right after a specific touchpoint |
| Question | Recommendation | Satisfaction |
| Use | Executive metric / long-term trend | UX improvement / operational quality |
Easy mnemonic: NPS for the exec team, CSAT for the operating team.
Step 1: Decide what you are trying to improve first
The most common CSAT failure is "we'll just ask about satisfaction." Data accumulates, but you cannot tell what change moves the score, and the results gather dust.
Settle the target of improvement before fielding:
- Improve support quality → CSAT immediately after a support case
- Improve onboarding → CSAT immediately after initial setup
- Measure product quality → CSAT after the product arrives
Once the target is settled, the questions, the timing, and the analysis axes all fall out of it naturally.
Step 2: Question design
The CSAT question itself is one item, but you always pair it with a few supporting questions to capture the why.
Recommended set
- CSAT proper — 5-point or 7-point scale
- Reason (open text) — "Tell us why you felt that way"
- Improvement request (open text, optional) — "Anything you'd like us to change?"
- Attributes (optional) — plan, tenure, etc., so you can analyze by segment
Past 4–5 questions, response rate drops. Stay tight.
Picking the scale
- 5-point is easy to understand but suffers from central bias (everyone picks 3)
- 7-point gives finer resolution but takes longer to answer
- 4- or 6-point even scales force respondents off the center
For testing whether a change moved the needle, use an even scale. For long-term trending, 5-point is standard.
Step 3: Distribute right after the experience
CSAT precision drops as memory fades. Days later, satisfaction ratings drift toward the middle.
| Experience | When to distribute |
|---|---|
| Support case | Immediately after resolution (in-email or in-chat) |
| Purchase / contract | Right after product arrival / setup complete |
| Event attendance | Same day or next day |
| Feature use | On the completion screen, or within 24 hours |
Follow-up email distribution has low open rates and biased samples. Where possible, collect via in-app feedback rather than email.
Step 4: Set up data so it is actually analyzable
Staring at the headline number does not drive improvement. Design upfront so you can slice three ways:
1. Trend over time
Monthly or quarterly trends surface program effects and seasonality.
2. By segment
Breaking down by plan, tenure, region etc. surfaces things like "satisfaction is only low in one specific segment."
3. Theme classification on open-text
Classify open responses into themes like "support / features / pricing / ease of use" and count. Prioritization for improvement becomes obvious.
Past a few dozen open responses, AI classification is effective — faster than doing it by hand, and arguably more objective.
Step 5: Build the loop into action
The real value of a CSAT program is action, not collection. Three mechanisms that prevent CSAT from becoming "just a number":
1. Immediate follow-up on low scores
For low responses (1–2 on a 5-point), follow up personally where possible. "Could you tell us more about what happened?" is often enough to start a relationship-repair conversation.
2. Review at the executive cadence
Put CSAT score plus representative open-text quotes on the monthly executive review. Frontline improvement starts to connect to executive decision-making.
3. Re-measure after the change
When you ship an improvement, re-measure with the same question and look at the delta. Repeat this enough and your team accumulates organizational knowledge about what kinds of changes move the score.
Summary
Five steps to a working CSAT program:
- Decide the target of improvement first
- Pair the headline question with supporting questions
- Distribute right after the experience
- Make it analyzable by trend, segment, and theme
- Build the loop: action and re-measurement
Simple as a survey, but design and operations decide whether it changes decision quality.
Repoan ships CSAT templates for SaaS, e-commerce, B2B, and restaurants. Combined with website embedding and auto-generated brand theming, you can ship a CSAT form that looks native to your site.
Once responses come in, the AI report feature (see AI response analysis) handles open-text theme classification and exec-summary generation in one click. You can start improvement work the same day the data lands.
Related
- After collection: Putting survey results to work
- Designing the improvement cycle: Running a survey PDCA cycle
- AI-era customer understanding: Why run surveys in the AI era