CSAT Customer Satisfaction Calculation: Formula & Examples

CSAT customer satisfaction calculation means dividing positive survey responses by all valid submitted responses and multiplying by 100. On a five-point scale, a common definition of positive is a rating of 4 or 5. The result is a percentage, not an average rating. To make it useful, report the scale, threshold, touchpoint, period, and number of responses alongside the score.

CSAT customer satisfaction calculation: the standard formula

The standard CSAT formula is positive survey responses divided by valid survey responses, multiplied by 100. On a five-point scale, teams commonly count ratings of 4 and 5 as positive. The calculation is simple; the important part is defining what “positive” means and keeping that definition consistent.

CSAT (%) = (positive responses ÷ valid survey responses) × 100

For example, if 80 of 100 people who submitted a rating chose one of your positive options, the calculation is 80 ÷ 100 × 100 = 80% CSAT. The denominator is the submitted ratings, not every person who was invited to answer.

CSAT stands for customer satisfaction and is usually used to understand satisfaction with a particular product, service, or interaction. That scope matters. A rating after a delivery, a support conversation, and an onboarding session may reflect different experiences. If you blend them into one figure, you can make it harder to spot which experience needs attention.

Before sending a survey, write down the exact question and the scoring rule. A question such as “How satisfied were you with your support conversation?” ties the rating to a particular event. A broad question about overall satisfaction may capture several experiences at once, making a low score harder to interpret or act on.

Include the calculation rule in the metric definition your team uses. For example: “Support CSAT is the percentage of submitted five-point ratings of 4 or 5 after a support conversation.” That short description makes it easier for teammates to calculate the same metric and to understand what the number represents.

The score matters because it can help your team notice changes in how customers experience a specific interaction. But a percentage does not explain why a customer was satisfied or dissatisfied. Treat it as a signal to investigate, not as a complete account of service quality.

How to calculate CSAT score out of 5 and out of 10

On a five-point scale, a common calculation counts ratings of 4 and 5 as positive, then divides that count by all submitted ratings. On a ten-point scale, the positive cutoff needs to be stated explicitly; one example uses 7 and above. Keep the same scale and cutoff over time so trend comparisons remain meaningful.

For a five-point survey, a typical set of labels is very dissatisfied, dissatisfied, neutral, satisfied, and very satisfied. With the common threshold, the final two options count as positive. The other responses remain in the denominator, including neutral ratings, because they are valid submitted responses.

For a ten-point survey, do not assume that every team uses the same cutoff. Some teams may define positive as 9 or 10; another example counts 7 and above. Those rules will classify the same response set differently, so publish the cutoff with the result. A reader should not have to guess which ratings counted.

The scale and wording also affect how easy a survey is to answer. A compact scale may be quicker to understand, while a longer scale gives respondents more choices. Whichever format you choose, make the labels clear and avoid changing the scale halfway through a reporting period.

A stable definition is especially important when comparing channels, teams, or time periods. If one report counts only the highest answers and another counts a broader positive group, the percentages are not directly comparable. The apparent movement could come from a changed rule rather than a change in customer experience.

Write down three things before collecting ratings: the question, the available scale, and the positive cutoff. Then keep them together in the report or dashboard description. If you have a reason to change the method, mark the change and treat the new results as a different series rather than quietly joining them to the old one.

Worked example: turn individual ratings into a CSAT percentage

To calculate CSAT from a list of ratings, first mark which responses meet your positive threshold. Count those responses, divide by all valid submitted ratings, and multiply by 100. Then label the result with the touchpoint and period. This makes the percentage easier to reproduce and less likely to be mistaken for an overall company score.

Suppose a support survey uses a five-point scale and the team has 1,000 submitted responses. If 550 of those responses are ratings of 4 or 5, the calculation is:

550 positive responses ÷ 1,000 valid responses × 100 = 55% CSAT

The 1,000 in the denominator includes all submitted ratings, not just the positive ones. Ratings below the chosen positive cutoff still count as responses. If there were unanswered survey invitations, those invitations are not submitted ratings and do not belong in the CSAT denominator.

That result should not stand alone as “55% customer satisfaction” if it actually describes only a particular interaction. A clearer label would be “support conversation CSAT, five-point scale, ratings of 4 and 5 counted as positive, for the stated reporting period.” Naming the touchpoint and period helps someone reading the report understand its scope.

