NPS Questions: What to Ask Promoters, Passives, and Detractors (With Examples)

Most teams focus on the NPS score. The NPS question that generates it is a single line, and it has not changed much since Fred Reichheld published it in 2003. What changes everything is what you ask next. The follow-up question is where NPS becomes useful for product decisions.

This post covers the standard NPS question, why the exact wording matters, and the specific follow-up questions to ask each score group. Promoters, Passives, and Detractors are in different situations and have different things to tell you. Asking them all the same follow-up question wastes that signal.

The Standard NPS Question

The question Bain and Company published in the Harvard Business Review in 2003:

On a scale of 0 to 10, how likely are you to recommend [Company/Product] to a friend or colleague?

Three things about the wording matter: the scale, the comparison frame, and the noun you use for what you are asking about. Each one affects the quality of the data you get back.

Why 'friend or colleague' and not just 'friend'

The 'colleague' frame makes the question relevant for B2B products. Recommending a project management tool to a friend is a different mental model than recommending it to a colleague who needs it for work. Including 'colleague' keeps the question in a professional context for SaaS products. If you are running NPS for a consumer product, 'friend' alone works fine.

Why 0-10 and not 1-10 or 1-5

The 0-10 scale has a built-in anchoring effect. Zero feels like a genuine 'I would never recommend this' option. A 1-10 scale loses that floor. The three bands - Detractors (0-6), Passives (7-8), Promoters (9-10) - were calibrated against purchase behavior data over time, not set by intuition. Changing the scale invalidates your ability to benchmark against industry data.

Use your product name, not 'our company'

For SaaS in-product NPS, replace [Company] with your product name. 'How likely are you to recommend Mapster to a friend or colleague?' is more specific than 'our company.' It focuses the respondent's answer on the product experience, which is what you can directly improve. Company-level NPS captures brand perception and support quality alongside product quality, making it harder to act on.

The Follow-Up Question is Where NPS Gets Useful

The score tells you how many users are Promoters, Passives, and Detractors. The follow-up tells you why. Without it, you have a trend line and no action.

Most teams ask the same follow-up to every respondent: 'What is the main reason for your score?' That question is better than nothing, but it gets broad answers. Tailoring the follow-up to each score group gets you specific answers. A Detractor has a problem. A Passive has a gap. A Promoter has a reason they love you. Each needs a different question.

Three levels of follow-up quality:

• Bad: 'Please share any feedback you would like to provide.' Too open, no direction, produces vague answers.
• Better: 'What is the main reason for your score?' Generic but directive. Works as a baseline for all groups.
• Best: Different questions for different score groups. Specific to the situation each respondent is in.

NPS Follow-Up Questions for Detractors (0-6)

Detractors gave you a low score and have a reason. The job of the follow-up is to surface that reason with as little friction as possible. They are already willing to tell you what went wrong. Your question just needs to give them the opening.

Follow-up questions that work for Detractors:

• "What went wrong?" - Direct, low friction, invites a full explanation. Best for 0-3.
• "What is the main reason for your score?" - Reliable across the full Detractor range (0-6).
• "What would need to change for you to give a higher score?" - Best for 4-6, where the issue is specific and narrower.
• "What is the most frustrating thing about [Product]?" - Best for 0-3, where the problem is strong and the user wants to name it.
• "Was there a specific moment when things went wrong?" - Useful for diagnosing onboarding failures or support issues.

For users in the 0-3 range, use an open, direct question. They want to describe what happened and will write more than you expect. For users in the 4-6 range, a gap-focused question ('what would need to change?') is more useful because they partially like the product and the issue is narrower.

What to do with Detractor follow-up answers

Group by score first: read 0-3 answers separately from 4-6 answers. Users in the 0-3 range represent your highest churn risk and often have a single acute problem. Users in the 4-6 range have a gap, not a catastrophe. Look for the same word or phrase appearing in 3 or more responses in the same score band. That is your pattern. Route each answer to the team responsible for the named problem.

NPS Follow-Up Questions for Passives (7-8)

Passives are your most valuable segment for product improvement. They liked your product enough not to call it bad, but they did not love it. Something is missing or slightly off. The gap between a Passive and a Promoter is usually one specific thing, and the right question surfaces it.

Follow-up questions that work for Passives:

• "What would need to change to make this a 9 or 10?" - The most reliable Passive question. Direct and gap-focused.
• "What is the one thing that would make you love [Product]?" - Useful when you want a single concrete answer.

