10 Net Promoter Score (NPS) Questions for 2026

The standard Net Promoter Score (NPS) question—“How likely are you to recommend us?”—gives you a number. But a number alone doesn’t tell you why someone would or wouldn’t recommend you, or what to do next. In 2026, the real value of NPS comes from pairing that core question with targeted follow-ups so promoters become advocates, passives become fans, and detractors get a chance to be saved before they churn. This guide gives you 10 NPS questions you can use in 2026: the baseline metric plus follow-ups for promoters, passives, and detractors, and how to implement them with conditional logic and workflows in your form builder.

For NPS design and best practices, see NPS survey best practices for 2026 and survey and feedback form templates. For actionable customer feedback in the same vein, see actionable insights: 12 customer satisfaction questions for 2026 and form analytics: what metrics actually matter.

Why the core NPS question isn’t enough

The core NPS question gives you a number; conditional logic lets you ask different follow-ups for promoters, passives, and detractors so you get the why and can act.

NPS is the go-to metric for customer loyalty: a 0–10 scale and a single question. But if your score goes up or down and you don’t know why, the number is a blunt instrument. Conditional logic in your survey lets you ask different follow-up questions based on the score: promoters (9–10) can be asked for testimonials or referrals; passives (7–8) can be asked what would make them fans; detractors (0–6) can be asked what went wrong so your team can intervene. That turns NPS questions into a feedback loop that drives action—not just a dashboard number. Use a form builder that supports branching so one NPS survey can serve all three segments without making everyone answer the same long list. Research shows that NPS surveys using segment-specific follow-ups (one personalized question per respondent) can achieve much higher completion rates than long, static forms—so branching isn’t just better for insight; it’s better for response volume too.

The core metric

1. “How likely are you to recommend [Your Product/Company] to a friend or colleague?”
Scale: 0–10. This is the non-negotiable anchor for calculating your NPS (percentage of promoters minus percentage of detractors). Keep it as the first question; then use conditional logic to show the right follow-up block based on the score. No need to ask “Why?” in a single open box for everyone—branch by segment instead.

For promoters (score 9–10)

These respondents are your best advocates. Use NPS questions that surface what you’re doing right and turn sentiment into assets.

2. “What is the main reason for your high score?”
Why it works: Surfaces your killer advantage in the customer’s own words. Use this for messaging and positioning. Keep the field optional so promoters who are in a hurry can skip it without abandoning the survey.

3. “Which specific feature or experience would you be most likely to tell others about?”
Why it works: Identifies the best talking points for referrals and marketing. Tag responses by theme (e.g. “ease of use,” “support,” “price”) for content and sales enablement. This question often reveals the one thing to lead with in ads and sales conversations.

4. “Would you be open to sharing a brief testimonial about your experience?”
Why it works: Converts positive sentiment into social proof. Route “Yes” responses to your team so someone can follow up for a quote or case study. Follow up within a week via the same channel (e.g. email) so the offer feels relevant and easy to act on.

For passives (score 7–8)

Passives are satisfied but not enthusiastic—and vulnerable to competitors. Use NPS follow-up questions to find the gap.

5. “What is one thing we could do to improve your experience?”
Why it works: Gap analysis in one question. Often reveals low-hanging fruit that would move them to promoter.

6. “If you could change one aspect of our product or service today, what would it be?”
Why it works: Passives often give the most practical, actionable suggestions. Use for roadmap and prioritization.

For detractors (score 0–6)

Detractors are at risk of churning or bad-mouthing. NPS questions here should open a rescue path.

7. “We’re sorry to hear that. What was the main reason for your score?”
Why it works: Empathy first, then a clear problem statement. Gives your team something concrete to address. Avoid defensive or leading language; keep the tone supportive so detractors feel heard and are more likely to give usable feedback.

8. “What could we have done differently to meet your expectations?”
Why it works: Shifts from “what happened” to “how to fix it.” Use answers to close the loop and, where possible, win them back. This question often surfaces process or communication gaps that are fixable without a product change.

9. “Is there a specific issue right now that’s preventing you from seeing value in our product?”
Why it works: Flags immediate blockers (e.g. billing, access, a bug). Consider routing this to support or success for fast follow-up—and trigger a webhook or alert so the right person is notified within hours, not days.

The comparison check

10. “How does your experience with [Your Product] compare to other solutions you’ve used?”
Why it works: Competitive pulse—you learn how you stack up in the customer’s mind. Optional; can be asked once per year or in a separate research survey to avoid length.

