CSAT, or Customer Satisfaction Score, is a single-question metric that measures how many customers were satisfied with a specific interaction. On a 5-point scale, it is usually the percentage of respondents who choose 4 or 5. On a Likert scale, that often means "satisfied" or "very satisfied." The formula is simple: satisfied responses divided by total responses, multiplied by 100. Use a csat survey after a purchase, support case, onboarding step, or feature use when you need a fast read on experience quality at a specific moment.
For customer experience managers, support leaders, and product teams, CSAT is useful because it is direct, measurable, and easy to operationalize. It tells you whether the moment you just delivered felt good to the customer. That makes it one of the most practical health checks in SaaS and consumer brands, especially when you want to monitor service quality without building a long survey.
Key Takeaways
- CSAT measures point-in-time satisfaction, not long-term loyalty or brand advocacy.
- The standard CSAT formula is satisfied responses divided by total responses, multiplied by 100.
- A 5-point Likert scale is the most practical choice for most CSAT survey programs.
- CSAT works best right after a meaningful interaction, such as checkout, onboarding, or support resolution.
- PollPe helps teams run unlimited CSAT surveys on the free tier, trigger surveys with Business plan webhooks, and analyze results with Aria.
What CSAT Measures (and What It Doesn't)
CSAT measures how satisfied a customer feels about one specific experience. That could be a support reply, a checkout flow, a delivery update, an onboarding task, or a new feature. Because it is tied to a single interaction, it is a point-in-time metric. That is its strength. It gives you a clean read on whether the experience you just delivered met expectations.
What CSAT does not measure is equally important. It does not tell you whether the customer will renew, recommend your brand, or expand their account. A customer can give a high CSAT score after a support interaction and still churn later because of pricing, missing features, poor fit, or a competitor offer. CSAT also does not measure effort. A user may report that they were satisfied after a tedious process because the issue was eventually solved, even if the process itself was painful. That is where CES has a different role.
CSAT should therefore be used as an operational instrument, not a vanity metric. It is best for identifying friction in specific workflows and for tracking whether service or product changes are improving the customer experience. If your question is, "Did this interaction go well?", CSAT is the right tool. If your question is, "Will this customer stay loyal?", you need a broader measurement mix that includes NPS, retention data, product usage, and account health.
In practice, the strongest CSAT programs are narrow and event-based. They ask one clear question, at the right time, to the right audience, then route the insight into a process that fixes the issue. That is how CSAT becomes useful for support teams, product teams, and growth-minded operators.
The CSAT Formula and How to Calculate It
The standard CSAT formula is:
CSAT % = (Satisfied responses / Total responses) × 100
If you use a 5-point Likert scale, most teams count responses of 4 and 5 as satisfied. If you use a different scale, you should define "satisfied" before you start reporting, then keep that rule consistent across time.
Example calculation
Imagine you sent a csat survey and received 200 responses.
- 156 respondents selected 4 or 5
- 44 respondents selected 1, 2, or 3
The calculation is:
156 / 200 × 100 = 78%
So the CSAT score is 78%.
That is the number most leaders want to see in dashboards, weekly reviews, and executive updates. It is simple, comparable, and easy to trend if you keep the question and scale stable.
Common CSAT scale options
| Scale option | Example response labels | How to score | Strengths | Trade-offs |
|---|---|---|---|---|
| 5-point Likert | Very dissatisfied, dissatisfied, neutral, satisfied, very satisfied | Count 4 and 5 as satisfied | Most common, easy to benchmark, easy to explain | Needs consistent wording across every survey |
| 1 to 10 scale | 1 = very poor, 10 = excellent | Often count 8 to 10 as satisfied | Familiar to some teams, more granular | Harder to compare across vendors and teams |
| Emoji scale | Angry, neutral, happy, very happy | Count the top 2 emojis as satisfied | Mobile-friendly, fast for in-app surveys | Less precise for trend analysis |
| Binary scale | Yes / No, satisfied / not satisfied | Count "Yes" or "Satisfied" | Very simple, easy for low-friction feedback | Loses nuance, weak for diagnosing issues |
For most B2B and consumer product teams, the 5-point Likert scale is the best default. It is the easiest to standardize and the most practical for benchmarking over time.
CSAT vs NPS vs CES: When to Use Each
CSAT, NPS, and CES are often grouped together, but they answer different questions. If you want a healthy survey program, you need all three in the right place.
| Metric | Question | Scale | Best For | Cadence |
|---|---|---|---|---|
| CSAT | How satisfied were you with [interaction]? | 5-point Likert or equivalent positive share | Support interactions, checkout, onboarding, feature launches, delivery experiences | After specific events or on a regular operational cadence |
| NPS | How likely are you to recommend us? | 0 to 10 | Brand loyalty, account health, advocacy, expansion signals | Quarterly or biannual for most teams |
| CES | How easy was it to complete [task]? | 5 or 7 point ease scale | Friction reduction, process optimization, support and onboarding efficiency | After tasks, journeys, or workflow changes |
Use CSAT when you want a direct read on satisfaction after a touchpoint. Use NPS when you want to understand overall relationship health and advocacy. Use CES when your main question is about effort and friction.
The three work best together when they are not forced into the same moment. A support team might run CSAT after a ticket closes, CES after a self-service knowledge base journey, and NPS every quarter for account health. That combination gives you both operational detail and strategic direction.
If you want a deeper framework for effort measurement, see our Customer Effort Score guide. If you are building a longer relationship program, review our NPS survey best practices.
CSAT Question Examples That Actually Work
The best csat survey questions are short, specific, and tied to one interaction. They should not try to measure the entire relationship. They should measure the moment.
Here are 10 examples that work across SaaS and consumer brands:
- Post-purchase: How satisfied were you with your purchase experience today?
- Post-checkout: How satisfied were you with the checkout process?
- Post-delivery: How satisfied were you with your delivery experience?
- Post-support: How satisfied were you with the support you received?
- Post-resolution: How satisfied are you with how your issue was resolved?
- Post-onboarding: How satisfied were you with the onboarding experience?
- Post-setup: How satisfied were you with the setup process for your account?
- Feature-specific: How satisfied are you with the new reporting feature?
- Documentation: How satisfied were you with the help article or guide you used?
- Customer success touchpoint: How satisfied were you with your recent call or email exchange with our team?
A few practical rules apply to every question:
- Ask about one event, not the whole relationship
- Keep wording stable so trend data stays clean
- Use the same scale across all recurring surveys
- Pair the score with an open-text follow-up such as "What is the main reason for your score?"
That follow-up matters. The score tells you where the problem is. The comment often tells you why.
What's a Good CSAT Score?
A good CSAT score depends on the industry, channel, and customer expectation. A 75% score in one category may be strong, while the same number in another category may be average. ACSI and Zendesk benchmark reports both show that satisfaction norms vary by sector and by customer journey.
Benchmark table by industry
| Industry | Good CSAT benchmark | What it usually signals | Benchmark note |
|---|---|---|---|
| SaaS | 78%+ | Healthy product experience and service quality | SaaS expectations are high, so consistency matters |
| E-commerce | 75% | Solid purchase and fulfillment satisfaction | Checkout, shipping, and returns affect the score heavily |
| Banking | 76% | Reliable service and trust at key moments | Convenience and clarity are major drivers |
| Retail | 77% | Strong store or support experience | In-store, online, and pickup experiences all shape the result |
| Hospitality | 80%+ | Excellent guest experience | Expectations are high and competition is intense |
The most important benchmark is your own baseline. If your CSAT rose from 70% to 76% after a support workflow change, that is a meaningful operational win even if your industry average is higher. Benchmarking is useful, but trend direction is usually more actionable.
When you report CSAT, always include the survey context. A checkout score is not the same as a ticket-resolution score. A mobile in-app score is not the same as a post-email score. The more specific your survey design, the more honest your benchmark becomes.
How to Run a CSAT Program in PollPe Survey Builder
If you want to run csat survey programs without engineering overhead, PollPe gives you a practical path from launch to analysis.
1) Set the trigger around the moment that matters
The best CSAT programs are event-based. On PollPe Business plan, you can use webhooks, Zapier, Slack, and custom integrations to trigger a survey after a ticket closes, an order ships, an onboarding milestone completes, or a feature is used. That is the right moment to ask because the experience is still fresh.
2) Build the survey with Aria
PollPe's AI assistant, Aria, is available as Standard on all plans and Deep Analysis on Business+. Use it to draft a clean CSAT question, a short follow-up, and a segment-specific version for support, product, or post-purchase flows. If your audience spans regions, PollPe Business+ also supports 15 languages, including Hindi, Telugu, and Tamil, which helps you collect more accurate feedback from diverse customer bases.
This matters because CSAT programs fail when they are hard to localize, hard to manage, or too expensive to scale. PollPe's free plan includes unlimited responses, which is a meaningful advantage over tools that cap free usage, such as Typeform's 10 responses per month free limit and the response caps on SurveyMonkey plans. For a high-volume transactional survey like CSAT, unlimited responses are not a nice-to-have. They are the difference between sampling a few customers and measuring every important interaction.
3) Embed the survey where the experience happens
Use website embed or in-product placement for product flows, onboarding steps, and post-action prompts. For support and account management, trigger a survey immediately after the customer interaction ends. The closer the survey sits to the moment, the more useful the score becomes.
4) Read results in dashboards, not spreadsheets alone
PollPe supports automated dashboards, and on Business+ you also get cross-tabulation, advanced filters, and custom dashboards. That means you can compare CSAT by plan, region, agent, product area, or audience type without manually stitching reports together. If you are reviewing support quality, this saves time. If you are reviewing product adoption, it helps you isolate which feature path is creating friction.
See current plan details on PollPe pricing.
5) Segment, act, and close the loop
A CSAT score becomes valuable only when it leads to action. Segment by audience, look for patterns in low scores, read comments, and route detractors to the right owner. Support should own service issues. Product should own workflow friction. Customer success should own account-level follow-up. The best teams treat low CSAT as an operational signal, not a report to archive.
If you are ready to launch your first survey, run unlimited CSAT surveys free at app.pollpe.com.
Common CSAT Mistakes
Even strong teams make CSAT mistakes. Most of them are easy to avoid once you know what to look for.
Asking at the wrong time A survey sent too late loses context. A survey sent too early can miss the actual experience. Trigger CSAT right after the meaningful event.
Changing the scale or wording every month If the question changes, the benchmark becomes unreliable. Keep the wording and response scale consistent.
Ignoring detractors and comments The score is the summary. The comments are the diagnosis. If you do not read the open text, you are missing the main value of the survey.
Surveying everyone all the time Broad, untargeted surveys create noise and fatigue. CSAT works best as an event-based measure with clear audience rules.
Collecting scores but not following up When customers give low scores, someone needs to respond. Set a workflow for escalation, review, and resolution. If a customer took the time to answer, the company should take the time to act.
FAQ
What is the minimum sample size for CSAT?
There is no universal minimum, but 30 to 50 responses per segment can give you a directional read. For stronger trend confidence, aim for 100 or more responses in the same segment or workflow. If you are comparing teams, regions, or product flows, make sure the sample mix is reasonably balanced.
What is the ideal CSAT scale?
For most teams, a 5-point Likert scale is the best choice. It is easy to answer, easy to explain, and easy to benchmark over time. If you use another scale, define the threshold for "satisfied" before you start reporting.
What response rate is good for a CSAT survey?
Transactional CSAT surveys often perform better than broad brand surveys. A 15% to 30% response rate is a solid range for targeted follow-up, and higher rates are possible when the survey is sent immediately after the interaction. The more specific and timely the ask, the better the response quality tends to be.
Can I trigger CSAT after specific events in PollPe?
Yes. On the Business plan, you can trigger CSAT after specific events using webhooks, Zapier, and custom integrations. That is useful for support closures, checkout completion, onboarding milestones, and product usage events.
How should I act on CSAT results?
Start with the lowest scores and read the comments attached to them. Then segment the data by team, product area, plan, or region. Fix the highest-frequency issue first, measure again, and close the loop with affected customers. CSAT is strongest when it drives a clear operational action.
Conclusion
CSAT is one of the most useful customer experience metrics because it is simple, specific, and actionable. It tells you whether a single interaction met expectations, and that makes it ideal for support, onboarding, product, checkout, and post-purchase workflows. The score matters, but the real value comes from consistent measurement, smart segmentation, and fast follow-up.
If you are building a serious customer feedback program, use CSAT alongside NPS and CES, not instead of them. And if you want to start quickly without hitting response caps, PollPe gives you a practical path forward with unlimited responses on the free tier, Aria for survey generation, and Business features like webhooks, Zapier, multi-language support, and advanced analytics.
Run unlimited CSAT surveys free at app.pollpe.com and turn every customer interaction into a measurable signal.