You can reproduce the calculation in a spreadsheet by counting responses that meet the threshold and dividing by the number of valid rating entries. Check that blank cells and comments without ratings are not included in the count of submitted ratings. If a question allows a respondent to skip the rating and leave a comment, treat those answers according to a written reporting rule.

It is also useful to keep the raw response count next to the percentage. A percentage can look precise even when it comes from a small number of submissions. The count helps the reader see how many ratings contribute to the result and provides context when comparing it with another period or touchpoint.

Finally, keep the calculation separate from interpretation. The arithmetic tells you the share of responses classified as positive. It does not prove why customers gave those ratings, whether every customer had the same experience, or what change will improve future results. Use comments and operational context to decide what to investigate next.

CSAT percentage vs average rating: report both carefully

A CSAT percentage counts the responses that meet a defined positive threshold. An average rating uses every numeric response in the calculation. These are different summaries of the same survey data: the percentage shows the share classified as satisfied, while the average describes the mean rating on the scale.

For example, a five-point survey could have an average rating of 3.70 out of 5. That number is not a CSAT percentage. To calculate the percentage, count the responses meeting the agreed cutoff—commonly 4 and 5—and divide that count by all submitted ratings.

The average can add context because it reflects movement across all rating values. A change in the number of neutral or low ratings can affect the average even if the count of positive responses changes little. Conversely, a positive-response percentage focuses on the selected threshold and does not show how far above or below it the other ratings fall.

If you report both metrics, name them precisely and include the scale. For instance, keep “CSAT: percentage of five-point ratings of 4 or 5” separate from “average rating: mean of submitted five-point responses.” Avoid putting an average under a chart or label called “CSAT %,” because readers may assume it represents a share.

To calculate a simple average, add all valid numeric ratings and divide by the number of valid numeric ratings. If your survey uses a consistent five-point scale, state that scale and the number of ratings included. The average should use the same set of valid submitted ratings as the percentage unless you have a clearly documented reason for using a different set.

If you need an average across groups with different numbers of responses, use a weighted average rather than averaging the group averages equally. Multiply each group’s average by its number of valid responses, add those products, and divide by the combined response count. This gives more influence to groups with more responses. Keep the method and group counts visible so the calculation can be checked.

Handle nonresponses, duplicates, and small samples without overstating results

Use submitted ratings as the CSAT denominator; unanswered survey invitations are not survey responses. Report the number of submitted ratings and the number of invitations separately when you can, so readers can see the response rate as well as the score. Decide how to treat repeat submissions consistently and disclose the rule.

A response rate and a CSAT score answer different questions. The response rate describes how many invited people submitted a response under your chosen method. CSAT describes the share of submitted ratings that met your positive threshold. Do not substitute one for the other or combine them into a single figure.

To report response rate, define what counts as an invitation and what counts as a response for that survey. For example, be clear about whether a partial survey counts as a response, and which survey question is being measured. Consistency matters when surveys run through different channels or contain multiple questions.

An unanswered invitation does not become a dissatisfied response. Putting it in the CSAT denominator would change the metric from the share of submitted ratings that are positive to a different calculation. Keep invitations, submitted ratings, and positive ratings as distinct counts in your reporting.

Repeat responses need a written policy too. A customer might submit more than one rating, such as after separate support interactions, or might submit more than one rating for the same event. Decide whether the unit you are measuring is the customer, the interaction, or the survey submission. Then use that unit consistently and avoid removing responses without a clear, documented reason.

There is no single sample-count rule that makes every CSAT result reliable. A small count can still provide useful feedback about an individual case, but it is a weak basis for a broad conclusion about all customers. Show the response count, avoid presenting a small set of ratings as a precise read on the whole customer base, and look for supporting information before making a major change.

Also be cautious about who chooses to respond. People with particularly good or bad experiences may be more motivated to submit feedback, while other customers may not answer. A score therefore describes the responses you received; it may not represent every invited customer equally. Track response counts and response patterns alongside the percentage.

Segment scores and turn low ratings into follow-up actions

Break CSAT results down by relevant touchpoint, support channel, product area, customer segment, or reporting period. An overall percentage can hide a difficult part of the journey. Pair low ratings with an optional comment, review recurring causes, and decide who will follow up or address the underlying issue.

Start with the experience the survey measures. If you ask after a support interaction, group those responses separately from ratings about checkout or delivery. Then look for useful breakdowns, such as channel or product area, while keeping enough context to understand what each group includes.