NPS benchmarks: what’s a good score in 2026?

Net Promoter Score is calculated as % promoters (9–10) minus % detractors (0–6); passives (7–8) are neutral. The result ranges from −100 to +100. Benchmarks vary by industry and business model (B2B vs. B2C). In 2026, a common rule of thumb is: any NPS above 0 is a start, above 20 is favorable, above 50 is excellent, and above 70 is world-class. The global average often sits around +32, but sector medians can differ widely—so the most useful benchmark is your own trend over time and, where possible, segment breakdown (e.g. by product, tenure, or channel). Tracking NPS questions and follow-up themes by segment lets you see whether a drop is broad or concentrated in one cohort, so you can act on the right lever. For customer satisfaction metrics alongside NPS, see actionable insights: 12 customer satisfaction questions.

Response rates and survey length: why conditional logic wins

NPS survey response rates depend on channel and length. Email NPS surveys often see 10–30% response, with 30%+ considered strong; in-app surveys can reach ~25–30% when triggered at a relevant moment; SMS one-question NPS can hit 40–50%. The moment you add multiple open-ended questions for everyone, completion drops. Best practice: keep the primary NPS question plus one segment-specific follow-up per respondent. Conditional logic does exactly that—each person sees only the follow-up that fits their score (promoter, passive, or detractor), so you get the “why” without killing completion. Short, mobile-friendly NPS questions and a clear progress indicator also help. For survey design that maximizes completion, see how to build surveys that get 80%+ response rates.

When and how often to run NPS surveys

Relationship NPS (overall loyalty to your company or product) is often run quarterly so you can trend without fatiguing customers. Transactional NPS (after a purchase, support ticket, or key interaction) can be sent within 24–72 hours of the event for the best recall and relevance. Avoid surveying the same person too often—if you run both relationship and transactional NPS, stagger them so one customer isn’t asked every month. Set a rule (e.g. “No NPS within 90 days of last response”) if your form builder or CRM supports it. Timing also affects response: sending when the experience is fresh and using the same channel (e.g. email after an email support close) tends to improve participation. For churn and retention surveys that complement NPS, see exit surveys for churn and retention.

How to build your NPS flow with conditional logic

A minimal NPS survey with the 10 NPS questions in this guide works like this: (1) Ask the core question—“How likely are you to recommend [X]?”—with a 0–10 scale. (2) Branch on the answer: if 9–10, show promoter follow-ups (e.g. “What is the main reason for your high score?” and “Would you be open to a brief testimonial?”). If 7–8, show passive follow-ups (“What is one thing we could do to improve?”). If 0–6, show detractor follow-ups (“What was the main reason?” and “What could we have done differently?”). (3) Optionally add the comparison question (“How does your experience compare to other solutions?”) at the end for a subset (e.g. once per year) to avoid length. (4) Thank the respondent and, if you promised it, tell them how you’ll use the feedback. In a form builder like AntForms, you set conditional logic (show block if NPS ≥ 9, else if ≥ 7, else show detractor block) so one form serves all segments. For conditional logic in other contexts, see conditional logic forms explained and best form builder with conditional logic.

Closing the loop: follow-up timing and ownership

NPS questions only drive value when someone acts on the answers. Detractors should be routed to your team (e.g. via webhooks to Slack or your CRM) with a 48-hour response SLA where possible—someone should reach out to understand and, if feasible, fix the issue. Promoters who say “Yes” to a testimonial should get a follow-up email or call to collect the quote. Passives don’t need an immediate call, but their “one thing we could do” should be aggregated and fed into product or ops so you can trend themes. Report back to customers when you make changes (“We’ve updated [X] based on your feedback”) so they see that NPS isn’t a black hole. Closing the loop improves retention and can lift future NPS response rates because people learn their voice matters. For feedback loops and churn prevention, see reduce churn with feedback loops.

Pitfalls to avoid in NPS surveys

One-size-fits-all follow-up: Asking everyone the same “Why did you give this score?” is better than nothing, but segment-specific NPS questions (promoter vs. passive vs. detractor) yield more actionable answers and keep the survey short. Survey fatigue: Running NPS too often or sending long surveys depresses response. Stick to the core question plus one conditional follow-up per segment. No action: Collecting scores without routing detractors or following up on testimonials wastes the data. Wire webhooks or integrations so low scores trigger alerts. Wrong timing: Sending NPS weeks after an interaction yields vague or no response; aim for 24–72 hours for transactional NPS. Required long-form: Making the follow-up “Why?” required can increase drop-off; keep it optional or use conditional logic so only the relevant segment sees it. For form analytics to track completion and drop-off, see form analytics: what metrics actually matter.

