NPS Follow-Up Question: Examples, Best Practices

Net Promoter Score (NPS) is famous for being short. One question. One number. One tidy chart for your next meeting.
And then… reality shows up in your inbox wearing sweatpants: Why did customers choose that number?

That’s where the NPS follow-up question earns its keep. The score tells you what happened.
The follow-up tells you why it happenedand what to do next without resorting to interpretive dance.

In this guide, you’ll get examples, best practices, and a practical way to decide
which follow-up question to ask (and when to keep your curiosity on a leash so response rates don’t sprint away).

What Is an NPS Follow-Up Question?

An NPS follow-up question is the question you ask immediately after the standard 0–10 likelihood-to-recommend rating.
It’s usually open-ended, designed to capture context in the customer’s own words.

The classic follow-up is simple and blunt (in a good way): “What is the primary reason for your score?”
That one line is widely used because it reliably reveals the drivers behind promoters, passives, and detractors.

Why the follow-up matters more than the score (yes, really)

• It turns a number into a plan: A score without a reason is a weather report with no forecast.
• It reduces guesswork: Teams stop debating what customers “probably meant.” Customers tell you.
• It creates a feedback loop: Great NPS programs don’t just measurethey respond, fix, and follow through.

The “Golden Rule” of NPS Follow-Ups: Keep It Short

Most teams get better data when they ask one strong follow-up, occasionally two. More questions can feel like
a “quick question” that turns into a 40-minute meeting invite.

A simple structure that works

1. Rating question: 0–10 likelihood to recommend
2. Follow-up question: “What is the primary reason for your score?”
3. Optional: One targeted question if you need a specific data point (category, feature, channel, etc.)

If you only remember one thing: Ask for the reason first. “Why?” is the gateway to actionable feedback.

Best Practices for Writing Follow-Up Questions That Get Useful Answers

1) Make the question answerable in one breath

The best follow-ups feel easy. If the customer needs to “think back to Q3 of last year’s implementation timeline,”
you’ll get either silence or a rage haiku.

Good: “What’s the main reason for your score?”

Less good: “Please describe all factors that influenced your sentiment across product, support, and billing.”

2) Avoid “10-shaming”

Questions like “Why didn’t you give us a 10?” can sound defensive, even when you mean well.
They also bias responses toward nitpicks and guilt.

Try instead: “What could we do to make your experience better?”

3) Don’t ask two questions wearing one trench coat

“What did you like and what should we improve and would you recommend us to your friends and how did you hear about us?”
is not a follow-up question. It’s a hostage situation.

Keep it single-purpose: one prompt, one answer.

4) Match the follow-up to your goal

• Diagnose drivers: ask for the reason behind the score.
• Find improvement ideas: ask what would make the experience better.
• Validate product direction: ask which feature mattered most.
• Trigger outreach: ask if you may follow up (especially for detractors).

5) Keep your tone human (and on-brand)

You can keep the meaning while adjusting the voice:

• “What’s the primary reason for your score?” (classic, neutral)
• “Quick one: what drove that score today?” (friendly, casual)
• “What stood out mostgood or bad?” (invites specifics)

Segmented NPS Follow-Up Questions for Promoters, Passives, and Detractors

Many teams segment follow-ups by score band because the job-to-be-done differs:
promoters (9–10) tell you what to double down on, passives (7–8) reveal “good but not great” friction, and detractors (0–6)
spotlight urgent fixes and save-worthy relationships.

For Promoters (9–10): learn what to amplify

• “What do you like most about your experience with us?”
• “What’s the main reason you’d recommend us?”
• “Which feature or benefit matters most to you?”
• “What would you tell a friend about us in one sentence?”
• “Would you be open to sharing a short review or testimonial?” (optional, keep it separate)

For Passives (7–8): find the one thing holding you back

• “What’s the one thing we could change to make your experience better?”
• “What kept you from choosing a higher score?” (gentle, not accusatory)
• “What almost made this a 9 or 10?”
• “Which area needs the most improvement: product, support, onboarding, or pricing?” (optional multiple choice)

For Detractors (0–6): identify root cause and invite recovery

• “What’s the primary reason for your score?”
• “What went wrongor didn’t meet expectations?”
• “What could we do to improve your experience?”
• “If you’re open to it, may we contact you to learn more and help?” (permission-based outreach)
• “What would ‘fixed’ look like to you?” (gets concrete success criteria)

High-Performing Follow-Up Question Examples (Copy, Paste, Improve)

Below are follow-up questions you can rotate depending on what you need to learn. The best move is to pick
one primary follow-up and use others in targeted surveys (by touchpoint, lifecycle stage, or segment).

General-purpose (works for almost any NPS survey)

• “What is the primary reason for your score?”
• “What’s the main reason you chose that rating?”
• “What could we do to improve your experience?”
• “What’s one thing we should keep doing?”
• “What’s one thing we should stop doing?”

Product-focused follow-ups (feature, usability, reliability)

• “Which feature influenced your score the most?”
• “What’s been the biggest friction point for you lately?”
• “If you could change one thing in the product, what would it be?”
• “What nearly made you give a higher score?”

Customer support follow-ups (speed, empathy, resolution)

• “Did we solve your issue today? What made you feel that way?”
• “What stood out about your support experiencegood or bad?”
• “What could we do to make support feel easier next time?”

Onboarding and implementation follow-ups (time-to-value)

• “How quickly did you get value from our product?” (optional scaled question)
• “What part of onboarding felt confusing or slow?”
• “What resource would have helped you most?”

Pricing and value follow-ups (ROI, packaging, expectations)

• “How well does the value match the price?” (optional scaled question)
• “What would make the product feel more worth it?”
• “Was anything missing that you expected at this price?”

B2B relationship follow-ups (account management, trust, outcomes)

