Skip to content

Guide

DSAT Meaning in Customer Service, Call Centers and BPOs

DSAT meaning in customer service: the dissatisfaction score formula with a worked example, what counts as negative, and why DSAT is not the inverse of CSAT.

· Updated · 11 min read

Reviewed by Dominik Blattner, founder of Kaizo

Part of: IQS Meaning: Internal Quality Score in Customer Service

DSAT (Dissatisfaction Score) is the customer service metric that shows the percentage of survey responses rating an interaction negatively. The formula is DSAT = (dissatisfied responses / total responses) x 100. The DSAT meaning is the same in call centers and BPOs, but there it is often a managed target in its own right, not just the flip side of CSAT.

In short

  • DSAT is calculated from the same post-interaction survey as CSAT, and lower is better.
  • Your scale and threshold decide what counts as dissatisfied, so write the threshold down.
  • DSAT and CSAT don’t add up to 100%, because of neutral responses.
  • A healthy CSAT average can hide a concentrated group of unhappy customers.
  • DSAT says a customer was unhappy. The conversation says why.

How do you calculate DSAT?

To calculate DSAT, count the survey responses that fall in your dissatisfied range, divide by the total number of responses you received, and multiply by 100. If 18 of 150 responses are dissatisfied, your DSAT is 12%. The denominator is responses received, not surveys sent, and a lower DSAT is better.

DSAT is a survey-based metric, calculated from the same post-interaction survey that produces your CSAT score. After a ticket, chat or call closes, the customer is asked to rate the experience, and the dissatisfied share of those ratings is your DSAT.

Note the denominator: it is total responses, not total surveys sent. Customers who never answered are not counted as dissatisfied, and they are not counted as satisfied either. They are simply not in the calculation at all, which is a limitation worth remembering when you read the number.

ElementDetail
FormulaDSAT = (dissatisfied responses / total responses) x 100
Dissatisfied responsesRatings in the negative range, for example 1 and 2 on a 1 to 5 scale
DenominatorTotal responses received, not total surveys sent
ScaleUsually 1 to 5, sometimes 1 to 3, or a simple thumbs up and thumbs down
Worked example18 dissatisfied out of 150 responses = 12% DSAT
TimingCollected immediately after the interaction closes
DirectionLower is better, unlike CSAT where higher is better

What counts as a dissatisfied response?

A dissatisfied response is any rating that falls below the threshold you set. There is no universal threshold. On a 1 to 5 scale, most teams count 1 and 2 as dissatisfied and 3 as neutral. Which ratings you count is a business decision, not a mathematical one, and that single choice changes your number more than anything else.

On a 1 to 5 scale

The common convention is to count 1 and 2 as dissatisfied, 3 as neutral, and 4 and 5 as satisfied. This mirrors the standard CSAT convention of counting only the top two ratings as positive. Some teams count 3 as dissatisfied too, on the argument that a neutral rating after a support interaction is not a good outcome. That single decision can roughly double the reported DSAT on the same survey data.

On a 1 to 3 scale

A three-point scale, often labeled good, neutral and bad, leaves less room for interpretation. The bottom rating is dissatisfied. But it also compresses the signal: a customer who was mildly annoyed and a customer who was furious land in the same bucket, so the score tells you less about severity.

On a thumbs up and down survey

A binary survey removes the threshold question entirely, because there is no neutral option. DSAT becomes simply the share of thumbs down. The tradeoff is that you lose the ability to see the middle of your distribution shifting before it turns negative.

Why the threshold has to be written down

Because the threshold is a choice, a DSAT number is only comparable to another DSAT number when both were calculated the same way. If you benchmark against an external figure without knowing which ratings that team counted as dissatisfied, you are comparing two different metrics that share a name. Document your threshold, keep it stable, and treat your own trend over time as the real signal.

Is DSAT the opposite of CSAT?

No. DSAT is not simply the inverse of CSAT. If CSAT is 80%, DSAT is almost never 20%. Neutral ratings count in the denominator of both metrics but in the numerator of neither, so the two figures leave a gap. And both are calculated only on the customers who answered the survey, not on everyone you served.

Neutral responses sit in between