A segment can reveal a pattern that an aggregate result conceals. For example, a stable overall score could coexist with a problem in one support channel or product area. The purpose of segmentation is not to produce as many slices as possible; it is to locate a meaningful difference that your team can investigate.

Keep the survey question focused on one experience. A short question with an optional open text field can let a customer explain what affected the rating without making every respondent complete a long questionnaire. Comments are especially useful when the number alone cannot distinguish between a slow response, an unclear answer, or a product problem.

Create a practical review path for low ratings. Someone should read the rating and any comment, decide whether the customer needs a direct reply, and record an issue for the relevant team when the cause is broader than one conversation. The follow-up can acknowledge the customer’s concern, clarify what happened, or explain the next action without promising an outcome the team cannot deliver.

Look for repeated causes rather than reacting to every isolated score as if it were a trend. If customers repeatedly mention the same friction point, investigate the process or content behind it. Then review later feedback to see whether the experience changed. Close the loop with the customer when you have a useful update, and close the internal loop by recording what was changed.

CSAT is most useful when it leads to a decision. The decision might be to improve a help article, investigate a recurring delivery issue, coach a support workflow, or ask a follow-up question. If no one reviews the comments or owns the next step, collecting more ratings alone will not explain what customers need.

What is a good customer satisfaction score (CSAT)?

A CSAT score should be judged against the experience it measures, the survey method, and your own results over time. A range of 75–85% is cited as good in one benchmark, but it is not universal. Compare like with like, and use comments and other relevant measures to understand what a percentage cannot show.

A benchmark can be a starting point for a question, not a verdict on your service. Scores can differ with industry, survey wording, channel, and which customers choose to respond. Before comparing your result with an external range, check that the scale, positive cutoff, touchpoint, and calculation method are comparable.

Your own trend is often more useful when the measurement stays consistent. Compare the same type of interaction across periods, using the same scale and cutoff. If the score moves, check the response count and survey context before deciding the cause. A change in the mix of respondents or experiences could affect the result.

CSAT is a snapshot of reported satisfaction with a particular experience. It does not capture every nuance, explain the cause of a rating, or by itself represent the customer relationship over time. Use the number alongside customer comments and operational information, and consider other measures when they answer a different question.

Avoid changing a process just to move the percentage. A higher share of positive ratings does not explain whether customers’ underlying problems have been resolved. Pair the metric with what customers say and what your team observes in the interactions. That gives you a better basis for prioritizing fixes than a target score on its own.

Frequently asked questions

What response rate should I report with CSAT?

Report the response rate using a clearly defined invitation count and response count. There is no single rate that fits every survey channel and customer group. Keep the method consistent, and show the counts alongside the rate so readers can see how many customers were invited and how many responded.

If the survey has multiple questions, state whether the rate refers to people who submitted any response or people who answered the specific rating question. The second measure can be more useful when some customers skip the rating but leave other feedback.

Should unanswered survey invitations count in the CSAT denominator?

No. The standard CSAT denominator is the number of valid submitted survey responses. An unanswered invitation is not a rating and should not be counted as either positive or negative. Keep the number of invitations separate so you can report response rate as a distinct measure.

How do I calculate a weighted average rating alongside CSAT?

For a weighted average across groups, multiply each group’s average rating by that group’s number of valid ratings. Add those products and divide by the total number of valid ratings across the groups. Report the scale, group counts, and method. Keep this average separate from CSAT, which is the percentage of responses meeting your stated positive threshold.

Is 80% CSAT good for a small support team?

An 80% result can be a useful signal, but it is not enough on its own to judge a small team’s service. Check the number of submitted ratings, the touchpoint, and the survey method. Compare with the team’s own results gathered using the same scale and threshold, and read comments for context.

How often should I ask the same customer for a CSAT rating?

Set a frequency rule that fits the experience you are measuring and avoid repeatedly asking the same person about the same event. A survey after a discrete support interaction can be timed while the conversation is fresh; a longer-term product experience may need more time before asking. Keep the rule consistent and watch for signs that customers are being over-surveyed.

Make the result useful

Use a consistent question and scoring rule, report the percentage with its response count and scope, and assign someone to review feedback and follow up. If you are also evaluating support tools, compare AI chatbots for customer service against the workflow your team needs.