CSAT

CSAT (Customer Satisfaction Score) is a metric that measures how satisfied a customer was with a specific interaction: a purchase, a support ticket, a delivery or the use of a product. It is collected with a simple question ("How satisfied are you with...?") and a short scale, usually from 1 to 5.

Unlike other indicators, CSAT is transactional and short term: it captures sentiment at a specific moment, right after the contact. Its formula is straightforward: you divide the number of positive responses (the two highest options on the scale) by the total number of responses and multiply by 100, which gives a value from 0 to 100.

As an experience metric, CSAT is part of the service and customer success dashboards consolidated in analytics platforms such as Metrix, where it is cross-referenced with ticket volume, resolution times and account data to understand not just the number but the reason behind it.

CSAT was born in customer service teams as a quick way to know whether an interaction went well or badly. Its value lies in its immediacy: you ask as soon as the contact ends, while the experience is still fresh, and that is why it is one of the most widely used indicators for evaluating support, after-sales service and key moments in the customer journey.

How it is measured and calculated

The CSAT survey uses a single question with a scale, almost always from 1 to 5 (where 1 is "very dissatisfied" and 5 is "very satisfied"). The calculation groups the responses and counts the two top categories as "satisfied" (4 and 5). The formula is:

CSAT = (satisfied responses / total responses) x 100

If 150 of 200 completed surveys were a 4 or a 5, the CSAT is 75%. It is an easy number to communicate across the whole organization, and that simplicity explains why it is so widely adopted.

Best practices for implementing it

• Ask at the right moment: right after closing a ticket or delivering an order, not weeks later.
• One clear question: CSAT loses strength when it is mixed into long questionnaires that lower the response rate.
• Segment by channel and reason: the same 80% can hide an excellent WhatsApp channel and a terrible phone line.
• Add an optional open field: the free-text comment explains what is behind the number and is where actionable improvements show up.
• Watch the trend, not the single data point: what matters is whether CSAT rises or falls over time, not an isolated value.

Why it matters for the business

A falling CSAT usually signals operational friction (delays, errors, lack of follow-up) before it turns into churn or complaints. In Argentine service and consumer companies, where word of mouth and reputation carry weight, monitoring CSAT by team lets you spot in time which process is breaking down. For example, a distributor that measures CSAT at the close of each delivery may discover that dissatisfaction is concentrated in one specific delivery zone and fix the route or the carrier, not the whole operation.

CSAT, NPS and CES: how they differ

CSAT is often confused with other experience metrics. Each one answers a different question, and it pays to use them together rather than as substitutes for one another.

CSAT is ideal for evaluating concrete moments, NPS for reading the underlying relationship and loyalty, and CES for detecting friction in specific processes. Many customer success teams combine all three to get a complete picture.

Common mistakes

The first is treating CSAT as absolute truth without looking at the response rate: if only 5% answer and they are the angriest customers or the biggest fans, the data is biased. The second is comparing your own CSAT with benchmarks from another industry without context, since the ranges vary a lot between sectors. The third is measuring without acting: CSAT only creates value if it triggers concrete improvement actions. Finally, putting it on a dashboard next to other operational KPIs keeps you from reading it in isolation and gives it the context it needs to be useful.