UR

Satisfaction Surveys (CSAT)

A practical measurement method for understanding satisfaction at key moments in the user journey.

How to use CSAT surveys to measure satisfaction at specific interactions, identify problem areas, and track change over time.

15 October 20224 min read

Quick take

If you want to measure how satisfied users are at a specific moment, use CSAT surveys.

What it is

CSAT (Customer Satisfaction) are a UX and product method used to measure how satisfied users are with a specific , , or overall experience.

They typically ask a simple question such as “How satisfied were you with this experience?” with a rating scale.

CSAT is usually triggered at key moments, such as after a purchase, support , or .

Unlike broader , CSAT is focused on immediate, contextual .

The goal is to quantify satisfaction and identify areas where the experience falls short.

CSAT is useful when you need a direct measure of how users feel immediately after a specific interaction.

When to use it

Use this method when you need to measure satisfaction at specific points in the .

It is most useful when:

You want to measure satisfaction after key interactions
You need quick feedback on a specific feature or flow
You are tracking performance over time
You want to identify problem areas in the experience
You are supporting service or product improvement

It is less useful when:

You need deep understanding of behaviour or motivation
Feedback is not tied to a clear interaction
Response rates are low or biased
CSAT is often used alongside NPS and qualitative research to provide both measurement and understanding.

Key takeaway

Use CSAT when you need a simple, repeatable way to measure how users feel about a specific moment in the experience.

How to run it

Set up properly.

Before you start, be clear on where the survey will be triggered, what it relates to, and what scale you will use.

Timing and are critical to getting meaningful .

Run the method.

CSAT should be simple and timely.

Ask a clear satisfaction question. Use a consistent rating scale, such as 1 to 5. Trigger the survey immediately after the . Optionally include a follow-up open question. Keep it quick and unobtrusive.

The easier it is to respond, the better the .

Capture and make sense of it.

The value comes from measuring satisfaction over time.

Look across to identify overall satisfaction scores, trends over time, differences across or , and patterns in negative feedback.

Use this to prioritise improvements.

What to look for

Focus on:

CSAT score
The overall satisfaction rating
Trends
Changes in satisfaction over time
Low scores
Areas where users are dissatisfied
Context
Where in the journey feedback is collected
Qualitative feedback
Comments explaining the score

Where it goes wrong

Most issues come from:

A score without has limited value.

poor timing of the survey
unclear or inconsistent scales
low response rates
ignoring qualitative feedback
focusing on scores without action

What you get from it

Done properly, this method gives you:

a clear measure of user satisfaction
visibility of problem areas
trends over time
evidence to guide improvements

Key takeaway

It helps you understand how users feel in the moment.

Get in touch

If this sounds like something you need, we can help you measure satisfaction properly and turn into real improvements.

No guesswork. No assumptions. Just clear you can act on.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is CSAT in UX?

CSAT is a method used to measure user satisfaction with a specific or experience.

When should you use CSAT surveys?

Use them after key such as purchases, support, or .

What is a good CSAT score?

It depends on the product, but higher scores indicate better satisfaction.

How is CSAT measured?

Typically through a rating scale, such as 1 to 5 or 1 to 10.

Does CSAT improve UX?

Yes. It helps identify dissatisfaction and track improvements over time.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20