NPS follow-up · Use case

“Why did they give us that score?”

NPS follow-up questions ask why someone answered “How likely is it that you would recommend [company] to a friend or colleague?” the way they did, on a scale from 0 to 10. Detractors (0–6), passives (7–8) and promoters (9–10) each need a different follow-up, and when the answer is “it's fine,” Spoke asks one more.

The answer

Detractors are reacting to the price rise; passives are held back by support handoffs.

An example of the line the Agent Results Brief leads with.
The basics

NPS survey questions: the standard question and its 0–10 scale

The standard Net Promoter Score question, from Fred Reichheld of Bain & Company, is “How likely is it that you would recommend [company] to a friend or colleague?” People answer from 0 (not at all likely) to 10 (extremely likely), and the score puts them in one of three groups. Every NPS follow-up question starts from which group they're in.

Detractors0 to 6

Unhappy customers. Ask what's behind the score and what would change it.

Passives7 or 8

Satisfied, not enthusiastic. They count in the total but add nothing to the score. Ask what kept it from a 9.

Promoters9 or 10

Enthusiastic fans who recommend you. Ask why, so you know what to protect.

NPS = % promoters − % detractors (a number from −100 to 100)

01 · The questions

NPS follow-up questions Spoke asks, by score

Under every question is the follow-up Spoke asks when the first answer is vague. That second question is where the real answer usually is.

Detractors: a score of 0 to 6

When to ask: right after someone scores you 0 to 6
  1. What's the main reason for your score?

    If the answer is vague, Spoke asks

    When did that last get in your way?

  2. Which part of working with us affected your score most?

    If the answer is vague, Spoke asks

    What happened the last time you ran into it?

  3. What were you hoping we'd do for you when you signed up?

    If the answer is vague, Spoke asks

    How close have we come to that so far?

  4. What would have to be different for you to score us higher?

    If the answer is vague, Spoke asks

    Of those changes, which one matters most to you?

  5. What, if anything, do you do outside our product to get the job done?

    If the answer is vague, Spoke asks

    How much time does that take you in a normal week?

  6. What would you tell a friend who asked you about us?

    If the answer is vague, Spoke asks

    What's the one thing you'd make sure they knew?

  7. What almost made you stop using us?

    If the answer is vague, Spoke asks

    What kept you from leaving?

Passives: a score of 7 or 8

When to ask: right after someone scores you 7 or 8
  1. What's the one thing that kept this from a 9 or 10?

    If the answer is vague, Spoke asks

    When did you last notice it?

  2. What do you value most about working with us?

    If the answer is vague, Spoke asks

    What would you miss first if it went away?

  3. What's working well enough, but not great?

    If the answer is vague, Spoke asks

    What would great look like there?

  4. What's missing for you right now?

    If the answer is vague, Spoke asks

    What do you do today to get around it?

  5. What would make us an easy recommendation?

    If the answer is vague, Spoke asks

    What's the closest we've come to that so far?

  6. What would make you look at other options?

    If the answer is vague, Spoke asks

    When has that come closest to happening?

Promoters: a score of 9 or 10

When to ask: right after someone scores you 9 or 10
  1. What's the main reason you'd recommend us?

    If the answer is vague, Spoke asks

    What happened the last time you noticed it?

  2. Who would you recommend us to?

    If the answer is vague, Spoke asks

    What problem would they be trying to solve?

  3. How would you describe us to that person?

    If the answer is vague, Spoke asks

    What's the first thing you'd tell them?

  4. What was it like before you started with us?

    If the answer is vague, Spoke asks

    What changed first once you did?

  5. What would you add, if you could add one thing?

    If the answer is vague, Spoke asks

    Which part of your work would that help with?

  6. What's one thing we should never change?

    If the answer is vague, Spoke asks

    What would it mean for you if it did change?

Send these questions Spoke asks each person on their own and follows up on every vague answer.
02 · The interview

