Customer Satisfaction Score (CSAT): A survey-based metric that captures how satisfied a customer was with a specific interaction, transaction, or support experience, calculated as the percentage of respondents who gave a positive rating out of all respondents who completed the survey.
CSAT is one of the most common quality metrics in outsourced customer service. If you are evaluating a BPO for voice, chat, email, or back-office work, you will almost certainly see CSAT mentioned in every proposal. The question is whether the vendor is measuring it rigorously or just reporting a number that looks good on a slide.
How Is CSAT Calculated?
CSAT is calculated by dividing the number of satisfied responses by the total number of survey responses, then multiplying by 100 to get a percentage. Satisfied responses are typically those that fall in the top one or two tiers of the scale used.
The formula:
CSAT (%) = (Number of Satisfied Responses / Total Responses) × 100
A realistic example: you send a post-interaction survey to 500 customers. 410 respond. Of those, 320 rate the experience 4 or 5 out of 5. CSAT = (320 / 410) × 100 = 78%.
The rating scale varies by vendor and client:
| Scale | ”Satisfied” Counts As |
|---|---|
| 1 to 5 (most common) | Ratings of 4 or 5 |
| 1 to 3 | Rating of 3 |
| 1 to 10 | Ratings of 8, 9, or 10 |
| Binary (yes/no) | “Yes” responses only |
This matters more than it sounds. A vendor reporting CSAT off a 1-to-3 scale and another reporting off a 1-to-5 scale are not directly comparable. Always ask which scale is used and which responses count as “positive.”
What Is a Good CSAT Score in BPO Operations?
A CSAT score above 80% is generally considered healthy for outsourced customer service operations, though the right benchmark depends heavily on industry, channel, and process complexity. From operating experience, here is what I would treat as indicative ranges:
| Range | What It Suggests |
|---|---|
| Below 70% | Significant service quality issues; investigate root causes immediately |
| 70% to 79% | Below average; acceptable only during ramp-up or for high-complexity processes |
| 80% to 89% | Solid, within normal operating range for most support outsourcing |
| 90% and above | Strong; typical for well-run, low-complexity, or high-tenure teams |
These are indicative ranges based on operating experience, not published benchmarks. Your business may have its own internal targets that differ.
I would also note that CSAT can be inflated by survey design (leading questions, low response rates, only sending surveys after resolved tickets) or deflated by process factors outside agent control (shipping delays, product defects, policy limitations). A vendor’s CSAT number alone tells you less than how it is measured and what it is tied to.
Why CSAT Matters When Evaluating a BPO
CSAT is one of the clearest signals of whether an outsourced team is actually delivering the customer experience you are paying for, not just hitting call handle times or ticket volume targets. A vendor can close 500 tickets a day and still damage your brand if resolution quality is poor.
For buyers comparing call center outsourcing vendors, CSAT serves as the quality counterweight to efficiency metrics like AHT (average handle time). High throughput with low CSAT usually means agents are rushing, skipping resolution steps, or transferring too quickly.
I tell buyers to ask three questions when a vendor presents CSAT data:
- What is the survey trigger? (Post-call, post-resolution, periodic, random sample?)
- What is the response rate? A 12% response rate is not representative.
- How does CSAT feed into agent coaching, QA scoring, and performance reviews?
If CSAT is just a reporting number and not connected to how agents are managed, it is decorative. Good operations use low CSAT scores to trigger root-cause analysis, coaching, or process review within days, not quarters.
How CSAT Relates to Other Quality Metrics
CSAT measures satisfaction with a specific moment; it sits alongside NPS (Net Promoter Score) and FCR (First Contact Resolution) to give a fuller picture of service quality. Each metric captures something different:
| Metric | What It Measures | When to Use It | |---|---| | CSAT | Satisfaction with one interaction | Post-transaction quality tracking | | NPS | Likelihood to recommend (relationship-level) | Brand loyalty, long-term retention | | FCR | Whether the issue was resolved in one contact | Efficiency and resolution quality | | QA Score | Internal agent quality assessment | Process compliance, coaching |
For buyers working with Philippines or India-based BPO teams, CSAT is often the primary external quality metric, supplemented by internal QA scoring. FCR and CSAT together are more useful than either alone.
The mistake I see often: a buyer locks CSAT into the SLA at a fixed minimum (say, 80%) without tying it to response rate or survey methodology. The vendor hits 81% by surveying only resolved tickets and suppressing escalation cases. Define the measurement method in the contract, not just the target number.
Before choosing a BPO, do not just ask what their CSAT score is. Ask how they survey, what they do when scores drop, and whether CSAT is connected to how agents are coached and managed. The score matters less than the system behind it. Compare providers and request that detail upfront at /get-quotes/.