How is CSAT calculated?

Divide the number of positive responses by all responses on the declared rating scale, then multiply by 100. Using the default method here, positive means ratings of 4 or 5 on a 1–5 scale.

What counts as a positive CSAT response?

This calculator treats ratings of 4 and 5 as positive. Other thresholds and scales exist, so the team must declare its definition and avoid mixing methods silently.

What is the difference between CSAT and NPS?

CSAT measures satisfaction with a named interaction or experience. NPS measures willingness to recommend and is intended as a relationship-level loyalty signal. They answer different questions.

When should a support team send a CSAT survey?

Send it close enough to the named interaction for useful customer recall. Keep the timing consistent and document it, because timing can influence responses and comparisons.

CSAT Score Calculator: Measure a Support Moment, Not a Brand

CSAT is the percentage of survey responses that meet a declared satisfaction threshold for one named support interaction. Using the default method here, divide ratings of 4 or 5 by all valid 1–5 ratings, then multiply by 100. Keep the rating distribution visible so the percentage leads to learning, not agent score gaming.

How does the CSAT calculator work?
What should the survey ask and when?
How do CSAT, NPS, and CES differ?
Which biases can distort CSAT?
How should a support team act on CSAT?
Sources
FAQ

How does the CSAT calculator work?

CSAT calculation uses one declared rule: divide positive responses by all responses on the chosen scale, then multiply by 100. On this page, the default scale is 1–5, and positive means a rating of 4 or 5. This approach is consistent with common CSAT guidance from Qualtrics.

Use the calculator in five steps:

Add the count for every rating from 1 through 5.
Declare the positive threshold before reviewing the result.
Add ratings 4 and 5 to get the positive-response count.
Add all 1–5 responses to get the total response count.
Divide positive responses by total responses and multiply by 100.

Formula:

CSAT = (responses rated 4 or 5 ÷ all 1–5 responses) × 100

Suppose the rating counts are:

Rating	Responses
1	3
2	4
3	8
4	35
5	50
Total	100

There are 85 positive responses: 35 ratings of 4 plus 50 ratings of 5. The result is:

85 ÷ 100 × 100 = 85.0% CSAT

The 85.0% figure is useful, but it is not the whole result. Keep the response count and full distribution beside the percentage. A score built from mostly 5s communicates something different from one built from many 4s, even when the positive percentage is the same.

Other survey scales and positive thresholds exist. A team may use a different range or define positive responses differently. That choice can be valid, but it must be declared and applied consistently. Do not silently compare a 1–5, 4–5 threshold with another scale or threshold.

What should the survey ask and when?

The survey should name one specific interaction or experience so the answer reflects a support moment rather than a vague opinion of the brand. The customer should be able to identify what is being rated without guessing which part of the journey the question refers to.

Timing should stay close enough to the interaction for useful recall. Send the question after the named support event, while the resolution or handoff is still clear. If timing changes, record that change because it can affect how customers respond.

Before reporting results, document the survey design:

The interaction being measured
The rating scale and positive threshold
The channel used to collect responses
The timing of the survey
Any exclusions
The response count and rating distribution

This discipline makes the result easier to interpret and repeat. It also prevents a team from changing the calculation rules after seeing an unfavorable score. SurveyMonkey’s CSAT guidance is a useful reference for keeping the measure focused on customer satisfaction.

How do CSAT, NPS, and CES differ?

CSAT, NPS, and CES measure different customer questions. They should support one another, but they should not be merged into one target or treated as interchangeable.

Metric	Main question	Best use	What it should not replace
CSAT	How satisfied was the customer with a named interaction?	Transaction-level support feedback	Relationship-level loyalty
NPS	How likely is the customer to recommend?	Relationship-level loyalty signal	Satisfaction with one case
CES	How easy or difficult was it to complete a task?	Process friction and effort	Overall satisfaction or recommendation

CSAT is strongest when the team wants to understand a particular support moment. NPS looks at the broader customer relationship. CES focuses on effort. A customer can be satisfied with a resolution, still find the process difficult, and remain uncertain about recommending the company.

Keep the metrics in separate reports with separate owners and actions. Use SellerTrove’s NPS calculator when the question is customer loyalty rather than interaction satisfaction. For broader support workflows, explore the Customer Service collection.

Which biases can distort CSAT?

CSAT can move because of who responds, when they respond, and how the survey is delivered—not only because service quality changed. Interpret the percentage alongside its collection conditions.

Common distortions include:

Nonresponse: Customers who answer may differ from customers who ignore the survey.
Channel: Email, chat, phone, and other channels can attract different response patterns.
Timing: A survey sent immediately after an event may produce a different result from one sent later.
Case mix: A period with unusually difficult or unusually simple cases can shift the score.
Language: Survey language can affect comprehension and who chooses to respond.
Agent incentives: Pressure tied directly to scores can encourage behavior that improves the number without improving the experience.

Sampling and response bias deserve particular caution. The calculator describes the responses collected; it does not prove that the percentage represents every customer. Be careful with strong conclusions when the response count is small, the sample is uneven, or exclusions changed.

Review the percentage with the underlying counts. A change from 85% to 88% may have a different meaning depending on how many customers answered and how the ratings were distributed. Zendesk’s customer satisfaction guide and Medallia’s customer satisfaction overview provide additional supplied perspectives on interpreting the measure.

How should a support team act on CSAT?

Use CSAT as a learning signal, not as a simplistic verdict on an agent. The practical goal is to find repeatable causes of satisfaction or friction and improve the support system around them.

A useful review cycle is:

Check the score with response count and rating distribution.
Read available comments alongside the ratings.
Segment results by interaction type, channel, timing, and other documented conditions.
Identify workflow causes that the team can change.
Recheck the same declared measure after the change.

Protect agents from automatic punishment based on one rating or one percentage. Agent performance can be affected by case mix, customer expectations, language, channel, and processes outside the agent’s control. If the organization rewards only a higher CSAT number, agents may be pushed toward score protection instead of honest resolution.

Keep the threshold stable while learning from the results. If the team changes the question, scale, timing, or exclusions, label the change so old and new results are not presented as a seamless trend.

For adjacent customer feedback and review workflows, SellerTrove also covers Shopify product review apps and UGC tools. If survey feedback connects to public endorsements or reviews, consult the FTC endorsements and reviews guidance. To assemble the broader support stack, use Stack Builder.

CSAT Score Calculator: Measure a Support Moment, Not a Brand