What is CSAT, and what does a CSAT score measure?
CSAT stands for customer satisfaction score. A survey asks someone to rate satisfaction with a stated experience, product, or service. The resulting percentage depends on the scale and the definition of a satisfied response. On a five-point scale running from very dissatisfied to very satisfied, the common top-two-box calculation counts ratings 4 and 5 as satisfied.
SurveyMonkey’s documentation separates this percentage calculation from an average rating. That distinction matters: an average of 3.8 out of 5 and a CSAT of 70% can describe the same response set. They use different calculations and should keep different labels in your report.
For a small SaaS, choose an experience someone can actually judge. Completing a first import, receiving help with a failed task, or finishing a reporting cycle provides more context than an unexplained score request immediately after signup. Define whose experience the survey represents before choosing where to display it.
CSAT score calculator
Enter response counts for one defined five-point survey wave. This calculator counts ratings 4 and 5 as satisfied and includes valid ratings 1 through 5 in the denominator. It excludes unanswered invitations because they are not ratings. Do not enter percentages into the count fields or combine different survey scales.
The defaults are an original fictional example with 20 responses. The calculator does arithmetic only; it does not collect feedback, identify customers, establish whether your sample is representative, or predict renewals. An empty survey has no defined CSAT, while a completed survey with no satisfied respondents has a valid score of zero.
Enter counts for one five-point survey wave. Ratings 4 and 5 count as satisfied; all five ratings remain in the denominator. Defaults are fictional. Calculations stay in your browser; no responses are submitted.
- CSAT score
- 70.00%
- Satisfied responses
- 14
- Valid responses
- 20
JavaScript is required to update this calculator. The formula and worked example below remain readable without it.
CSAT formula with a worked SaaS example
CSAT (%) = satisfied responses ÷ all valid rated responses × 100. In the fictional BriefBoard example, ratings 4 and 5 have eight and six responses. The numerator is 14, the total is 20, and CSAT is 14 ÷ 20 × 100 = 70%. Neutral and dissatisfied ratings stay in the denominator.
The weighted rating sum is 76, so the average is 76 ÷ 20 = 3.8 out of 5. Dividing that average by five would produce 76%, which is not the same top-two-box CSAT calculation. State the formula when an exported dashboard calls several different measures a satisfaction score.
Suppose 80 eligible people were invited and these 20 answered. The rated-response rate is 25%, while CSAT remains 70% among respondents. The views of the other 60 people remain unknown. These invented counts explain the calculation; they are not ShowMeYourSaaS customer results or an industry benchmark.
| Rating | Count | Counts as satisfied? |
|---|---|---|
| 1 — very dissatisfied | 1 | No |
| 2 — dissatisfied | 2 | No |
| 3 — neither satisfied nor dissatisfied | 3 | No |
| 4 — satisfied | 8 | Yes |
| 5 — very satisfied | 6 | Yes |
| All valid ratings | 20 | 14 satisfied; CSAT 70% |
Write a focused CSAT question and useful follow-up
Ask about one experience and make the reference clear. Our original example is: ‘Thinking about the project brief you just submitted, how satisfied were you with that submission experience?’ Use consistently ordered, fully labeled response choices. A respondent should not need to infer whether a higher number means a better or worse experience.
Follow with an optional neutral prompt such as ‘What most affected the rating you chose?’ An additional task question can ask what the person was trying to accomplish. Avoid turning the follow-up into a feature vote or asking someone to justify why they did not give a higher score.
Write down when invitations are sent and who can receive them. If you survey only successful completions, you miss people who were blocked earlier. That can be a deliberate experience survey, but its report should say so. Coordinate invitation frequency across support, product, and renewal messages to avoid repeatedly asking the same person.
CSAT vs NPS: choose the question you need answered
CSAT asks about satisfaction. Net promoter score asks about likelihood to recommend and uses different response groups and arithmetic. NPS can be used in relationship or experience research, so the survey context still matters; its name alone does not tell you what was measured.
Use the NPS guide for its zero-to-ten scale and promoter-minus-detractor formula. Do not subtract dissatisfied CSAT responses to invent an NPS, or compare a CSAT percentage directly with an NPS point score. A person can be satisfied with one support interaction while still having a poor overall product experience.
Neither score proves task completion, product-market fit, or retention. Connect the feedback with the experience in the customer journey map, then inspect actual outcomes using a consistent account or person unit. A survey response is evidence of what that respondent reported at that time.
Interpret changes without losing the response counts
There is no universal score that makes every small SaaS successful. Compare waves only when question wording, scale, eligible population, trigger, and collection window are sufficiently comparable. A changed invitation rule can change the result even when the product did not improve.
Small waves move in large steps. In the fictional 20-response example, changing one rating from 3 to 4 increases CSAT by five percentage points. Keep the distribution and comments visible rather than reporting a percentage alone. A shift deserves investigation; it does not identify a cause by itself.
If two comparable waves have 14 satisfied responses out of 20 and two out of four, their pooled CSAT is 16 ÷ 24 = 66.67%, not the unweighted average of 70% and 50%, which is 60%. Pool only when a combined population makes sense, and retain the separate waves so the weighting remains inspectable.
Turn a score into a bounded improvement decision
Group the explanations by concrete task failure and record what is observed versus inferred. A complaint about a missing confirmation might suggest a delivery problem, a visibility problem, or a misunderstanding. Review a representative example before choosing the fix. Do not discard low ratings because their comments are inconvenient.
Assign an owner and a review question: can the person now recognize that a brief was received, for example? Check the task result after the change and keep the survey setup consistent. If you consider a randomized comparison, the A/B testing guide explains sample planning and why tiny response sets should not be treated as a reliable winner declaration.
Download the CSAT survey and calculation worksheet
The original worksheet includes the five-point question example, response counts, average-versus-CSAT arithmetic, pooling example, and blank fields for scope, timing, follow-up, and a review decision. Sources were checked on October 27, 2026.