On a five-point scale, a rating of 3 is usually counted as neither satisfied nor dissatisfied. Those responses are in the denominator of both calculations but the numerator of neither. So CSAT plus DSAT will typically fall short of 100%, and the gap is your neutral population. That gap is informative on its own: a large neutral block means a lot of customers came away feeling nothing much, which is a different problem from a small block of angry ones.

Non-responses sit outside both

Response rates on post-interaction surveys are typically low, and the customers who answer are not a random sample. People with a strong reaction in either direction are more likely to reply than people who were mildly inconvenienced. That means both CSAT and DSAT are computed on a self-selected slice of your customers, and the dissatisfaction that never gets a survey response is invisible in both numbers.

The practical consequence: read DSAT as the share of respondents who told you they were unhappy, not as the share of customers who were unhappy. Those are different populations. The full breakdown of how the two metrics diverge on the same data is in CSAT vs DSAT.

What does a DSAT trend tell you that CSAT hides?

A DSAT trend shows whether the group of genuinely unhappy customers is growing, even when the CSAT average looks flat. CSAT is an average, and averages absorb small groups. A team can hold a steady CSAT for two quarters while its share of 1 and 2 ratings quietly doubles, because movement between 3s, 4s and 5s offsets it.

The reason to watch DSAT separately is that dissatisfied customers behave differently from merely unsatisfied ones. They escalate, they churn, they write reviews, and they generate repeat contacts. The cost of a support operation is concentrated in that tail, so the tail deserves its own metric. Seeing which conversations sit in that tail, and what they have in common, is what customer support insights are for.

Read DSAT as a distribution, not a single number

The most useful view is not this month’s DSAT percentage but where the dissatisfied responses cluster: by queue, by channel, by issue type, by time of day, by tenure of the agent handling it. Dissatisfaction is rarely spread evenly. When you segment it, a flat-looking 9% often turns out to be 4% almost everywhere and 30% in one workflow that nobody has looked at.

Pair it with the metrics that explain it

DSAT tends to move with the operational metrics around it. A rise often traces back to first response time, first contact resolution, or the number of transfers before a resolution. Reading DSAT alongside those, rather than alone, is what turns it from a scoreboard into a diagnosis. The wider set of metrics that belong on the same dashboard is covered in our guide to customer service metrics and KPIs.

DSAT meaning in call centers and BPOs

In a call center or BPO, DSAT is usually a managed target with a threshold, an owner and a review cadence, not a diagnostic you check when something feels wrong. Outsourced quality is contractual, so a service level agreement often sets a maximum tolerable dissatisfaction rate alongside a minimum satisfaction score, and each dissatisfied response gets reviewed.

DSAT appears far more often in contact center and BPO vocabulary than in general CX writing, and that is the structural reason. The client cares about the floor of the experience as much as the average, so the floor gets its own number in the contract. The wider list of contract metrics is in our guide to KPIs in BPO.

That framing changes how the metric is used. In-house CX teams often treat DSAT as a diagnostic. Contact centers treat each dissatisfied response as something to review individually, categorize, and either accept as outside the team’s control or route into coaching.

It also explains the vocabulary you will encounter around it: DSAT tickets, DSAT reviews, DSAT drivers, DSAT recovery. These all describe the same underlying workflow of taking the negative responses seriously one at a time rather than watching a percentage move.

That review-and-coach loop is where the workload sits in a BPO, and it is the part that automated scoring against each client’s own criteria takes off the team’s plate. In Kaizo, scorecards can be scoped per client, which is how BPOs run one per account and keep DSAT under control while scaling support to more clients.

How do you find the reason behind a DSAT score?

You find the reason behind a DSAT score by reading the conversation that produced it. The score records an outcome, not a cause: it cannot tell an unclear agent from an unpopular policy, a wrong answer or a long wait. Each needs a different fix, and only the conversation shows which one happened. The causes of customer dissatisfaction fall into five groups, and most never reach a survey.

The cause is in the conversation itself. Every dissatisfied rating on a ticket, chat or email has a written conversation attached to it, and that conversation contains the actual sequence of events. Reading those conversations, rather than reading the score, is how a DSAT number becomes an action.

A worked example: from 18 ratings to three drivers

