Net Promoter Score (NPS): a customer loyalty metric calculated by asking customers how likely they are to recommend a company on a 0 to 10 scale, then subtracting the percentage of Detractors (0 to 6) from the percentage of Promoters (9 to 10). In a BPO relationship, the same term gets applied to two different things at once: how the outsourcing buyer feels about the vendor, and how the buyer’s own customers feel about the brand. Treating those as one metric is where scorecards break down.
Is NPS the same thing whether it’s measured for the client or the end customer?
No. Client NPS measures whether the outsourcing buyer would recommend that BPO to another business, and it belongs in quarterly business reviews as an account-health signal. End-User NPS measures whether the buyer’s own customers would recommend the buyer’s brand, collected through post-interaction surveys run by the contact center.
These are structurally different things. Client NPS reflects the vendor relationship: contract flexibility, responsiveness of the account manager, quality of reporting, how well escalations get handled. End-User NPS reflects the buyer’s brand, product, and pricing, filtered through one support interaction. A BPO can run a flawless call and still get hit with a Detractor score because the end user is angry about a shipping delay or a price increase that has nothing to do with the agent. I would keep these two numbers on separate lines of any scorecard or dashboard, with the source and sample size labeled next to each, so nobody confuses vendor satisfaction with brand satisfaction when a contract comes up for renewal.
This is also the exact failure mode agents complain about in call center forums: a detractor score driven by a policy decision, a price increase, or a shipping delay outside the agent’s control still lands on that agent’s individual performance review. If a client’s commercial SLA ties agent bonuses or corrective action directly to raw End-User NPS, without separating out interaction quality from product or policy dissatisfaction, the metric stops measuring service and starts measuring how angry customers already were before they called.
How is NPS calculated, and what counts as a good score?
NPS is calculated as %Promoters minus %Detractors, using a 11-point scale from 0 to 10, where 9 and 10 are Promoters, 7 and 8 are Passives (excluded from the math), and 0 through 6 are Detractors. The result is a single number ranging from -100 to +100, reported as a plain integer, not a percentage.
Example: if 500 customers respond to a survey, 250 give a 9 or 10 (50% Promoters), 150 give a 7 or 8 (Passives), and 100 give 0 to 6 (20% Detractors), the NPS is 50 minus 20, or +30. Treat that as an indicative benchmark, not a hard statistic, because what counts as “good” depends heavily on industry, survey timing, and response rate. A retailer and a health insurer will have very different baselines, and a low response rate can skew the result toward whoever felt strongly enough to answer, usually the most satisfied or most frustrated customers rather than the median one.
Why does using NPS as an individual agent metric cause problems?
NPS was built as a relational, account-level indicator, not a transactional one, and applying it to a single agent’s performance conflates two things that do not belong together: how the customer feels about the company overall, and how the agent handled one call. An agent has no control over pricing, product defects, delivery timelines, or company policy, all of which routinely drive a Detractor score regardless of call quality.
This is a known point of friction between BPO leadership and frontline staff. Discussions among contact center agents describe cases where team leads review low NPS scores tied to bonuses or performance improvement plans, only to find the complaint was about a corporate decision the agent had no part in and could not have fixed on the call. If a client wants to measure agent-level performance, Customer Satisfaction Score (CSAT) tied to the specific interaction is a tighter fit, since it asks about the transaction rather than the whole relationship. NPS still has a role at the account or program level, just not as a lever for individual pay or discipline.
How should NPS show up in an outsourcing contract or SLA?
NPS belongs in an outsourcing SLA as a program-level or account-level indicator, reviewed on a rolling basis with enough sample size to be statistically meaningful, not as a hard target tied to individual agent pay. A workable structure separates Client NPS (vendor relationship health, reviewed quarterly) from End-User NPS (brand and product sentiment, reviewed monthly or quarterly with trend context), and uses CSAT or quality-monitoring scores for interaction-level agent evaluation.
| Metric | What it measures | Right place to use it |
|---|---|---|
| Client NPS | Buyer’s willingness to recommend the BPO vendor | Quarterly business review, account health |
| End-User NPS | End customer’s willingness to recommend the buyer’s brand | Program-level trend tracking, not individual agent scoring |
| CSAT | Satisfaction with a specific interaction or resolution | Agent-level scorecards and coaching |
When I look at a proposed SLA that ties agent bonuses directly to raw NPS, I treat it as a red flag on process design, not just a compensation detail. It usually means nobody has separated what the agent controls from what the company controls, and that gap tends to show up later as attrition or gamed survey responses.
If you are comparing vendors and want to see how they structure scorecards and SLAs around metrics like this, get outsourcing quotes and ask each one directly how they separate relational and transactional metrics in reporting.