How the interview goes.

Every person gets interviewed, not surveyed. Spoke asks, listens, and follows up on what that person actually said. Here's an example.

Spoke
NPS follow-up · 5 min
You scored us a 6. What's the main reason for that score?
Mostly the price. It went up this year and I'm not sure we get more for it.
What did you expect to get for the new price?
The custom reports we asked for last year, at least. We pay more and still build them by hand every month.
Of the reports you build by hand, which one takes the longest?
03 · The answer

What the answer looks like.

Read the answer, not the transcripts: themes ranked by how many people raised them, the quotes behind each, and the places where two groups disagree.

Agent Results Brief Final
Summary

The reasons split by score. Detractors point to the price rise and to slow support, like a new location that took four days of emails to set up. Passives are held back by support handoffs: they explain the problem twice. Promoters praise support when it reaches them fast, so promoters and detractors disagree on it. What to do: show what the new price buys, fix the ticket handoff, then make setup self-serve.

Promoters and detractors disagree on support.
Promoters: fixed before they asked · 40
Detractors: support is too slow · 29
What to do about the score
1Tell customers what the new price includes, with the reports it adds, before the next invoice.
2Pass the full ticket history to whoever picks up a support handoff, so nobody explains twice.
3Let customers add a new location themselves, without emailing support.
What people said · Price rose, value didn't
“Same product, bigger invoice.”
“I'd pay it if the reports came with it.”
“Nobody told us what the increase was for.”
Themes · 212 responses
Detractors: price rose, value didn't58
Passives: explaining a ticket twice47
Promoters: fixed before they asked40
Detractors: support is too slow29
Sentiment
41% positive33% mixed26% negative

An example Agent Results Brief. The counts, themes and quotes are illustrative, not from a real survey.

The follow-up

What Spoke does after “because it's fine”

A fixed follow-up gets one answer and stops. When the reply is “it's fine” or “great service,” Spoke asks one more question about what that person said. One example per score group:

Example · Detractor · scored 5 · quarterly NPS survey
QuestionWhat's the main reason for your score?
First answerIt's fine. It does the job.
Spoke follows upThink of the last time you used it. What were you trying to get done?
Real answerAdding our new location. I had to email support to set it up and it took four days. Everything else is okay, but that's the part my boss saw.
What it uncovered

The 5 isn't about the product as a whole. It's one setup step that needs a support email and makes the customer look slow to their boss.

Example · Passive · scored 7 · after a support ticket closed
QuestionWhat's the one thing that kept this from a 9 or 10?
First answerNothing really. It's fine.
Spoke follows upIf this had been a 9, what would have been different?
Real answerI'd have heard from someone who'd read my first message. I explained the problem twice before anyone opened the screenshot I sent.
What it uncovered

A 7 that looks satisfied hides a handoff problem: the ticket history isn't reaching whoever picks it up.

Example · Promoter · scored 10 · software customer, second year
QuestionWhat's the main reason you'd recommend us?
First answerGreat service, honestly.
Spoke follows upWhat's one moment of that service you still remember?
Real answerMy import failed on a Friday. Support messaged me before I'd filed a ticket and fixed it that night.
What it uncovered

What this promoter values is specific: a problem fixed before they had to ask. That's the thing to protect as you grow.

Choosing the follow-up

Which follow-up to ask for each score

One open follow-up after the score is enough if it fits the group. Here is the first follow-up to ask, what you're trying to learn, and the probe for a vague reply.

ScoreWhat you want to learnAsk firstIf the answer is vague
Detractors (0–6)The specific thing behind the low score, and whether it can be fixed“What's the main reason for your score?”“When did that last get in your way?”
Passives (7–8)The one gap between okay and a recommendation“What's the one thing that kept this from a 9 or 10?”“When did you last notice it?”
Promoters (9–10)What they value, in their words, so you can protect it“What's the main reason you'd recommend us?”“What happened the last time you noticed it?”