Take the example from the formula above: 18 dissatisfied responses out of 150. Instead of reporting “DSAT is 12%”, open each of the 18 conversations and tag the main driver: agent handling (unclear answer, wrong information, tone), process or policy (a refund rule, a transfer, a wait), or product (a bug or missing feature the agent could not fix). Then count the tags.

The split decides the next step. Agent handling goes to coaching for the agents involved. Process and policy go to the team that owns the rule. Product goes to the product team with the conversations attached as evidence. Doing this at scale, and categorizing what you find rather than collecting anecdotes, is the subject of how to reduce DSAT, and the method for tracing a pattern back to its cause is in our guide to root cause analysis.

Where QA and survey data meet

QA scores what happened inside the conversation against your own standards for accuracy, process and tone. Survey metrics record what the customer felt about it afterward. Kaizo measures that internal quality and traces every score back to the evidence in the transcript, so a dissatisfied rating can be connected to the specific handling behavior behind it rather than debated. Because it runs natively in Zendesk and Salesforce, the conversation and the score sit in the same place. For more on turning those patterns into decisions, see our guide to customer service insights.

When is DSAT not the right metric to watch?

DSAT is the wrong metric to lean on when survey volume is too small, the threshold keeps changing, or you need to know why customers were unhappy. In those cases the number moves on noise, and reading the conversations directly tells you more.

If your team handles a handful of tickets a week, a manager reading every negative conversation will learn more than any percentage, and you do not need a tool for that. If you have no written quality standard yet, start there: a DSAT number can tell you something went wrong, but without a scorecard you cannot say what good looks like. And if bad customer service reviews are your main source of complaints, remember that public reviews come from an even more self-selected group than survey respondents.

See which conversations sit behind your DSAT

Start by reading the conversations behind your dissatisfied ratings, then look for the pattern across them. To see how that works at scale, explore customer support insights in Kaizo or book a meeting for a live demo with realistic sample conversations.

Frequently asked questions

What is the DSAT formula?

DSAT equals the number of dissatisfied responses divided by the total number of responses, multiplied by 100. If 18 out of 150 survey responses fall in your dissatisfied range, your DSAT is 12%. The denominator is responses received, not surveys sent, so customers who never answered are excluded from the calculation entirely.

What is the full form of DSAT in customer service?

DSAT stands for Dissatisfaction Score, sometimes written as dissatisfaction rate. It is the counterpart to CSAT, which stands for Customer Satisfaction Score. Both are calculated from the same post-interaction survey. Note that outside customer service, the same four letters are used for an entirely unrelated standardized test, so context matters.

Should a neutral rating of 3 count as dissatisfied?

It depends on the threshold you choose. On a 1 to 5 scale the common convention is to count ratings of 1 and 2 as dissatisfied, with 3 treated as neutral. Some teams include 3 on the argument that a neutral outcome after a support contact is still a failure, which can roughly double the reported number on identical data. Whichever you pick, write it down and keep it stable.

Do CSAT and DSAT add up to 100%?

No. Neutral responses are counted in the denominator of both but the numerator of neither, so they create a gap between the two figures. On top of that, both metrics are calculated only on customers who responded, and response rates are typically low, so dissatisfaction that never produced a survey response is missing from both.

What is a good DSAT score?

There is no credible universal benchmark, because the number depends entirely on your scale, your chosen threshold, your survey timing and your response rate. A team counting neutral ratings as dissatisfied will report a much higher DSAT than a team that does not, on exactly the same customers. The useful comparison is your own trend over time and the variation between your own queues, channels and issue types.

Why do contact centers track DSAT separately from CSAT?

Because an average absorbs a small group. CSAT can hold steady while the share of genuinely angry customers grows, since movement between the middle ratings offsets it. Dissatisfied customers also drive disproportionate cost through escalations, repeat contacts and churn, and in outsourced environments a maximum dissatisfaction rate is often written into the service level agreement as a target in its own right.

In KaizoDashboardsCoverage, quality trends and coaching impact report natively. No BI project, no monthly assembly job.See Dashboards

On this page

See this in a live demo

We will walk you through Kaizo with realistic sample conversations, so you see the example scored, explained and coached.

Trusted by global support teams

  • Foot Locker
  • Canva
  • GetYourGuide
  • Instacart
  • BlaBlaCar
  • UiPath