CSAT Calculator: Formula, Examples, and Score Guide

A CSAT calculator works out the percentage of survey respondents who gave a satisfied rating. CSAT stands for customer satisfaction, and on a standard five-point survey, ratings of 4 and 5 are commonly counted as satisfied. Divide that count by all valid responses to the same survey and multiply by 100. The result describes the people who answered; it does not automatically represent every customer.

What does CSAT mean, and how does it differ from NPS and CES?

CSAT measures how satisfied customers say they are with a product, service, or particular interaction. It is useful when you want feedback about a defined experience, such as a support conversation or purchase. NPS asks about loyalty and likelihood to recommend, while CES focuses on how easy it was to resolve an issue.

The wording and timing of a satisfaction question set the scope of the score. “How satisfied were you with the help you received?” asks about support. “How satisfied are you with this product?” asks about a wider experience. Neither is a complete measure of how every customer feels about your business.

That distinction matters when you review results. A post-support survey can help you see whether customers felt satisfied with the interaction, but it does not directly tell you whether they will remain customers or how much effort the issue took to resolve. Those are different questions, suited to different measures.

Choose the metric based on the decision you need to make:

• Use CSAT to assess satisfaction with a specific product, service, or interaction.
• Use NPS when you want to ask about customer loyalty or likelihood to recommend.
• Use CES when you want to understand how easy customers found it to get an issue resolved.

For a support team deciding whether a change to a reply process helped, an interaction-level CSAT question may fit. For a team investigating how much effort customers experience, a question about ease may be more relevant. Avoid treating one score as a substitute for the others. A high interaction satisfaction score does not, by itself, answer every question about loyalty or effort.

How to calculate CSAT on a five-point scale

For a standard five-point survey, calculate CSAT as satisfied responses divided by all valid responses, multiplied by 100. A common definition of “satisfied” is a rating of 4 or 5. For example, if 42 of 60 respondents chose either rating, the CSAT score is the proportion of those 60 answers that met the satisfied threshold.

The formula is:

CSAT (%) = satisfied responses ÷ total valid survey responses × 100

On a five-point scale, the response labels commonly run from very unsatisfied at 1 to very satisfied at 5, with 4 representing satisfied and 3 neutral. Under the usual threshold, ratings of 4 and 5 count as positive. Decide on that threshold before you calculate or compare results.

Worked example

Suppose 60 customers answer the same post-support satisfaction question. Of those answers, 42 are ratings of 4 or 5. Divide 42 by 60, then multiply by 100:

42 ÷ 60 × 100 = the percentage of responses counted as satisfied

The result means that the calculated percentage of respondents in that survey gave a rating counted as satisfied. The remaining responses still belong in the denominator, including neutral or dissatisfied ratings. Excluding them would make the percentage look higher than the share of all respondents who were satisfied.

To calculate a score from your own survey:

1. Choose the survey question and reporting period you want to assess.
2. Count valid answers to that question in that period.
3. Count the answers that meet your stated definition of satisfied.
4. Divide satisfied answers by all valid answers.
5. Multiply by 100 and report the percentage with its response count.

For example, if you use a different scale, define which choices count as positive before you collect or report results. A one-to-seven or one-to-ten scale can also measure satisfaction, but the five-point threshold of 4 and 5 should not be copied across automatically. A yes-or-no question uses a different response format, so state clearly which answer is counted as satisfied.

Who belongs in the denominator—and what the score says

The denominator is the number of valid survey answers to the question you are calculating, not the number of people invited to answer. CSAT describes the responses received, rather than the full customer base. Pair the percentage with the response count so readers can see how many answers it represents.

In the worked example, 60 people answered and 42 selected a satisfied rating. The result is the share of those 60 respondents, not the share of everyone who has bought from your store or contacted support. Customers who were invited but did not respond have not supplied a satisfaction rating and do not belong in the calculation.

That is why the denominator deserves as much attention as the numerator. If you divide satisfied ratings only by satisfied-plus-neutral ratings, or leave dissatisfied answers out, you are no longer calculating the share of all survey respondents who were satisfied. Keep all valid answers to the same survey question in the denominator.

Report the response volume alongside the percentage. For instance, reporting the CSAT percentage alongside “42 satisfied responses out of 60 answers” is more useful than giving the percentage alone. A percentage without its count hides how many answers support it. A small set of responses can move sharply when one answer changes, so avoid reading a small change as a clear signal without looking at the underlying responses and context.

