CSAT

What is CSAT?

CSAT stands for Customer Satisfaction Score. It’s a metric that measures how happy customers are with a specific interaction, product, or service. Most teams use it for support: after every closed ticket, ask the customer how satisfied they were, then track the average over time.

The thing that makes CSAT useful is that it’s interaction-specific. NPS asks about the brand. CES asks about the effort involved. CSAT asks about this conversation. That makes it a sharp tool for improving the quality of individual support touchpoints.

How to calculate CSAT

The formula is simple:

CSAT (%) = (Number of satisfied responses / Total responses) × 100

“Satisfied” usually means a 4 or 5 on a 5-point scale (or the equivalent on whatever scale you use). Customers who answer 1, 2, or 3 don’t count as satisfied. Some teams include 3 as neutral and exclude it from the denominator, which can shift the score by 5 to 10 points either way. Whichever method you pick, stay consistent so your numbers are comparable over time.

Worked example: 100 customers respond to a survey. 78 give a 4 or 5. CSAT = 78%.

What’s a good CSAT score?

It depends on industry and channel, but rough benchmarks:

Anything below 70% generally signals a problem worth investigating. Anything above 90% sustained over months is exceptional.

Why CSAT matters for ecommerce support teams

CSAT is the most direct signal you have about the quality of individual support interactions. It doesn’t tell you everything — an agent can be friendly but slow, which shows up in FRT and AHT but might not tanked CSAT. But it’s the closest thing to a customer’s verdict on the experience.

For ecommerce teams specifically, CSAT correlates with repeat purchase behavior. Customers who rate interactions highly are significantly more likely to buy again. That makes support quality a commercial metric, not just an operational one.

CSAT vs NPS vs CES: when to use which

These three metrics measure different things. Using the right one depends on what question you’re actually trying to answer.

CSAT: How was this specific interaction? Best for evaluating support quality, ticket by ticket.

NPS: Would you recommend us? Best for measuring brand perception and long-term loyalty. Survey quarterly or after major milestones.

CES: How easy was it to get help? Best for identifying friction in your support process. High effort scores predict churn even when CSAT is decent.

Most mature support teams use all three, but on different cadences and for different purposes.

How to improve your CSAT score

Most CSAT improvement comes from a handful of factors:

• Send the survey at the right time. Immediately after ticket close, not 48 hours later. Response rates and quality of feedback both drop with delay.
• Keep it short. One question plus an optional comment field. Longer surveys get abandoned.
• Look at response rates, not just scores. A CSAT of 88% from 5% of customers is a different signal than 88% from 50%. Low response rates mean your data is skewed toward customers motivated to respond — usually the very happy and very unhappy.
• Segment by agent and ticket type. Aggregate CSAT hides variation. A team average of 80% might include one agent at 95% and another at 65%. Segment to find the real patterns.
• Read the comments. The numerical score tells you whether customers were satisfied. The comments tell you why. The qualitative data is where the improvement opportunities live.

For teams using AI, Neople customers typically see CSAT improve by 8–15 percentage points after deployment, primarily because the support team has more time for the harder, higher-stakes interactions that used to get rushed.