• "Is there a specific feature you wish we had?" - Good for surfacing roadmap gaps.
• "What almost stopped you from recommending us?" - Surfaces the hesitation point, not just the missing feature.
• "What do you use alongside [Product] that you wish was built in?" - Powerful for finding integration gaps and adjacent use cases.

What to do with Passive answers

Passive follow-up answers are your product roadmap. Aggregate the answers and look for themes. The most common gap mentioned by Passives is usually the feature with the highest impact-to-effort ratio for improving your NPS. When the same answer appears repeatedly from Passives on your most important plan tier, that is where to focus first.

NPS Follow-Up Questions for Promoters (9-10)

Promoters already recommended you. The question is what drove that. If you ask them the right question, they tell you which feature, outcome, or workflow made the difference. That is your retention moat and your word-of-mouth message in one answer.

Follow-up questions that work for Promoters:

• "What made you give that score?" - Open and reliable. Works for most Promoter follow-ups as a default.

• "What is the one feature you would be most disappointed to lose?" - Surfaces your core value driver, not a generic positive response.
• "What problem did [Product] solve that you could not solve before?" - Finds your differentiation in the user's own words.
• "How would you describe [Product] to a colleague who had never heard of it?" - Gives you the user's language for your product, often more specific than your marketing copy.
• "Is there anyone specific you would recommend [Product] to?" - Opens a referral conversation without a hard pitch.

What to do with Promoter answers

Promoter answers have two uses. First, find your retention moat: the feature or workflow mentioned most often is the one you cannot weaken or remove without damaging loyalty. Second, find your word-of-mouth message. Promoters describe your product in their own language, which is usually more specific and compelling than what your marketing team wrote. Both are direct inputs into product and positioning decisions.

Conditional NPS Follow-Up Questions (Logic Jumps)

Instead of one generic follow-up question, route each score group to the question that fits their situation:

• Score 0-6 (Detractors): "What went wrong?" or "What would need to change for you to give a higher score?"
• Score 7-8 (Passives): "What would need to change to make this a 9 or 10?"
• Score 9-10 (Promoters): "What made you give that score?" or "What is the one feature you would be most disappointed to lose?"

This is called conditional branching or logic jumps. You configure the follow-up question for each score band once and the survey routes each respondent automatically. Every NPS response arrives with a follow-up answer calibrated to what that respondent had to tell you. No bloated survey, no generic open field, no wasted question for a group that cannot answer it meaningfully.

How Many NPS Questions Should You Ask?

Two is the right number for most NPS surveys: the 0-10 scoring question and one targeted follow-up.

Adding a third question is only justified when:

• The third question is conditional (shown only to a specific score group, not all respondents).
• You need a specific structured data point you cannot get from user attributes (use case, industry, team size).
• Your respondents are highly engaged users who expect a longer survey (power users, early adopters, high-LTV accounts).

Avoid adding a third question just because you have more things you want to know. Completion rates typically drop 20-30% from question 2 to question 3. If you add a third question, make it short-answer or multiple choice, not another open-ended field.

How to Segment NPS Follow-Up Answers

Open-ended follow-up answers are only useful after segmentation. Reading Detractor answers from your free plan and Pro plan together hides the signal in noise. Before analyzing any NPS open-ended responses:

• Separate by score group first: Detractors, Passives, Promoters.
• Within each group, separate by plan tier.
• Within each group, separate by user tenure (under 30 days active vs over 30 days).
• Look for the same word or phrase in 3 or more responses in the same segment. That is your pattern.

If Marc from Berlin on the Pro plan gives you a 3 and writes 'integrations are missing,' that is a different problem than a free plan user writing the same thing. One is a retention risk. The other is an upsell signal. The answers look the same before segmentation and completely different after it.

Start With the Score, Act on the Follow-Up

The NPS scoring question is settled. Use the standard wording, the 0-10 scale, 'friend or colleague,' and your product name. Do not change it. Every change makes your scores harder to benchmark and your trends harder to compare over time.

The follow-up is where you have choices, and those choices determine whether your NPS data is useful or not. A generic 'tell us more' produces generic answers that pile up without driving any action. A targeted question for each score group produces specific answers you can route to the right team and act on the same week.

Set up conditional follow-up questions for each score band. Link every response to the user who submitted it so you know the plan tier, role, and tenure behind each score. Read Detractor, Passive, and Promoter answers as separate groups. The score tells you the ratio. The follow-up tells you the reason. Both together tell you what to do next.