What is CSAT?

CSAT is widely used in customer-facing software support. The concept is simple; the calculation details are not universal. Always check how your helpdesk vendor or survey tool defines a “positive” response.

Support-specific scope

In SaaS support, CSAT usually follows a ticket, chat, or email resolution. It answers “how satisfied were you with this help?” It does not directly answer “do you love the product?” or “will you renew?”

Common formula

A frequent approach is to take the percentage of positive responses on a rating scale. For a 1–5 scale where 4 and 5 count as positive:

CSAT (%) = (number of positive responses ÷ number of responses) × 100

Some teams use a 1–3 scale, a binary thumbs-up/down, or a different positive threshold. Those are product-specific conventions, not a single industry law.

Realistic software support example

A customer reports that SSO login fails for one identity provider. You confirm impact, gather tenant details, find a known configuration miss, and walk them through a fix. The ticket is resolved the same day. The survey asks “How satisfied were you with the support you received?” They select 5. That CSAT reflects the interaction. Separately, their admin may still dislike the product’s SSO setup UX—an issue better tracked by product feedback, not ticket CSAT alone.

Practical application

• Know when the survey fires (on resolve, on first reply, after N hours).
• Read comments, not only the score.
• Compare CSAT with response and resolution timing before changing process.
• Learn the wider metric set in customer-support metrics explained.
• Practise the skill on the Support Metrics that Matter roadmap item.