Every support and CX team eventually faces the same question from leadership: what is our NPS? For teams that have never measured it, the term shows up in a board deck or investor update before anyone has defined what it means for their own customers.
At its simplest, NPS is a loyalty metric that asks customers one question: how likely are you to recommend this business to a friend or colleague? The answer, scored 0 to 10, sorts customers into three groups and produces a single number between negative 100 and positive 100.
This guide is written for support and CX teams deciding whether NPS belongs alongside the metrics they already track. I
TL;DR
- NPS helps businesses measure customer loyalty with one simple question: how likely are you to recommend us to a friend?
- NPS scores customers as Promoters, Passives, or Detractors based on a 0 to 10 rating.
- The formula subtracts the percentage of Detractors from the percentage of Promoters to produce a score from negative 100 to positive 100.
- A score above 0 is generally acceptable, above 50 is strong, and above 70 is considered world class.
- NPS and CSAT measure different things and work best together, not as substitutes for each other.
- Teams already running CSAT can decide whether NPS adds a genuinely new signal before adopting it.
What is NPS?
NPS, or Net Promoter Score, is a loyalty metric that asks customers how likely they are to recommend a business, on a scale of 0 to 10, and converts the answers into a single score from negative 100 to positive 100.
Customers who respond are grouped into three categories based on their rating. The resulting score reflects the balance between customers likely to promote the business and customers likely to discourage others from using it. Bain and Company, the consulting firm that developed the metric in 2003, designed it as a simpler alternative to lengthy satisfaction surveys. The bet was that one well-chosen question could predict loyalty about as well as a twenty-question survey, and the metric spread widely because it delivered on that promise for many businesses.
Why NPS caught on beyond its original use case
NPS started inside enterprise B2B relationships, where a champion’s willingness to recommend a vendor carried real weight in renewal conversations. It has since spread into retail, subscription software, healthcare, and financial services, each keeping the same three-way classification and formula intact.
Why does NPS matter for a business?
NPS matters because it gives leadership a simple, comparable number for tracking customer loyalty over time, and loyalty is a leading indicator of referrals, renewals, and long-term revenue.
A single transaction can go well even when the underlying relationship is fragile. NPS is built to catch that fragility before it shows up as churn. A customer who rates an interaction five out of five on CSAT can still answer a 6 on the recommend question, because the immediate experience was fine but the overall relationship has not earned real advocacy yet.
The metric also creates a shared language across departments. Product, support, and executive teams can look at the same trend line and share a reference point, even though each team influences the score through different levers: reliability, service quality, pricing fairness, and communication consistency.
Pro Tip: NPS works best as a trend line, not a single snapshot. A score of 35 means very little in isolation. A score of 35 that climbed from 20 over four quarters tells a real story leadership can act on.
How do you calculate NPS?
NPS is calculated by subtracting the percentage of Detractors from the percentage of Promoters, ignoring Passives entirely, to produce a final score between negative 100 and positive 100.
Every respondent falls into one of three groups:
- Promoters (score 9 to 10): Loyal customers likely to keep buying and refer others.
- Passives (score 7 to 8): Satisfied but not enthusiastic, and open to switching for a better offer.
- Detractors (score 0 to 6): Unhappy customers at risk of churning or speaking negatively about the business.
Formula:
NPS = % Promoters − % Detractors
Worked example: A survey of 200 customers returns 120 Promoters, 50 Passives, and 30 Detractors. Promoters make up 60% of respondents, Detractors make up 15%. Subtracting 15 from 60 gives an NPS of 45.
What counts as a good NPS score?
A score above 0 shows more promoters than detractors. Above 20 is generally solid, above 50 is strong, and above 70 is considered world class.
| Score range | Interpretation |
|---|---|
| Below 0 | More detractors than promoters, needs urgent attention |
| 0 to 20 | Fair, room for meaningful improvement |
| 20 to 50 | Good, majority of customers satisfied |
| 50 to 70 | Excellent, strong customer loyalty |
| Above 70 | World class, rare across most industries |
Benchmarks vary by industry. A software company and a retail chain will not share the same baseline, so compare scores within the same industry rather than against a universal target. Always ask what the realistic ceiling looks like for a given category before judging a specific number.
How is NPS different from CSAT?
NPS measures long-term loyalty with one relationship-level question. CSAT measures satisfaction with a specific interaction or transaction, asked right after it happens.
| Aspect | NPS | CSAT |
|---|---|---|
| Question asked | How likely are you to recommend us? | How satisfied were you with this interaction? |
| Timing | Periodic, relationship-level | Immediate, right after a ticket or purchase |
| Scale | 0 to 10 | Usually 1 to 5 |
| What it predicts | Long-term loyalty and referral behavior | Whether a specific experience met expectations |
| Best used for | Tracking overall brand sentiment over time | Diagnosing service quality on individual interactions |
The two metrics answer different questions. CSAT tells a support team whether yesterday’s ticket resolution felt good to the customer. NPS tells the business whether the overall relationship is strong enough that the customer would vouch for it publicly. A team already tracking satisfaction survey data has the interaction-level signal covered. NPS adds the relationship-level signal on top of it.
Consider a customer who has filed six support tickets over a year, each earning a five-star CSAT rating because the agents were fast and helpful. The customer still needed six tickets for a product that should have needed one. Their NPS response reflects that frustration even though every CSAT score looked perfect, exactly the blind spot NPS is designed to catch.
Pro Tip: Running NPS and CSAT side by side only works if the team knows which question each one answers. A support team that swaps in NPS to replace CSAT loses the day-to-day quality signal that actually helps agents improve.
How do you collect NPS data?
Businesses collect NPS through email surveys, in-app prompts, post-interaction surveys, and SMS, timed to fit the customer relationship rather than a single transaction.
- Email surveys: Sent periodically, often quarterly, to a broad customer base. This is the most common channel for relationship NPS because it reaches customers outside of any specific interaction.
- In-app or onsite prompts: Triggered at moments of high engagement, such as after a milestone like completing a major project inside the product.
- Post-interaction surveys: Sent after a support ticket or purchase, though this blurs into CSAT territory if overused for NPS and should be reserved for major moments rather than every interaction.
- SMS and text surveys: Useful for mobile-first customer bases needing a fast response, particularly in industries where email open rates are low.
Choosing the right channel depends on where the business already has the customer’s attention and how often they want to be surveyed. A subscription business might time email to the renewal date. A field services company might prefer SMS after a technician visit.
What is the difference between relationship and transactional NPS?
Relationship NPS measures overall loyalty on a recurring schedule. Transactional NPS measures loyalty right after a specific interaction, closer to how CSAT is used.
| Aspect | Relationship NPS | Transactional NPS |
|---|---|---|
| When it’s sent | Quarterly or twice a year, independent of any single interaction | Immediately after a purchase, support ticket, or onboarding step |
| What it tracks | How the overall relationship trends over time | Loyalty tied to one specific moment |
| Who typically sees it | Leadership and boards, as the primary reported metric | Operational teams, for immediate follow-up |
| Best used for | Long-term loyalty trend across the full customer base | Major milestones, such as post-onboarding or post-renewal |
| Risk if overused | Low response rates if sent too often | Blurs into CSAT territory if applied to every interaction |
Relationship NPS asks the core question every quarter or twice a year, independent of any single interaction. It tracks how the relationship trends over time and is the version most commonly reported to leadership.
Transactional NPS asks the same question immediately after a purchase or support ticket, tying the loyalty question to a specific moment. Most mature programs run relationship NPS as the primary metric and use transactional NPS sparingly for major milestones.
Why do NPS programs fail even when the score looks fine?
Programs fail when the score becomes the only artifact anyone looks at. No follow-up process, no segmentation, and no connection to day-to-day operations turn NPS into a number nobody acts on.
No defined follow-up process
A Detractor response that goes unanswered for weeks teaches the customer the survey was theater. The single highest-leverage fix is a fast, defined path from a low score to a human follow-up, ideally within 48 hours.
Treating the score as the whole story
A quarterly number without open-ended comments or segmentation tells leadership that something changed, not why. Programs that skip the qualitative layer end up debating causes with no evidence to settle the argument.
Survey fatigue from poor sequencing
Sending an NPS survey the same week as a CSAT survey and a renewal check-in trains customers to ignore all of them. Sequencing surveys with intention protects response rates across every program.
No link between the score and daily operations
A number that lives only in a quarterly board deck never reaches the teams whose daily work shapes it. Programs that route Detractor themes back to product and support planning are the ones that see the score move.
Pro Tip: If nobody on the support or CX team can name last quarter’s top Detractor theme, the program has become a reporting exercise rather than a loyalty program.
How does a support-first team decide whether to add NPS?
Support-first teams already tracking CSAT should check for genuine loyalty blind spots before adding NPS, using a simple three-question audit rather than adopting the metric by default.
This section introduces the NPS Fit Check, a three-question audit for teams deciding whether NPS is worth the added survey load.
Question 1: Does leadership need a loyalty number, or a service-quality number? If the ask is “are customers happy with our support,” CSAT already answers that. If the ask is “would customers recommend us,” CSAT cannot answer that on its own.
Question 2: Can the team commit to acting on Detractor responses? NPS without a follow-up process just produces a number nobody uses. A team needs a defined path for reaching out to Detractors within days, not months.
Question 3: Will survey frequency create fatigue on top of existing CSAT surveys? Stacking a quarterly NPS survey on top of after-every-ticket CSAT surveys can overload customers. Space them out and be deliberate about how often each customer is asked anything.
Worked example: A 15-person support team already sends CSAT after every resolved ticket, averaging a 92% satisfaction rate. Leadership asks for the company’s NPS ahead of a fundraising round. The team runs the NPS Fit Check, confirms the ask is genuinely a loyalty number, and commits to a quarterly relationship NPS survey with a defined 48-hour follow-up on any Detractor response.
Pro Tip: The fastest way to avoid NPS becoming a vanity number is to define the Detractor follow-up process before the first survey goes out, not after the results come back.
What does a well-run NPS program look like?
A well-run program tracks the score as a trend, follows up with every Detractor within days, segments results by customer type, and routes recurring themes back to the teams that can fix them.
Concrete signals to look for:
- NPS reported as a multi-quarter trend, not a single isolated number
- Every Detractor response triggers a follow-up within 48 to 72 hours
- Results segmented by plan tier, tenure, or region rather than blended
- Open-ended comments read and tagged into recurring themes, not archived unread
- Relevant teams see the themes tied to their area every quarter
- Survey timing coordinated with other feedback channels to avoid fatigue
What are the common mistakes teams make when starting an NPS program?
Common mistakes include skipping the follow-up process, surveying too often, ignoring segmentation, and treating the first score as a permanent baseline instead of a starting point.
Mistake 1: No follow-up process for Detractors
Symptom: Low scores get reported but nothing happens afterward.
Cause: No owner assigned to respond to negative feedback.
Fix: Assign a named owner and a 48-hour response window before the first survey goes out.
Mistake 2: Surveying too frequently
Symptom: Response rates drop every quarter.
Cause: NPS stacked on top of CSAT without coordination.
Fix: Build a shared survey calendar so no customer is asked more than once in a short window.
Mistake 3: Reporting one blended score
Symptom: The score looks stable, but specific segments are quietly churning.
Cause: No segmentation by plan tier, tenure, or region.
Fix: Break every report into at least three segments before presenting to leadership.
Mistake 4: Treating the first score as fixed
Symptom: Teams stop questioning the number after the first survey.
Cause: No plan to track the score as a trend over multiple survey cycles.
Fix: Commit to at least four consecutive survey cycles before drawing conclusions about direction.
What are the common limitations of NPS?
NPS has real limitations: a single score lacks context, survey timing can skew results, and the score is vulnerable to gaming or selection bias if not run carefully.
- The score lacks context by itself: A 45 tells you the balance of sentiment, not why. Pair NPS with open-ended follow-up questions.
- Timing skews results: Surveying right after a bad outage produces a very different score than a stable quarter.
- Gaming and selection bias are real risks: Cherry-picking who gets surveyed inflates the number without reflecting reality.
- Passives are underexplored: Most programs focus on converting Detractors and rarely look at moving a Passive into a Promoter.
How do you improve a low NPS score?
Improving NPS starts with closing the loop on Detractor feedback, addressing onboarding friction first, and segmenting responses before deciding what to fix.
- Close the feedback loop systematically: Every Detractor response should trigger a follow-up within days, not a quarterly review.
- Address onboarding first: Early-stage friction often drives the loudest Detractor responses and is usually the cheapest to fix.
- Segment before you act: A single low score can hide very different problems across customer segments. Break down responses by plan tier, tenure, or region before assuming one fix applies everywhere.
- Activate promoters, not just detractors: Improving a low score is not only about fixing what is broken. Turning Promoters into referral sources compounds the score from the other direction.
Where do support and CX teams go from here?
NPS measures loyalty at the relationship level, while CSAT measures satisfaction at the interaction level. Teams already running CSAT should confirm NPS fills a genuine gap before adding it.
Three things carry the outcome:
- NPS and CSAT answer different questions, and running both only helps if the team knows which is which.
- A Detractor follow-up process matters more than the score itself.
- Treat the first score as a starting point, not a verdict, and track it across several cycles before drawing conclusions.
Teams weighing whether to add NPS can start by auditing what their current satisfaction survey data already shows, and whether the gap is really about loyalty or about service quality.
Frequently Asked Questions
What is NPS?
A loyalty metric that scores customers 0 to 10 on how likely they are to recommend a business, producing a score from negative 100 to positive 100.
How do you calculate NPS?
Subtract the percentage of Detractors from the percentage of Promoters, and ignore Passives entirely in the formula.
What is a good NPS score?
Scores above 20 are generally solid, above 50 are strong, and above 70 are considered world class, though benchmarks vary by industry.
What is the difference between NPS and CSAT?
NPS measures long-term loyalty with one relationship question. CSAT measures satisfaction with a specific interaction right after it happens.
How often should you send an NPS survey?
Send relationship NPS quarterly or twice a year, and reserve transactional NPS for major milestones to avoid survey fatigue.
What is the difference between relationship and transactional NPS?
Relationship NPS tracks loyalty on a recurring schedule. Transactional NPS ties the same question to a specific interaction or purchase.