Summary: 10 NPS questions at a glance

Use conditional logic so each respondent sees only the follow-ups for their segment—keeping the survey short and completion high while still capturing the “why” behind the score.

Example: a minimal NPS flow in practice

Here’s a minimal NPS survey using the 10 NPS questions above. Step 1: “How likely are you to recommend [Company] to a friend or colleague?” (0–10, required). Step 2 (conditional): If 9–10, show: “What is the main reason for your high score?” (open, optional) and “Would you be open to sharing a brief testimonial?” (Yes/No). If 7–8, show: “What is one thing we could do to improve your experience?” (open, optional). If 0–6, show: “What was the main reason for your score?” (open, optional) and “What could we have done differently?” (open, optional). Step 3: Thank-you message and optional “Anything else?” Step 4 (backend): Webhook or integration sends detractor responses to a Slack channel or CRM so the team can follow up within 48 hours. That’s 2–4 questions per respondent depending on score—all answerable in under a minute. You get the NPS number, the “why” by segment, and a clear path to testimonials and rescue. For survey and feedback templates, see survey feedback form templates.

Segmenting NPS by cohort

NPS becomes more actionable when you segment results by who answered and when. Slice by product or plan (e.g. free vs. paid), tenure (new vs. long-term), channel (in-app vs. email), or touchpoint (post-purchase vs. post-support). A drop in NPS in one segment (e.g. users who signed up in the last 30 days) points to a specific fix—onboarding, pricing, or feature fit—instead of a vague “our NPS went down.” Use a form builder that can capture metadata (e.g. user ID, plan, signup date) so you can filter and trend NPS questions and follow-up themes by segment in your analytics or CRM. That way you know whether to invest in product, support, or messaging for the right group. For customer segmentation in marketing and forms, see customer segmentation strategies.

Turning NPS scores into action

NPS questions only pay off when scores trigger action. Use conditional logic so that: (1) Promoters see the testimonial/referral ask and their “why” is stored for marketing—tag responses by theme and route “Yes” to testimonial to your marketing or success team. (2) Passives see the “one thing we could do” question and responses go to product or ops; aggregate themes (e.g. “pricing,” “onboarding,” “feature X”) for roadmap and process improvements. (3) Detractors see the “main reason” and “what could we have done” questions, and webhooks or integrations (e.g. Slack, email, CRM) notify your team so someone can follow up within 48 hours. Define a clear owner for each segment (e.g. success for detractors, marketing for promoter testimonials) and a report-back step when you fix something so customers see that their NPS response led to change. A form builder with branching and unlimited responses (e.g. AntForms) lets you build one NPS survey that adapts to the score and routes data to the right place—no manual sorting. For churn and retention context, see exit surveys for churn and retention and reduce churn with feedback loops.

NPS vs. CSAT: NPS measures overall loyalty (“Would you recommend us?”) and is often tracked quarterly or after key touchpoints. CSAT (Customer Satisfaction Score) measures satisfaction with a specific interaction (e.g. one support ticket, one purchase) and is usually asked right after that event. You can run both: use CSAT for transactional feedback and NPS for relationship loyalty. Pairing the 10 NPS questions here with conditional logic ensures you get both the number and the “why” without over-surveying—each respondent sees only the follow-up that fits their score.

Key takeaway: In 2026, NPS is most valuable when the core 0–10 question is followed by segment-specific NPS questions via conditional logic—so every promoter, passive, and detractor path leads to a clear next step: testimonials, roadmap input, or rescue workflows.

Implementation checklist: Before launching your NPS survey, confirm: (1) The core 0–10 question is first and required. (2) Conditional logic shows only one follow-up block per segment (promoter, passive, detractor). (3) Webhooks or integrations route detractor responses to your team with a 48-hour follow-up goal. (4) Promoter “Yes” to testimonial is routed to marketing or success for follow-up. (5) Thank-you message and optional “Anything else?” close the flow. (6) You’ve set a rule to avoid surveying the same person too often (e.g. no NPS within 90 days). A form builder with unlimited responses and branching makes this possible without custom code.

Try AntForms to build NPS surveys with conditional logic, unlimited responses, and webhooks. Use the 10 NPS questions above, branch by score, and turn loyalty data into testimonials, roadmap input, and rescue workflows. For more, read NPS survey best practices, survey feedback form templates, and how to build surveys that get 80%+ response rates.