For practical reporting, record:

• The score and the number of valid responses.
• The exact question and the scale used.
• The response period and when the survey was sent.
• The channel or touchpoint the survey followed.
• The threshold used to define a satisfied answer.

There is no universal rule in this calculation for every possible partial or duplicate submission. Establish a consistent handling policy for your survey data and apply it the same way across the periods you compare. The important point is to be clear about what counts as a valid response, rather than changing the rule to suit a particular result.

A score is a useful summary, not an explanation. It tells you what share of respondents met your satisfaction threshold. It does not tell you why someone chose a rating, whether nonrespondents would answer differently, or whether the sample represents all your customers. Comments, response counts, and the circumstances of the survey help put the percentage in context. For more examples of the calculation, see the CSAT score calculation guide.

Why survey design changes the result

A CSAT result depends on the question, scale, threshold, and moment when customers are asked. Decide these before collecting answers, then keep them stable when tracking a trend. For support feedback, a short, specific question sent after a defined interaction is easier to interpret than a broad question with unclear timing.

Start with a question that names the experience you want to measure. “How satisfied were you with the support you received?” is more specific than “How satisfied are you?” A clear question helps respondents focus on the same part of the experience and helps your team know what a score refers to.

Choose a response scale that is practical for your customers and reporting. Five-point, seven-point, and ten-point scales are all used for satisfaction surveys; yes-or-no questions are another option. There is no single scale that works for every use. What matters for a trend is that the scale and the definition of a positive response do not quietly change between reporting periods.

Survey timing also shapes what the response is about. If you want to measure satisfaction with support, send the question after the support interaction or resolution, rather than at an unrelated point in the customer journey. If you want a wider view of customer satisfaction, use a question that clearly asks about that broader experience and define the reporting period.

Keep a simple survey record for each feedback stream:

• Question wording and answer choices.
• The rule for which answers count as satisfied.
• When the survey is sent and the reporting window.
• The support channel or customer touchpoint.
• Responses received and invitations sent, if you track both.

Channel comparisons need special care. You can compare channels when the question, scale, satisfaction threshold, and measurement window are consistent. Even then, differences in channel and response rates can distort a comparison. A score from customers who answer an email survey may not be directly comparable with one from customers who answer a prompt in a chat, especially if the survey experience or timing differs.

If you change the wording or scale, treat it as a change in measurement. Note when it happened and avoid presenting the resulting figures as if nothing changed. You may still learn from the new survey, but a trend across the change needs a clear explanation.

Common CSAT calculation and comparison mistakes

The most common calculation mistake is using the wrong denominator: dividing by invitations or positive answers instead of all valid responses to the survey. Comparison mistakes often come from mixing questions, scales, thresholds, channels, or time periods. Calculate consistently first; only then decide what a change might mean.

Watch for these errors when you build a report:

• Counting invitations as answers. People who received a survey but did not answer have not provided a rating. Keep them out of the response denominator.
• Leaving out negative or neutral ratings. The denominator should include all valid answers to that survey question, not just ratings you count as positive.
• Changing the satisfaction threshold. If ratings of 4 and 5 count as satisfied in one period but a different set counts in another, the resulting percentages are not directly comparable.
• Mixing scales. A rating of 4 on one scale may not mean the same thing as a rating of 4 on another. Define positive answers for each scale and keep the format stable for a trend.
• Combining different questions. Satisfaction with a support reply and satisfaction with a product are different topics. Keep those results separate unless you have a clear, consistent method for combining them.
• Ignoring timing or channel. A prompt sent right after a resolved case measures a different moment from a general survey sent later. Record the timing and channel before comparing results.

Another source of confusion is calling an average rating out of five “CSAT” without saying how it was calculated. An average is the sum of all ratings divided by the number of responses. The percentage satisfied is the number of responses that meet your positive threshold divided by all responses, multiplied by 100. They are different calculations and can produce different-looking numbers from the same responses.

If you report an average as well as the percentage, label each one clearly. For example, “average rating out of five” and “share of responses rated 4 or 5” tell readers what each figure means. Do not compare an average directly with a percentage as though the values shared a scale.

