Premium launches are $39 $19 right now · no code needed

Logo Launch IT (Fast)
GLOSSARY

Customer satisfaction score

Customer satisfaction score is a metric used to gauge how happy customers are with your product or service. It helps you understand if your customers are satisfied with their experience.


What is Customer Satisfaction Score?

Customer satisfaction score, almost always shortened to CSAT, is the metric behind those tiny surveys that ask "How satisfied were you with X?" on a scale, usually 1 to 5. Customers answer in two seconds, and you convert the answers into a percentage that tracks how happy people are with a specific interaction: a support ticket, an onboarding flow, a purchase, or the product as a whole.

What makes CSAT useful is its precision of moment. Unlike broad loyalty measures, CSAT is usually attached to one touchpoint right after it happens. Ask after a support conversation and you are measuring support. Ask after delivery and you are measuring fulfillment. That specificity is why teams run several small CSAT surveys at different points rather than one big annual survey nobody answers.

Day to day, CSAT shows up as an emoji row at the bottom of a help-desk email, a one-question popup after checkout, or a thumbs-up prompt after onboarding. Low-friction collection is the whole game: response rates collapse the moment a survey takes more than a few seconds.

How to calculate customer satisfaction score

The standard formula is: CSAT = (number of satisfied responses / total responses) x 100, where "satisfied" means the top two ratings on a 5-point scale (the 4s and 5s).

Worked example: say your startup sends a one-question survey after every resolved support ticket. In March you get 250 responses: 60 people rate you 5, 150 rate you 4, 25 rate you 3, 10 rate you 2, and 5 rate you 1. Satisfied responses are 60 + 150 = 210. CSAT = (210 / 250) x 100 = 84%. Note that the 3s count against you: neutral is not satisfied in this formula, which keeps the metric honest.

Why customer satisfaction score matters for startups

For a tiny team, CSAT is an early-warning system that costs almost nothing to run. Revenue and churn rate are lagging indicators: by the time they move, the damage is months old. CSAT moves within days of something breaking, like a rough release or a slow support week. The decision it changes is triage: a falling CSAT on onboarding surveys tells a two-person team to pause feature work and fix the first-run experience now, before the churn shows up in the accounting.

It also makes support quality visible. Without a score, support is judged by anecdote; with one, you can see whether this month's process change actually helped.

Customer satisfaction score in practice

Imagine you run a three-person meal-planning app. You add a one-tap CSAT prompt after onboarding and after each support reply. Onboarding CSAT comes back at 68 percent while support sits at 90 percent, which surprises you: you assumed support was the weak point. Reading the comments attached to low scores, you find users are confused by the grocery-list step. You redesign that single screen, and onboarding CSAT climbs to 82 percent over six weeks, followed a month later by better trial conversion.

Benchmarks and rules of thumb

Ranges vary by industry and by which touchpoint you measure, but many software teams treat CSAT in the mid 70s to mid 80s as healthy, with support-ticket CSAT often running higher (upper 80s to low 90s) because it is measured right after a human helped someone. Trends matter more than absolutes: a stable 78 percent is less alarming than a slide from 90 to 82 percent over two months. Also watch response rate; if only 5 percent of customers answer, the score mostly reflects your angriest and happiest users.

Common mistakes

  • Counting neutral 3s as satisfied. That inflates the score and hides problems. Stick to top-two-box scoring.
  • Measuring everything with one survey. A single generic "are you satisfied?" blends onboarding, product, and support into an unactionable mush. Attach surveys to specific moments.
  • Ignoring the comment box. The number tells you something changed; the comments tell you what. Always allow an optional free-text field.
  • Surveying too often. Prompting after every session burns goodwill and tanks response rates. Cap how often any one user is asked.

Related concepts

CSAT works best as one input in a broader customer feedback loop, alongside interviews and usage data. Rising satisfaction usually shows up later as stronger customer retention, and teams that act on the scores systematically are practicing the core of customer success.

See Customer satisfaction score in practice

Hundreds of startups launch on LaunchIt and put concepts like this to work. Browse them, or launch your own.

Share this term

Browse All Terms