What is CSAT (Customer Satisfaction Score)?

CSAT (Customer Satisfaction Score) is a metric that measures how satisfied a user was with a specific interaction or product experience. It is collected by asking a single rating question immediately after the interaction in question, typically on a 1-5 or 1-10 scale.

Unlike Net Promoter Score, which measures overall loyalty, CSAT measures satisfaction at a specific, bounded moment. That specificity is both its strength and its constraint: CSAT is precise about individual touchpoints but does not capture the broader relationship between a user and the product.

How CSAT is calculated

CSAT is expressed as a percentage of respondents who gave a positive rating. The threshold for 'positive' varies by scale used:

• On a 1-5 scale: scores of 4 and 5 are counted as satisfied.

• On a 1-10 scale: scores of 7 and above (or 8 and above, depending on convention) are counted as satisfied.

Formula: CSAT = (Number of satisfied responses / Total responses) x 100.

A CSAT of 75% means that 75% of respondents gave a positive rating for the interaction. SaaS benchmarks vary by product type and interaction, but scores above 80% are generally considered healthy for customer-facing interactions.

When to use CSAT vs. NPS

The choice between CSAT and NPS depends on the question being asked.

• Use CSAT when you want to measure satisfaction with a specific, recent interaction: a support ticket resolution, the completion of an onboarding step, the first use of a new feature, or a billing interaction.

• Use NPS when you want to measure overall loyalty and long-term sentiment, typically at set intervals (quarterly, or triggered by lifecycle milestones).

In practice, both are often inputs to the same system. CSAT scores on individual interactions feed into a broader customer health score model alongside NPS, product engagement data, and commercial signals.

Collecting CSAT in-app

CSAT collected via email after the fact produces delayed, often unrepresentative responses. Collecting CSAT via an in-app survey immediately after the interaction produces higher response rates and more accurate data because users are still in context.

Effective CSAT in-app collection requires precise trigger timing: the question should appear immediately after the interaction completes, not on the next login or after an arbitrary time delay. Jimo's Surveys feature allows CSAT prompts to be triggered on specific product events, ensuring the question appears at the right moment without manual scheduling.

Acting on CSAT data

A low CSAT score for a specific interaction identifies a friction point. Common next steps:

• Review the interaction flow for clarity and complexity. A CSAT drop after a new feature launch often signals that the feature needs better contextual guidance.

• Segment CSAT responses by user segment to identify whether the dissatisfaction is concentrated in a specific role or cohort, or whether it is universal.

• Pair low CSAT with open-text follow-up questions to capture specific reasons, not just the numerical signal.