What questions an NPS survey should ask: the 0-to-10 rating and one open-ended why, read on arrival, and why to skip the closed-ended battery.
An NPS survey needs two questions: the standard rating — how likely are you to recommend us to a friend or colleague, on a scale of 0 to 10 — and an open-ended follow-up asking the reason for that score. The rating produces the metric; the open-ended why produces everything you can act on. A third, optional question can ask what one change would raise the score. Beyond those, more questions usually cost you responses without adding signal.
The mistakes are predictable: rewording the rating question so it is no longer comparable to prior waves, dropping the open-ended why to boost completion, or bolting on a ten-question satisfaction battery that turns a thirty-second pulse into a chore. Each of these trades away the thing that makes NPS worth running — a clean, comparable score with a readable reason attached.
Key takeaways
The rating question gets all the attention, but it is the open-ended follow-up that converts NPS from a vanity metric into an instrument. “What is the main reason for your score?” is where the customer hands you the driver — unprompted, in their own words, ranked implicitly by what they chose to mention first. Drop that question and you are left with a number and no way to move it. Keep it, and every response carries its own explanation.
The reason teams drop it is that the answers pile up unread. A form-centric tool stores the comment as loose text with no way to read it against a codebook or keep it on the respondent. Sopact calls the alternative the Verbatim Thread: the open-ended answer read against your codebook on arrival, themed and cited, and kept on the same persistent record as the rating. The follow-up question becomes ranked drivers by default, so there is no reason to cut it, the model behind Sopact’s feedback tools.
NPS questionnaires moved through three eras. First, the rating plus a why, with the why skimmed by hand. Then the dashboard era, where tools kept the two questions but reduced the why to a word cloud, which quietly devalued it and tempted teams to add closed-ended driver questions instead. The current era keeps the open-ended why and reads it into themes on arrival, so the single follow-up outperforms a whole battery of closed questions.
The one test that separates the eras: ask whether your survey can turn one open-ended why into ranked, cited drivers automatically — because if it cannot, teams compensate by adding closed-ended questions that lengthen the survey and lower response rates. A readable open-ended answer replaces five closed ones. If the why is unreadable, the questionnaire bloats to make up for it.
NPS derives its value from comparability, and comparability is fragile. Changing “recommend to a friend” to “recommend to a colleague,” shifting the scale labels, or moving the question’s position in the survey can all move the score independent of any experience change. A reworded question makes this wave incomparable to the last, which quietly invalidates the trend line teams rely on to make decisions.
The discipline is to lock the rating wording, the scale, and the follow-up phrasing in a shared definition and change them only deliberately, with a documented break. Fixing the wording and validating responses at the source is what keeps wave two comparable to wave one, the same foundation honest benchmarking and sound measurement both require.
Add at most one: what single change would most improve your score. Skip closed-ended driver checklists — they impose your categories on the customer, whereas the open-ended why lets the customer name a driver you never thought to list. A checklist can only find problems you already suspected; an open-ended answer, read well, finds the ones you did not. The exception is a required attribute for segmentation, like role or plan, which should come from your records rather than the survey where possible.
The output of a lean, two- or three-question NPS is a fast survey with a rich read: high completion, a comparable score, and ranked drivers in the customers’ own words. Because Sopact reads the open-ended answer on arrival and keeps it on the Verbatim Thread, one why-question does the work a battery of closed questions cannot, and the survey stays short enough that people finish it — the question-design side of NPS verbatim analysis.
One well-read open-ended question outperforms a battery of closed driver questions: it finds the reasons you did not anticipate and keeps the survey short. The catch is that the open-ended answer must actually be read.
| The question | Closed driver battery | One open-ended why (read) |
|---|---|---|
| What can it find? | Only the drivers you pre-listed | Drivers the customer names, including new ones |
| Effect on completion? | Lowers it: more questions, more drop-off | Minimal: one short question |
| Whose categories win? | Yours, imposed on the customer | The customer’s, in their own words |
| Is it actionable? | Only if your list was right | Yes, once themed and ranked on arrival |
Reading that one answer well is the work of NPS verbatim analysis; the impact-oriented version of question design is impact survey questions.
An NPS number is a lagging summary; the reason a customer gave it is in the comment, and only if someone reads the comment while it still matters. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment a response arrives, improve while there is still time to act. On a feedback program that means a detractor’s reason is themed the day it lands and routed to someone who can close the loop, not filed for a quarterly readout.
The Loop is also what makes an NPS finding defensible: every driver and theme traces to the exact comment it came from, the standard detailed in Loop traceability, so “price is the top detractor driver” is backed by the sentences, not a hunch.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
The fastest way to improve your questions is to see what one open-ended why yields versus your current battery. Export a set of responses, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended survey responses
Here are our NPS comments with each respondent's score: [ATTACH]. Theme every comment against our codebook, cite the sentence behind each theme, and show the top five themes among detractors, passives, and promoters separately.
Academy walkthrough → Analyze sentiment and its drivers
For these NPS verbatims: [ATTACH], score sentiment per comment, then show the specific drivers behind the detractor comments — the recurring reasons, each with a quoted example — so I know what to fix, not just the score.
Academy walkthrough → Connect quant and qual data
Here are our NPS scores and open-ended comments on the same respondent IDs: [ATTACH]. Show which themes explain the detractor scores, quote a comment for each, and list the specific respondents worth a personal follow-up.
Academy walkthrough → Analyze NPS across waves
Here are two waves of NPS from the same respondents on the same IDs: [ATTACH]. Track each respondent's movement between waves, show who moved from detractor to promoter and who slipped, and surface the comments that explain the biggest moves.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading feedback on arrival and tying every comment to the person who gave it.
The standard 0-to-10 recommend rating and an open-ended follow-up asking the reason for the score, plus at most one optional question on what change would raise it. The rating is the metric; the open-ended why is what you act on. Sopact reads that why on the Verbatim Thread, so the follow-up becomes ranked drivers rather than archived text.
How likely are you to recommend us to a friend or colleague, on a scale of 0 to 10. Keeping this wording and scale fixed across waves is what preserves comparability. Sopact locks the wording and validates responses at the source so the trend stays honest.
Yes — it is the question that earns its keep. The open-ended why hands you the driver in the customer’s own words, unprompted. Teams drop it only because the answers pile up unread; Sopact reads each one on arrival, so keeping it costs nothing and adds everything.
Two, or at most three. The rating, the open-ended why, and optionally one question on what to change. More questions lower completion and dilute the fast pulse that makes NPS useful. Sopact makes the single open-ended why do the work a longer battery would, so the survey stays short.
No, when the open-ended answer is actually read. A closed battery can only find drivers you pre-listed and imposes your categories on the customer, while a read open-ended answer finds reasons you did not anticipate. Sopact themes the open-ended answer on arrival, so one question beats the battery.
Only deliberately, with a documented break in the trend, because rewording the rating or scale can move the score independent of any experience change and make waves incomparable. Sopact keeps the wording fixed in a shared definition so the comparison stays valid.
From your records where possible — role, plan, tenure — rather than adding survey questions, which lengthen it and lower completion. Sopact keeps respondents on a persistent record, so segmentation attributes attach automatically without burdening the survey.
Next: read the answers in NPS verbatim analysis, or set up the whole survey in measure NPS.