Finally, avoid treating a score as proof of a cause. If CSAT falls after a process change, the timing may justify investigating the change, but the percentage alone does not show what caused the difference. Check the response count, customer comments, and whether the survey method stayed consistent before deciding what to change.

Turn CSAT trends and comments into the next support fix

CSAT is most useful when a team turns the result into a specific follow-up, not when it is just a number in a dashboard. Review the trend beside the response count and customer comments, look for recurring causes of dissatisfaction, and choose an issue the team can investigate or address.

A practical review can follow this sequence:

1. Check the calculation. Confirm that the responses belong to the same question and reporting period, and that the satisfaction threshold has not changed.
2. Read the comments. Group comments by recurring theme, such as unclear instructions, an unresolved issue, or a delayed reply. Do not assume one comment explains a wider pattern.
3. Look at the touchpoint. Identify whether feedback relates to a support interaction, product experience, or another specific part of the journey.
4. Choose a focused issue. Pick one recurring, actionable cause to investigate rather than trying to address every theme at once.
5. Follow up where appropriate. Dissatisfied customers may be able to explain what happened and what they still need. Make the follow-up useful, not just a request to change a rating.
6. Review the result using the same method. Keep the question, scale, threshold, timing, and reporting window stable so you can interpret later responses in context.

For a support team, useful questions include: Was the customer’s issue fully resolved? Did they receive an answer that addressed the question? Did the response explain what would happen next? These checks help connect a rating to the work the team can review, without assuming that every low score has the same cause.

Close the loop with customers when their feedback leads to a change. A short explanation of what was changed, or what the team is doing next, shows that the response was considered. Internally, note the issue, the change made, and the method used to review later feedback. That makes it easier to learn from the work even if the score does not move immediately.

Support automation can be one part of this workflow, but it does not calculate CSAT or guarantee a better score. For example, momo answers from a business’s own content, cites sources when confident, and opens a ticket for the team when it is not sure. A support team could review feedback tied to those conversations to spot recurring questions or unresolved issues, then decide what to improve in its content or process. Human review still matters when deciding what a customer’s rating means and what action to take.

Frequently asked questions

These answers clarify how to read a CSAT percentage, choose the right response threshold, and compare survey results. They also explain why a score is not, on its own, a verdict on overall customer experience. Use the same method consistently and include the response count when sharing results.

What is the CSAT score range?

When reported as a percentage, CSAT runs from 0% to 100%, with 100% representing the highest possible share of satisfied responses. It is calculated from the answers received, using the satisfaction threshold you defined. The range does not mean that a particular score has the same significance for every team or survey.

What counts as a satisfied response on a five-point CSAT survey?

Ratings of 4 and 5 are commonly counted as satisfied on a standard five-point scale, where 4 means satisfied and 5 means very satisfied. Set the threshold before reporting results. If your survey uses different labels or a different scale, define which answers count as positive instead of assuming the five-point rule applies.

Can CSAT be reported as an average rating instead of a percentage?

Yes, but label it as an average rating, not as the percentage of respondents who were satisfied. To get the average, add all ratings and divide by the number of responses. To get percent satisfied, divide responses meeting your positive threshold by all valid responses and multiply by 100. They summarize the answers in different ways.

What is a good CSAT score?

A score alone is not enough to decide whether customer experience is good or poor. A benchmark around 75% is sometimes cited as a general reference, and the relevant range can vary by industry and service type. Compare your result with your own consistent historical measurements, inspect the response count, and read the comments before choosing a target or conclusion.

When should a support team send a CSAT survey?

If you want feedback on a support interaction, send the survey after that interaction or its resolution. That timing keeps the question connected to the experience you want to assess. If you are measuring a broader view, choose wording and timing that fit that purpose, then keep them stable when comparing results.

Can I compare CSAT across support channels?

You can compare channels when the survey question, scale, satisfaction threshold, and measurement window are consistent. Still, channel and response-rate differences can distort the comparison. Report the response count and channel alongside the score, and be cautious about treating a difference as a change in service quality without checking the survey context.

Put the result to work

A CSAT calculation is straightforward; interpreting it well requires a consistent question, a clear denominator, and context for the responses. Start with one defined support interaction, review the answers and comments together, then choose a practical issue to investigate. For another walkthrough, read how to calculate CSAT. If you are considering an AI support workflow, try momo free.