Customer satisfaction (CSAT)

A consulting platform analysed CSAT by customer company size. Enterprise customers had 79% CSAT; mid-market customers had 71% CSAT; small business customers had 68% CSAT. Investigation revealed that mid-market and small business customers were experiencing longer onboarding times and receiving less dedicated support. By implementing better self-service resources and improving onboarding for smaller customers, they closed the CSAT gap.

A SaaS company surveyed support CSAT after each support ticket resolution. Initial CSAT was 72%. They discovered that response time was the primary driver: tickets answered within 2 hours had 85% CSAT; tickets answered after 24 hours had 58% CSAT. They hired additional support staff to reduce response time, and CSAT improved to 81% within three months. Higher satisfaction also correlated with lower churn.

Measure CSAT regularly and consistently. Most organisations survey CSAT quarterly or biannually. Decide when to measure: after a support interaction? After a major product update? At contract renewal? The timing affects what CSAT actually measures and should align with your business objectives.

Act on CSAT feedback. If you survey but don't respond to the insights, customer satisfaction often declines further - customers feel heard but unheard. When you discover low satisfaction, investigate why. When you uncover common complaints, address them. When CSAT improves, communicate that improvement back to customers.

Segment your CSAT analysis. Don't just track overall CSAT; compare satisfaction by product tier, customer segment, tenure, and usage patterns. A new customer's satisfaction might be lower during onboarding but recover over time. Understanding these patterns helps you interpret the data and identify which groups need support.

CSAT, short for customer satisfaction, measures how happy a customer is with your product, your support, or one specific interaction. You ask a simple question, "How satisfied are you with [the thing]?", and they answer on a scale, usually 1-5 or 1-10. Aggregate the answers and you get a CSAT percentage. That's the whole mechanic. It's deliberately narrow: it tells you whether the last experience landed, not whether someone loves you enough to recommend you (that's NPS) or how easy you were to deal with (that's CES).

The useful thing about CSAT is that you can attach it to a moment. Product CSAT, support CSAT, feature CSAT, onboarding CSAT, they're all the same question pointed at different things. As a rough read, above 80% is strong, 60-80% has room to improve, and below 60% means something's genuinely wrong. Benchmarks shift by industry, though, so B2B support often scores lower than B2C simply because enterprise buyers expect more.

Why it matters

For a B2B growth team, CSAT is a leading indicator of churn and expansion. Happy customers renew, resist discounting, and buy more; unhappy ones quietly drift toward the exit. It's also diagnostic: if CSAT drops the week after a release, the release broke something. If it varies by segment, one segment is being underserved. That granularity is what makes it worth measuring rather than just guessing.

How to apply it

Measure at a moment that means something, and measure it the same way every time. The cleanest version is to trigger the survey right after the experience you care about, while it's fresh.

Say you're running support on Freshdesk. Fire a one-tap CSAT survey the moment a ticket is marked resolved, then slice the scores by agent, response time, and topic. That's where the real signal lives, you'll often find that tickets answered within two hours score 85% and ones that drag past a day score 58%, which points straight at staffing rather than agent quality.

Say you're an ecommerce brand on Gorgias. Tag every low-CSAT reply with its reason, returns, shipping, a buggy checkout, and you stop arguing about anecdotes and start fixing the one issue dragging the average down.

And say you want CSAT across the whole lifecycle, not just support. Use Customer.io to trigger a survey on a behavioural event, 30 days after onboarding, the day after a big feature ships, a week before renewal, so the timing is consistent and the scores are comparable over time.

Whatever tool you pick, the rule is the same: act on the feedback. Surveying customers and then ignoring what they tell you makes satisfaction worse, not better, because now they feel heard and dismissed. Investigate the low scores, fix the common complaints, and close the loop by telling people what changed.

For B2B growth teams, CSAT is a leading indicator of churn and expansion opportunities. Customers with high CSAT scores are less likely to cancel, more likely to renew, and more likely to buy add-on features or upsell offerings. Conversely, customers with low CSAT are at risk of churning, whether to competitors or simply by discontinuing use.

CSAT also reveals specific problems. If CSAT drops after a product update, the update may have introduced a bug or created usability issues. If CSAT varies by customer segment, one segment may be underserved. This granular insight helps you prioritise improvements.

From a sales perspective, high CSAT directly enables growth. Satisfied customers are more likely to renew, less likely to need heavy discounting at renewal, and more willing to expand relationships. If your goal is to grow revenue from existing customers, improving CSAT is often more efficient than acquiring net new customers.

An enterprise software company released a new reporting feature and surveyed CSAT with that feature specifically. CSAT was 64%, significantly lower than their 82% product CSAT overall. They collected open feedback and discovered the feature was missing an export-to-spreadsheet capability that customers expected. They added it, resurveyed, and CSAT on that feature improved to 78% within a quarter.