Customer Satisfaction Score (CSAT): CSAT is a metric that measures how satisfied a customer was with a specific interaction or transaction, usually collected through a short post-interaction survey and expressed as a percentage of respondents who rated the experience positively. In a call center and customer support contract, CSAT is rarely just a feedback tool. It is often a contractual SLA metric tied to penalties, bonuses, or renewal decisions, which changes how it should be evaluated.
How do I calculate a CSAT score?
CSAT is calculated by dividing the number of satisfied responses (usually the top one or two ratings on a scale) by the total number of survey responses, then multiplying by 100. If a vendor sends 500 post-call surveys and 410 customers select “satisfied” or “very satisfied,” the CSAT score is 82%.
The formula looks simple, but three variables change the outcome dramatically: the scale used, the response threshold counted as “satisfied,” and the response rate. A 5-point scale where only “5” counts as satisfied produces a very different number than a 5-point scale where “4” and “5” both count. I would never accept a CSAT figure in a proposal without first asking which scale and which threshold produced it.
What is a good CSAT score?
A good CSAT score for most customer service operations sits between 75% and 85%, though the right benchmark depends heavily on industry, channel, and how strictly the vendor counts satisfied responses. Complex technical support or collections work often runs lower, sometimes 65% to 75%, simply because the underlying interaction is inherently less pleasant regardless of agent quality.
I would not treat a single CSAT number as good or bad in isolation. A 90% CSAT score from a vendor surveying 8% of interactions with a lenient 3-point scale tells you less than a 80% score from a vendor surveying 40% of interactions with a strict 5-point scale where only the top rating counts. Ask for the sample size and response rate before reacting to the headline number.
How do you interpret CSAT scores in a vendor proposal?
CSAT scores in vendor proposals should be interpreted alongside sample size, survey scale, response rate, and how disputed or excluded scores were handled, not taken at face value. Vendors pitching your account have every incentive to present the most flattering version of a number that is easy to manipulate.
Three things I check before trusting a CSAT figure in a RFP:
| What to check | Why it matters | Red flag |
|---|---|---|
| Survey scale and threshold | A 3-point scale inflates scores versus a 5 or 7-point scale | Vendor won’t disclose the scale used |
| Response rate | Low response rates (under 10%) skew toward extreme opinions | “Historical average” with no sample size given |
| Dispute/exclusion policy | Some vendors exclude scores tied to escalations or complaints before calculating CSAT | Final number excludes any negative outlier |
A vendor quoting a 92% CSAT with no context is showing you capacity to produce a good-looking slide, not operating discipline. I would ask for the raw survey data, not just the rolled-up percentage, before shortlisting anyone on the strength of a satisfaction number.
How should CSAT be structured in a BPO contract?
CSAT should be written into a Master Service Agreement with a fixed survey scale, a minimum sample size or response rate, and a clear, narrow definition of which scores can be excluded as disputed, so the metric cannot be redefined mid-contract to hit a target. Without these guardrails, CSAT becomes a number the vendor controls rather than a number that reflects the customer experience.```
On r/callcentres and r/BPOinPH, agents and operators describe the same recurring problem from the ground up: policies outside the agent’s control (a delayed refund, a hold time, a hard company rule) generate “DSATs” that get baked into the vendor’s overall score, and unmet CSAT or AHT SLAs in the SOW can trigger financial penalties regardless of whether the root cause was staffing, process, or client policy. That is exactly why the contract language matters more than the metric itself.
When I review a MSA, I want to see: the exact survey question and scale locked in as an appendix, not left to be “mutually agreed” later; a minimum sample size or response rate below which CSAT cannot be used to trigger a penalty or bonus; and a documented, auditable process for disputing or excluding a score, with a cap on how many scores can be excluded per period. Without that cap, a vendor can quietly exclude every negative outlier and report a clean number that has nothing to do with the actual customer experience.
I would also pair CSAT with a second metric, ideally first contact resolution or a comparable outcome measure, because a vendor chasing CSAT in isolation can inflate it by closing tickets fast, offering unauthorized discounts, or steering surveys toward happy customers only. Comparing cost per resolved issue against the CSAT trend tells you more than either number alone. This is the same dynamic operations teams debate on r/sysadmin around Goodhart’s Law: once a metric becomes the target, people find ways to hit the target that have nothing to do with the underlying goal.
FAQ
Before you accept any vendor’s reported CSAT, walk through the basics below.
Get outsourcing quotes once you have a CSAT definition and audit clause you are comfortable enforcing.