• “What outcome matters most to youand how well are we delivering on it?”
• “What should we do in the next 30 days to improve your experience?”
• “Where are we making your job easier? Where are we making it harder?”

When to Ask NPS Follow-Ups (Timing and Channel Tips)

Pick a moment when the customer actually remembers the experience

NPS works best when it’s tied to a meaningful touchpoint: after onboarding, after a resolved support ticket,
after a renewal conversation, or after a milestone.

Match the channel to the customer’s context

• Email: best for relationship NPS, longer comments, B2B stakeholders.
• In-app: best for product NPS close to the experience (fast, high-intent responses).
• SMS: best when brevity is a feature, not a limitation (keep follow-up ultra-short).

Don’t forget the “thank you” page (and a little dignity)

Confirm you received feedback and set expectations: “Thanksour team reads every response.” Then actually do that.
The fastest way to make customers stop answering is to make them feel like they’re yelling into a canyon.

How to Turn Open-Ended Follow-Ups Into Action

1) Tag responses into themes (and make the themes usable)

Common buckets include: product quality, bugs, performance, support speed, support quality, billing, onboarding,
value for money, features, and communication. Start simple; expand once you see patterns.

2) Separate “loud” feedback from “common” feedback

One furious comment can feel like a crisis. Ten similar comments is a trend. Track frequency and severity.
Your roadmap deserves both empathy and math.

3) Close the loop (especially with detractors)

If someone took time to explain a low score, consider a follow-up that’s timely, personal, and focused on resolution.
Even when you can’t fix everything, a thoughtful response often reduces churn risk and rebuilds trust.

4) Use promoter feedback to sharpen your positioning

Promoter comments often contain your best messaging: the benefit customers actually feel, in words customers actually use.
That’s marketing gold. Also cheaper than a branding workshop with twelve sticky-note walls.

Common Mistakes (a.k.a. How to Accidentally Waste Everyone’s Time)

• Asking too many follow-ups: You don’t need a novel; you need a clue.
• Leading questions: “Was our amazing support the reason?” invites polite fiction.
• Vague prompts: “Any thoughts?” gets “No.” (which is technically a thought).
• No operational plan: If nobody owns the feedback, it becomes corporate wallpaper.
• Ignoring responses: Customers notice. They always notice.

A Simple Decision Framework: Which Follow-Up Should You Use?

Use this quick chooser:

If you want to understand drivers

Ask: “What is the primary reason for your score?”

If you want improvement ideas

Ask: “What’s one thing we could change to improve your experience?”

If you want to prioritize product work

Ask: “Which feature or part of the product most influenced your score?”

If you want to recover detractors

Ask: “What could we do to make this right?” + “May we contact you to help?”

If you want social proof

Ask promoters: “What would you tell a friend about us?”

Extra Field Notes: of Real-World “This Is What Actually Happens” Experience

Here’s what teams often discover once they start running NPS follow-ups consistently (and reading them like they matter).
Consider this a set of “been-there” patterns you can steal.

1) The best follow-up answers are specific because the question nudges specificity

When teams ask, “What’s the primary reason for your score?” they get a mix of poetry (“Love it!”) and pain (“Billing is chaos”).
The fastest improvement usually comes from a tiny tweak: add a gentle prompt such as
“What stood out most?” or “What influenced your rating today?” That small hint often turns “It’s fine” into
“Setup took 45 minutes longer than promised and I couldn’t find the export button.” Now you can actually do something.

2) Passives are your hidden roadmap, not your “meh” pile

Teams tend to obsess over detractors (understandably) and celebrate promoters (also understandablecake helps).
But passives frequently hold the most actionable “almost great” insight. A follow-up like
“What’s one thing that would make this a 9 or 10?” is magic because it forces prioritization.
You’ll hear themes like “faster support response,” “more predictable pricing,” or “better reporting.”
Passives are basically saying, “I’m willing to love you. Please don’t make me regret it.”

3) Detractors don’t just want fixesthey want to be heard

A classic pattern: a detractor explains the issue, then adds a line that’s not about the issue at all:
“No one responded,” “I had to repeat myself,” “I felt brushed off.” That’s a cue that your follow-up program
isn’t complete without a closing-the-loop motion.
Even a short, respectful message“Thanks for sharing; here’s what we’re doing next”can change the emotional temperature.
The follow-up question that helps most here is permission-based:
“If you’re open to it, may we contact you to help?”
It turns rage into a conversation (not always, but often enough to matter).

4) Promoter comments secretly power your marketing and training

Ask promoters, “What would you tell a friend about us?” and you’ll get lines that outperform your homepage copy:
“It saves me an hour a day,” “Support actually solves things,” “We finally stopped babysitting spreadsheets.”
Smart teams feed these verbatims into sales enablement, onboarding messaging, and even support training:
“Here’s what customers lovelet’s protect it.”

5) The biggest failure mode is collecting feedback with no owner

The fastest way to break NPS is to treat it as a dashboard decoration. The moment feedback becomes a shared inbox nobody checks,
customers can sense it. Internally, teams stop trusting the program because “we’re hearing the same thing every month.”
A simple operating rhythm fixes this: weekly theme review, one owner per theme, one visible change communicated back to customers.
The follow-up question gives you truth; operations make it useful.

Conclusion

The best NPS follow-up question isn’t the cleverestit’s the one that reliably produces clear, actionable reasons.
Start with the classic “primary reason” follow-up, keep it short, and segment only when you have a plan to act on what you learn.
Then do the part most surveys skip: respond, fix, and close the loop.

If you do this well, NPS stops being “a number we report” and becomes “a conversation we improve.” Your customers will notice.
Your team will notice. And your dashboard will finally mean something besides “we are… somewhat… a seven.”