What is CSAT?
CSAT, or Customer Satisfaction Score, measures how happy a customer is with a specific support interaction, transaction, or experience.

Key takeaways
- CSAT measures satisfaction with a specific support interaction, not overall loyalty.
- The trend is more useful than one isolated score.
- Segment CSAT by topic, channel, team, and automation status to find what to fix.
Quick answer
CSAT, or Customer Satisfaction Score, measures how satisfied a customer is with a specific interaction. Support teams usually collect it after a ticket is resolved with a short rating survey.
How CSAT works
- Send a short survey after resolution.
- Collect ratings such as satisfied or not satisfied, or a 1-5 score.
- Count satisfied responses against total responses.
- Track patterns by team, channel, topic, and customer segment.
How to interpret CSAT
CSAT is a signal, not a verdict. A low score can mean the agent was unclear, the policy disappointed the customer, the product caused pain, or the resolution took too long. Read the comment and the ticket before assuming the cause.
How to improve CSAT
- Respond faster to urgent and emotional tickets.
- Use knowledge base links so answers feel grounded and complete.
- Escalate exceptions instead of forcing a policy answer.
- Review low-CSAT tickets in batches to find recurring root causes.
- Turn confusing product moments into better onboarding and help content.
CSAT is a conversation review system
A CSAT score is useful because it points the team back to specific support interactions. It is less useful when treated as a leaderboard without context.
One low rating may reflect a bad answer, a slow reply, a disappointing policy, or a product problem support could not fix. The score tells you where to look, not what the root cause is.
For AI-assisted support, CSAT should be segmented by automation type. Compare fully human replies, AI-drafted replies, and auto-resolved tickets so the team can see where automation helps and where it creates risk.
How to review CSAT without overreacting
- Read the ticket before assigning blame to the agent or the automation.
- Group low scores by topic to find repeated product or policy issues.
- Watch trends over time instead of reacting to one week of noisy data.
- Compare CSAT with reopen rate and SLA breaches.
- Use customer comments as source material for better help center articles and draft guidance.
Frequently asked questions
Try Protodesk free for 7 days
Connect your first inbox, invite your team, and see AI triage, sidekick drafts, and auto-resolve with 300 trial credits. No credit card required.




