KPIs and metrics

Using NPS in Customer Support: Scores, Surveys and Follow-Up

How Net Promoter Score works, how to use it after support calls, its strengths and weaknesses, survey design tips and how to turn scores into action.

Call editorial team · Published · 5 min read

A customer finishes a support call, then gets a one-question survey: how likely are you to recommend us to a friend or colleague? Their answer feeds a number that appears on a dashboard. But what does that number say about the call, the product, the company, or the customer's mood that day?

A support team lead reviewing customer feedback results on a laptop at a desk
Illustrative image

This guide explains how NPS works, where it fits in support, how it differs from CSAT, how to design the survey and, most importantly, how to turn scores into improvements. It sits beside Measuring CSAT After Calls and Customer Effort Score and the overall Call Center KPIs.

How NPS works

NPS rests on one question: "How likely are you to recommend us to a friend or colleague?" Respondents answer from 0 to 10. They fall into three groups.

The three groups

  • PromotersScore 9 or 10. Enthusiastic and likely to speak well of you.
  • PassivesScore 7 or 8. Satisfied but unenthusiastic, open to competing offers.
  • DetractorsScore 0 to 6. Unhappy and more likely to speak against you or leave.

The score is the share of promoters minus the share of detractors, shown as a number between minus 100 and plus 100. Passives count in the total but not in the subtraction. A team with no detractors and no promoters, because everyone is passive, scores zero.

Because it is a single, simple question, NPS is easy to run, easy to compare over time and easy to explain to senior colleagues.

NPS in a support context

NPS was designed as a measure of loyalty to a company, not of a single interaction. That distinction matters in support, where teams often send it after a call.

Relationship NPS versus transactional NPS

Relationship NPSAfter-call NPS
What it asks aboutThe overall relationship with the companyThe experience that just happened, plus everything else
When it is sentPeriodically, such as quarterlyRight after a call or a resolved case
Influenced byProduct, price, delivery, brand and supportProduct and mood as well as the call itself
Best useTracking loyalty trendsSpotting unhappy customers while the case is fresh

Because after-call NPS blends the call with everything else, it is wise to use it together with a question about the call itself. See Measuring CSAT After Calls. A customer may love your product, hate the wait and still score you a 9; or the reverse.

Strengths and weaknesses

StrengthsWeaknesses
One question, easy to run and compareDoes not explain why on its own
Familiar to managers and boardsScores are shaped by factors support cannot control, such as price or product bugs
Splits customers into groups you can act onCulture and wording affect how people score
Open comment adds the storySmall samples swing wildly; non-responders are invisible

Designing the survey

A simple after-call survey flow

  1. Choose the triggerAfter every call, or after a case is resolved, so the timing is consistent.
  2. Ask one scored questionUse the standard wording and the 0 to 10 scale.
  3. Ask whyOne open question, optional and short.
  4. Say thanksTell the customer what happens with the answers.
  5. Sample sensiblyAsk a share of callers if you are worried about survey fatigue.

Timing and tone matter. Send the survey soon after the event, while the memory is fresh, and avoid asking the same person repeatedly. If someone answers a survey every week, they will stop reading the question and the data will degrade. Keep a record of when each customer was last asked and leave a gap before asking again.

Close the loop

The real value of NPS in support is the follow-up. Detractors have told you something is wrong, and a prompt, personal reply can change the relationship. Even a short call to understand the issue can recover trust.

A close-the-loop routine

  1. Flag detractorsList low scores and comments daily.
  2. Open the callListen to or read the conversation behind the score.
  3. Decide the actionIs this a fix, an apology, a product issue or a misunderstanding?
  4. Reach outA named person contacts the customer, and keeps it brief.
  5. Record the causeTag themes so patterns show up across many scores.

Also read the promoters. They tell you what you do well, and it is worth sharing that with the team. See Finding Knowledge Gaps from Calls for turning feedback themes into content and training.

A hypothetical example

Imagine a support team whose after-call NPS drops from one month to the next. The first reaction is to blame the agents. Reading the comments tells a different story: many detractors mention a delayed delivery, and the calls were polite and helpful. The score fell because of a logistics problem, not because of the calls.

The team passes the finding to the operations group, tells the callers affected what is happening and adds a note to the opening script. Next month the comments change tone even though the delay continues, because customers feel informed. This is an invented example, but it shows why the comments matter more than the number and why support often acts as the early warning system for the whole company.

Using the score wisely

NPS in support readiness

  • Decide whether you need relationship NPS, after-call NPS or both
  • Pair NPS with a short question about the call itself
  • Add an open question for the main reason
  • Set up a routine to follow up detractors
  • Segment results by queue and topic
  • Review comments with the team each month
  • Avoid linking scores to individual pay
  • Explain to customers how answers are used

Doing it in Call

In Call, the Review and coaching area has a What customers said panel for the last 30 days. Its tiles show satisfaction out of 5, net promoter, how many replied and comments, with a list of unhappy customers with the call attached so you can open the recording. You create a survey by naming it, choosing whether it is asked after every call ends or when a case is resolved, and setting the share of those it should ask. A by-agent view shows replies, satisfaction and detractors per agent. Start with the unhappy customers list: a specific caller with the call attached is easier to act on than an average. Treat the by-agent view as a coaching aid, not a league table.

Frequently asked questions

What is a good NPS?

There is no universal answer. Scores differ by industry, region and survey method, so compare with your own past results and with similar surveys that use the same method, not with a number from another sector.

Is NPS the same as CSAT?

No. NPS asks how likely someone is to recommend you and is a loyalty measure. CSAT asks how satisfied they were with something specific, such as a call. Many teams use both.

Should we send NPS after every call?

It depends. After-call NPS is influenced by more than the call. Sampling a share of callers, and pairing it with a question about the call, helps avoid fatigue and confusion.

How many responses do we need?

Enough that one or two answers cannot swing the score. Small samples give unstable results, so look at trends over longer periods and be cautious with small queues.

Can we use NPS to rate individual agents?

With care. Scores reflect many things an agent cannot control. Use agent-level data to find coaching opportunities and read the calls behind low scores before drawing conclusions.

What should we do with detractor feedback?

Read the comment, open the call and follow up personally where it makes sense. Record the cause and look for themes across many detractors so you can fix the root problem.

Review customer feedback and create an after-call survey in Call

In the demo console you can try incoming calls in a simulation.

Related guides