CSAT (Customer Satisfaction)

CSAT is the metric customer support orgs use to measure how satisfied customers are with a specific interaction. The standard implementation sends a one-question survey after the ticket closes: "How would you rate your experience?" on a 1-to-5 scale, or sometimes a simple thumbs up or thumbs down. The percentage of positive responses (4-star and 5-star, or thumbs up) becomes the CSAT score. Healthy SaaS support runs CSAT above 90%, with best-in-class orgs sustaining 94% or higher. Below 85% indicates structural problems with response time, resolution quality, or agent training that the support leader needs to address. The metric is simple by design because it has to work across millions of customers without complex onboarding.

CSAT is a lagging indicator, which is both its strength and its weakness. The score tells you what already happened, which is useful for trend analysis and team performance review but useless for catching a quality problem in real time. By the time CSAT drops three percentage points, the bad interactions have already shipped. This is why funded support orgs pair CSAT with leading indicators like first response time, resolution time, and reopen rate, which catch quality problems before they show up in customer scores. CSAT also suffers from response bias. Customers with strong opinions, positive or negative, are more likely to respond than the median customer, which can skew the score in either direction.

CSAT interacts with AI deflection in a specific way. Teams that deploy AI well see CSAT hold steady or improve because customers get faster answers and the human team has more time for the cases that need them. Teams that deploy AI badly see CSAT drop fast because frustrated customers get routed in circles or receive wrong answers from ungrounded bots. The AI Support Department standard architecture ships with CSAT monitoring and routes any ticket scoring below 4 stars to a human review queue automatically, with the agent's decision audited and the RAG index updated when patterns emerge. The right deployment lifts CSAT alongside cutting cost per ticket. The wrong deployment trades CSAT for cost savings, which leadership eventually pays back through churn.