Skip to main content
Back to KPI Library
Customer Support

What is Customer Satisfaction Score?

Share of customers satisfied with an interaction or product.

How to calculate it

Calculate Customer Satisfaction Score as: (Satisfied responses / Total responses) × 100. Pull the inputs from your connected data and track the trend over time in your dashboard.

Examples

Example 1

420 of 500 survey responses are positive -> 84% CSAT.

Example 2

After a support interaction, 440 of 500 respondents rate it positively -> 88% CSAT, above the healthy threshold and trending up month over month.

Why it matters

Customer satisfaction score (CSAT) is the share of customers satisfied with an interaction or product and is a direct read on service and experience quality. It is fast to collect and easy to act on at the team or agent level. Survey timing and selection bias can skew it, so response rates and context should be considered alongside the score.

Benchmark context

75-85%+ is generally considered good; benchmark against your own trend and against the specific touchpoint being measured.

Common pitfalls

Survey timing and selection bias.

The complete guide

Understanding Customer Satisfaction Score

Customer satisfaction score (CSAT) is the share of customers satisfied with an interaction or product and is a direct read on service and experience quality. It is fast to collect and easy to act on at the team or agent level. Survey timing and selection bias can skew it, so response rates and context should be considered alongside the score. For context, 75-85%+ is generally considered good; benchmark against your own trend and against the specific touchpoint being measured. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Customer Satisfaction Score alongside NPS, CES and First Contact Resolution; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.

Make sure the numerator and denominator cover compatible populations and periods, and avoid dividing by a partial or unusually small base. Document business-hours rules, bot interactions, reopened tickets, pending time and the event that marks a case as resolved. Split the measure by channel, priority, issue type, customer tier and business-hours policy so that ticket mix does not create a misleading average. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.

Improve the measure by diagnosing demand and flow: remove repeat contact causes, strengthen knowledge content, route accurately, balance staffing to arrival patterns and coach from quality reviews. Common pitfalls: survey timing and selection bias. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.

Sources and further reading

  1. Customer satisfaction metrics

    Qualtrics Accessed

  2. ITSM metrics: what to measure and why it matters

    Zendesk Accessed

Related KPI guides

Turn KPI definitions into governed dashboards

Metricwise helps teams define metrics once, reuse them across dashboards, and ask trusted business questions in plain English.

Get Started