Three complementary satisfaction metrics, each capturing a different dimension of how users feel. Behaviour shows what users do; these catch what behaviour hides — the frustration behind a completed task.
▸ Try the interactive toolNPS, CSAT, and CES are three complementary metrics for measuring customer satisfaction, each capturing a different dimension of the experience. Behavioural data shows what users do; these satisfaction metrics catch what behaviour hides — a user can complete onboarding (good behaviour) while finding it a frustrating slog (bad experience). Used together, they give a complete picture no single metric provides.
NPS (Net Promoter Score) asks how likely you are to recommend the product (0–10, promoters minus detractors) — a broad loyalty signal, good for tracking overall sentiment, but lagging and unable on its own to tell you what to fix. CSAT asks how satisfied you were with a specific thing (1–5) — fired right after an interaction like onboarding or support. CES asks how much effort a task took — capturing friction specifically. The crucial discipline shared by all three: a score alone is nearly useless, so always pair it with an open-text follow-up ('why that score?') that tells you what to actually do.
A satisfaction score alone tells you little — always pair it with an open-text follow-up ('why that score?'). The number tracks sentiment; the text tells you what to fix. Behaviour shows what users do; these catch how they feel.
Behavioural metrics can show a task completed while missing that it was a miserable experience — satisfaction metrics fill that gap, but only if paired with the 'why' that makes a score actionable.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Behaviour hides feeling | A completed task can still be a frustrating one. | Satisfaction metrics catch the feeling behaviour misses. |
| A score with no 'why' | A bare NPS number tells you sentiment, not what to fix. | An open-text follow-up turns a score into an action. |
| Wrong metric for the question | Using NPS to gauge a specific flow's friction. | Each metric suits a different dimension — match them. |
| One metric for everything | Relying on a single number for a complex picture. | The three together give a complete satisfaction picture. |
Each measures a different dimension of satisfaction — and each is far more useful paired with an open-text 'why?' than reported as a bare number.
| Metric | Question asked | Best for | Key limitation |
|---|---|---|---|
| NPS (Net Promoter Score) | How likely are you to recommend us? (0–10) | Broad loyalty / overall sentiment, benchmarking | Lagging and slow; a score alone doesn't say what to fix |
| CSAT (Customer Satisfaction) | How satisfied were you with [this specific thing]? (1–5) | A specific interaction — onboarding, a support contact | Captures the moment, not overall relationship |
| CES (Customer Effort Score) | How easy was it to [do this]? (effort scale) | Friction in a specific task or flow | Narrow — measures ease, not delight or loyalty |
A team had rich behavioural data showing users completing onboarding — by the numbers, a success. But they had no systematic measure of how users felt about it. The behavioural data showed the completion and entirely missed that, for many, it was a frustrating slog they barely pushed through.
Adding satisfaction metrics caught what behaviour hid. A CSAT survey fired right after onboarding ('how satisfied were you?') with an open-text 'why?' revealed the frustration; CES would have flagged the effort specifically; NPS tracked whether overall loyalty was suffering. Crucially, the open-text follow-ups — not the scores alone — told them what to fix. The numbers showed there was a problem; the text showed what it was.
The deliverable is the right metric for each question — NPS for loyalty, CSAT for an interaction, CES for friction — each paired with an open-text 'why?'.
| Use… | When you want to know… |
|---|---|
| NPS | Overall loyalty / sentiment over time |
| CSAT | Satisfaction with a specific interaction |
| CES | How much effort a task required |
| + open text | — always, to learn what to fix |
Satisfaction metrics exist to catch what behaviour hides — the frustration behind a completed task, the effort behind a success. The three are complementary, each measuring a different dimension, and none is complete without the 'why' that makes it actionable.
The shared discipline matters more than the differences between the three: a score on its own is nearly useless. NPS tells you loyalty is slipping but not why; CSAT tells you an interaction disappointed but not what about it; CES flags friction but not its source. The open-text follow-up — 'why that score?' — is what converts each from a sentiment thermometer into a source of actionable insight, because it captures the reason behind the number. This is also why satisfaction metrics complement rather than replace behavioural analytics: behaviour answers 'what happened' with precision and is silent on feeling; satisfaction metrics answer 'how do they feel' and, with the open text, 'why' — and a complete picture of product health needs both.
A number alone doesn't say what to fix. Always pair it with open-text 'why?'.
NPS, CSAT, and CES measure different things. Match the metric to the question.
A completed task can hide frustration. Add satisfaction metrics.
Optimising the number without acting on the 'why' is theatre. Act on the text.
These metrics are inputs to a systematic VoC program (Tool 25).
Satisfaction (how they feel) pairs with engagement/funnels (what they do).
NPS/CSAT map to HEART's Happiness dimension (Tool 06).
CSAT after onboarding reveals the frustration behind completion (Tool 13).
You want to know three things: is overall loyalty trending up? was the new support flow satisfying? how hard is it to set up an account? Match NPS, CSAT, and CES to each.
Then add the one element each needs to be actionable — and say why the score alone wouldn't be enough.
If you reached for an open-text 'why?' alongside each score, you've grasped the discipline that makes satisfaction metrics useful: the number flags the problem, the text reveals the fix.