The question wording is Fred Reichheld's original, from “The One Number You Need to Grow” (Harvard Business Review, December 2003); Bain & Company's own page uses the shorter “How likely are you to recommend us to a friend or colleague?” The three groups and the formula (% promoters − % detractors, from −100 to 100) follow Bain's Measuring your Net Promoter Score. Timing, by common practice: ask transactional NPS soon after one interaction, relational NPS every quarter or twice a year. The same question has variants, such as product NPS (“recommend [product]”) and eNPS for employees (“recommend [company] as a place to work”). More on writing probes in follow-up questions.

What to avoid

Mistakes that leave you with a score and no reason

The number is the easy part. The reason is what gets lost. More on neutral wording in open-ended survey questions.

01

One fixed follow-up for everyone

A detractor and a promoter are telling you different things. Ask each what fits their score.

  • Bad: The same question for a 2 and a 10
  • Better: What's the one thing that kept this from a 9 or 10?
02

Leading wording

A follow-up that assumes the answer gets agreement, not the reason.

  • Bad: What did we do wrong?
  • Better: What's the main reason for your score?
03

Stopping at “it's fine”

“Fine” and “great service” are where the reason starts. Ask about the last time it happened.

  • Bad: Thanks for your feedback!
  • Better: What's one moment of that service you still remember?
04

Too many questions after the score

Every extra question costs answers to the ones that matter. Keep to the score and one or two open follow-ups.

  • Bad: The score plus ten ratings
  • Better: The score, then one follow-up that fits the group
04 · How to run it

Three steps, ten minutes.

  1. Write or pick the questionStart from “Why did they give us that score?” or say it your own way. Spoke drafts the goal, the audience and the follow-ups; you edit any of it.
  2. Send the linkShare one link however you reach people. They answer in the browser; you set the time: 5, 10 or 15 minutes (10 by default).
  3. Read the answerThemes ranked by how many people raised them, the quotes behind each, and what to do first. Every transcript is there too.
Send these questions

What do you want to learn, and who's answering?

Why did they give us that score?

Drafted the spec. Should I ask promoters who they'd recommend us to, or keep it to why they scored high?

Live survey spec
Goal
The reasons behind each NPS score, for detractors, passives and promoters, and what to fix first.
Audience
Every customer in this quarter's NPS survey, one link by email
Topics
The reason behind the score
What would move it up
Who asks this

People who need the answer.

Customer success managers
Find the reason behind each detractor's score while there's time to act.
Product managers
Learn which gaps keep passives from recommending you.
Support leads
See whether support is why people score you high, or low.
Founders
Turn a quarterly score into the one thing to fix next.
FAQ

Questions about this one.

What is a good NPS follow-up question?

One open question that fits the score. Ask detractors “What's the main reason for your score?”, passives “What's the one thing that kept this from a 9 or 10?”, and promoters “What's the main reason you'd recommend us?” If the reply is vague, ask about the last time it happened.

What is a good NPS score?

Anything above 0 means more promoters than detractors. Compare against your own last score and your industry, not a universal number.

What are the 3 NPS categories?

Detractors score 0 to 6, passives 7 or 8, and promoters 9 or 10. Passives count in the total number of answers but neither add to nor subtract from the score.

How do you calculate NPS?

Subtract the share of detractors from the share of promoters: NPS = % promoters − % detractors. The result runs from −100 (all detractors) to 100 (all promoters).

How do you follow up with detractors?

Reply to each one within a few days, ask about the specific thing they named, and tell them what you changed.

What's the difference between relational and transactional NPS?

Relational NPS asks about your company overall, on a regular schedule such as every quarter. Transactional NPS asks right after one interaction, such as a purchase or a support ticket. The follow-ups on this page work for both; for transactional NPS, ask about that one interaction.

Related

Ask your first question.

Free to start. No card. Your first ten agent surveys are on us.