NPS follow-up questions that explain the score

Net Promoter Score comes from Fred Reichheld's 2003 Harvard Business Review article "The One Number You Need to Grow". It asks one question, how likely you are to recommend a company to a friend or colleague, on a 0–10 scale. People answering 9–10 are promoters, 7–8 passives and 0–6 detractors. The score is the percentage of promoters minus the percentage of detractors.

The score on its own is a thermometer. It can tell you the relationship got worse this quarter, but not whether the cause was a price rise, a slow support team or a bug. The follow-up question is where that answer lives. The most common version is some form of "What is the primary reason for your score?" It is a reasonable default, but the same wording for all three groups gets you weaker answers than a question tuned to each one.

Detractors already have a complaint in mind. Asking "what let you down" invites the specific incident, which is what you need to fix it and to reply. Asking them "what do you like about us?" wastes their one answer.

Passives are the group most follow-ups miss. They are satisfied enough not to complain and not keen enough to recommend, so "why did you give a 7?" often gets "it's fine". Asking what would move them to a 9 or 10 points them at the gap, which is usually a single missing feature, a price concern or a competitor they are weighing.

Promoters tell you what to protect. Their answers show which parts of the product or service people would miss, and they supply phrases you can use in marketing, with permission. This is also the natural place to ask about referrals or testimonials, but see the caution on review requests below.

One open question per respondent, plus at most one short optional probe. NPS surveys are often sent frequently and to the same customers, so every added question costs answers on this survey and goodwill for the next. If you need ratings of specific areas such as support, pricing or onboarding, run them as a separate survey, or ask them only of a random sample.

Closed "driver" questions ("Which of these influenced your score?" with a list of areas) are faster to analyse, but they only offer the reasons you thought of. A reasonable compromise: run the open question for a few cycles, code the answers into themes, then turn the most common themes into a multiple-choice list with an "Other" box.

Read every answer in the first few cycles; there are rarely so many that you can't. Tag each one with one or two themes (pricing, onboarding, support speed, a specific feature, reliability) and keep the theme list short, ideally under 15. Then count themes within each group, not across the whole survey. A theme that dominates detractor answers tells you something very different from one that dominates promoter answers.

Look at two views every cycle: the share of detractor answers per theme (what to fix), and the share of passive answers per theme (what stands between you and more promoters). Record which themes grew since the last cycle. For the score itself, our NPS calculator at /tools/nps-calculator works from raw counts, and the eNPS calculator does the same for employee surveys.

Bain's Net Promoter System splits follow-up into two loops. The inner loop sends feedback straight to the frontline people and teams who can learn from it, and lets them follow up with customers where the feedback merits it. The outer loop handles fixes no single team can make, such as policy, pricing or product changes, through a transparent process that triages issues and assigns them to the team that can resolve them.

For a small team, that becomes three habits. Reply personally to every detractor who agreed to be contacted, ideally within a few working days and from someone who can actually help. Thank promoters and, if they opted in, ask for a referral or case study. Once a quarter, tell customers which themes you acted on. That is what makes people answer the next survey.

To reply, you need to know who answered. Pass a customer or account ID into the survey link as a hidden field rather than asking people to type their email again, and send responses to wherever your team works: a spreadsheet, a CRM or a chat channel.

Zunoform has a native NPS question type, and the form's summary tab shows the promoter, passive and detractor split. Logic on the NPS answer supports "is less than" and "is greater than", and a rule can require two conditions at once, so the three-path design above is three rules. Answer piping, hidden fields for customer IDs, and delivery to Google Sheets or a Zapier catch hook (where you can filter to detractors) all work on the Free plan.

The NPS question itself needs Pro ($14.99 a month) to publish. You can build and preview it on Free, or use a 0–10 rating question, which supports the same logic, and calculate the score in a spreadsheet. The Free plan caps responses at 500 a month. Zunoform is also a form builder, not a customer-feedback platform: there is no automatic theme tagging, no scheduled sending to your customer list and no built-in detractor alerting. If you need those, a dedicated NPS tool is a better fit.