CSAT

5 min read

Also known as: Customer Satisfaction Score, Satisfaction Rating, Post-Interaction Survey Score

CSAT is a post-interaction score measuring how satisfied a customer felt about a specific support touchpoint, ticket, or transaction.

Definition

CSAT (Customer Satisfaction Score) is a survey-based metric that captures how a customer felt immediately after a defined interaction — a resolved ticket, a chat session, an onboarding call, or a delivery. Customers rate their experience on a short scale (typically 1-5 or 'satisfied/dissatisfied'), and the score is calculated as the percentage of positive responses out of total responses.

Support teams trigger CSAT surveys automatically the moment a ticket closes, then route the results back into the CRM record so agents, managers, and account owners see satisfaction trends by customer, agent, channel, and issue type. Low scores typically open a follow-up workflow — a callback, a manager escalation, or a save play — while high scores feed coaching and recognition.

CSAT is interaction-specific, which separates it from NPS (relationship loyalty) and CES (effort on a single task). You can run all three in parallel; CSAT is the one that tells you whether the last thing you did for a customer landed.

Why It Matters

CSAT is the fastest feedback loop your support org has. A drop on a specific agent, queue, or product area surfaces within hours rather than waiting for a quarterly review, which means you can retrain, reassign, or fix a broken article before churn signals appear. Tying CSAT to account records also gives CS and sales a real reason to step in on at-risk renewals.

Teams that ignore CSAT usually discover satisfaction problems through cancellations or public reviews — both of which are too late and too expensive to reverse. Without a structured score, managers rely on gut feel, agent self-reporting, or the loudest escalations, which skews coaching toward whoever complains most and lets quiet dissatisfaction compound into churn.

Examples in Practice

A 40-person SaaS support team sends a two-question CSAT survey after every ticket closes. Scores below 3 automatically reopen the ticket, alert the team lead, and pause any auto-close timers — giving the agent a chance to recover the relationship before the customer files a complaint or downgrades.

An ecommerce brand attaches CSAT to delivery and returns interactions, not just support chats. When CSAT on returns drops two weeks in a row, the ops team traces it to a slow refund processor and renegotiates the SLA, lifting scores back above 90% within the next billing cycle.

A B2B services agency uses CSAT after every client deliverable review. Scores roll up to the account owner's dashboard so renewal conversations start with hard data — 'your team has averaged 4.7 across 22 deliverables this quarter' — instead of subjective check-ins.

Frequently Asked Questions

What is CSAT and why does it matter?

CSAT is the percentage of customers who rate a specific interaction positively, usually on a 1-5 or satisfied/dissatisfied scale. It matters because it's the closest thing support has to real-time quality feedback — you learn within hours whether your team, process, or product is meeting expectations on a per-ticket basis, which lets you intervene before dissatisfaction turns into churn.

How is CSAT different from NPS?

CSAT measures satisfaction with a single interaction, while NPS (Net Promoter Score) measures overall loyalty to the brand on a 0-10 scale. CSAT answers 'did we handle this ticket well?' and NPS answers 'would you recommend us?'. CSAT is tactical and high-frequency; NPS is strategic and surveyed quarterly or after major milestones. Most mature support orgs run both.

When should I use CSAT?

Use CSAT immediately after any defined customer interaction — ticket resolution, chat close, onboarding session, delivery, returns, or training. The survey has to fire while the experience is fresh, ideally within minutes of the event. Avoid using CSAT to measure broad relationship health; that's what NPS or account health scores are designed for.

What metrics measure CSAT performance?

The CSAT score itself is the primary metric, calculated as (positive responses / total responses) × 100. Supporting metrics include survey response rate, CSAT by agent, by channel, by issue category, and the recovery rate on low-CSAT tickets. Many teams also track time-to-CSAT (how quickly the survey fires) and the correlation between CSAT and retention.

What's the typical benchmark for CSAT?

Industry-wide, 80-85% is considered healthy across B2B SaaS and services, with top-quartile teams sitting at 90%+. Ecommerce and consumer support typically benchmark slightly lower because of higher volume and emotional purchases. The number that matters more than the benchmark is your own trend line — a 2-point drop month-over-month is a problem regardless of where you started.

What tools handle CSAT?

CSAT lives inside ticketing and CRM platforms that fire surveys automatically on ticket close and route results back to the customer record. Standalone survey tools work but create data silos. The better setup is a CRM or helpdesk that ties each score to the agent, ticket, and account so managers can coach and CS can intervene without exporting spreadsheets.

How do I implement CSAT for a small team?

Start with a one-question survey ('How would you rate this interaction?' with a 1-5 scale) that fires automatically when a ticket closes. Add a free-text follow-up for any score below 4. Review results weekly in a 15-minute team huddle. Don't overengineer the program — response rate matters more than survey length, and short surveys consistently outperform long ones.

What's the biggest mistake teams make with CSAT?

Treating CSAT as an agent scorecard instead of a coaching signal. When agents know their bonus depends on the number, they start gaming surveys — closing tickets prematurely, asking customers for high ratings, or avoiding hard cases. Use CSAT to find patterns and improve process, and pair it with QA scoring so individual agents are evaluated on the full picture.

How often should CSAT surveys fire?

Every closed interaction is the standard, but cap repeat surveys to one per customer per 48-72 hours so heavy users don't get survey fatigue. If a customer opens five tickets in a day, you want one CSAT, not five. Most modern ticketing systems handle this throttling automatically once the rule is configured.

Can CSAT predict churn?

Yes, but only when combined with other signals. A single low CSAT rarely predicts churn on its own — repeat low scores, declining trend lines, or low CSAT on accounts with low product usage are the real warning signs. Feeding CSAT into an account health score alongside usage, billing, and engagement data gives you a much more reliable churn prediction than CSAT in isolation.

The AMW Suite