Skip to content
Menu

CSAT (Customer Satisfaction Score)

The share of post-ticket survey responses that rate the support experience positively. It measures how clients felt about individual interactions with the service desk.

  • Filed under Service desk.
  • Also called Customer satisfaction, Client satisfaction, CSAT score.
On This Page
  1. What CSAT Measures at an MSP
  2. Getting a Number You Can Trust
  3. Using the Negative Responses
  4. Where CSAT Misleads
  5. Common Questions

What CSAT Measures at an MSP

CSAT is a ticket-level signal. When a ticket closes, your PSA sends the end user a short survey, usually one click from a good, neutral or bad rating, with an optional comment. CSAT is the share of responses that are positive. It tells you whether a technician handled a particular issue well, which makes it useful for coaching and for spotting a bad week before a client raises it. For current targets, see the Client Satisfaction KPI.

It does not measure the relationship. The person rating a password reset is rarely the person who signs your renewal. That is what NPS is for, asked of the decision maker.

Getting a Number You Can Trust

  • Track the response rate beside the score. If only the happiest and angriest users reply, the score describes them, not the client.
  • Survey every closed ticket, not a chosen sample. Letting technicians decide which tickets get surveyed skews the result.
  • Keep it to one question and one click. Every extra field cuts responses.
  • Report by client and by technician as well as overall, so one noisy account does not hide a problem elsewhere.

Most PSA platforms can send the survey automatically on ticket close. If you are choosing tools, the PSA entry covers where that fits.

Decide in advance what counts as positive. On a three-point scale that is usually only the top rating; on a five-point scale, the top two. Changing the definition later breaks the trend, so write it down with the report and keep it the same when you change survey tools or PSA platforms.

Using the Negative Responses

The score is less valuable than the comments behind the bad ratings. Read every one. Most fall into a few patterns, and each points somewhere different.

Complaint patternWhere to look
Took too longFirst response time and queue staffing
Had to explain it twiceHandoffs, notes and first contact resolution
Fixed, then broke againReopen rate and root cause
Tech was rude or unclearCoaching for that technician

Close the loop: a service lead calls the user back on every negative rating. That call often recovers the relationship, and clients notice when a bad rating gets a human response. Pair CSAT with first contact resolution and time to resolution, since those usually explain a falling score.

Where CSAT Misleads

A high CSAT can sit beside a client that is about to leave. Users may like your technicians while the owner thinks IT costs too much or that you never bring ideas. Watch CSAT for service quality, and use a regular QBR with the decision maker to hear the rest.

Common Questions

Should technicians see their own CSAT?

Yes, with the comments. It works best as a coaching tool reviewed together, not as a leaderboard or a factor in pay on its own.

What should a CSAT survey ask?

One question about how satisfied the user was with how the ticket was handled, with a small rating scale and an optional comment box.

Should I survey automated or alert tickets?

No. Survey only tickets a person raised and a person worked. Alert tickets with no user contact dilute the score.

Welcome Back

Sign in to your MSP Outpost account.