This Net Promoter Score (NPS) Survey Template helps customer experience, support, and product leaders run a repeatable recommend measure that still drives action: stable wording, clean sampling, and workflows that treat promoters, passives, and detractors differently.
Use it when you need a board-level trend line that is honest about what it can and cannot explain—not as a substitute for journey measurement, but as a simple pulse on advocacy intent.
Minimal NPS components that keep trend integrity
- Core item: 0 to 10 likelihood to recommend with consistent referent (brand, product line, or store—pick one).
- Driver or reason: short open text or structured tags explaining the score.
- Optional context block: product area, channel, or journey step—only fields you will analyze and that do not fatally lengthen mobile completion.
- Consent and privacy: how feedback may be used for follow-up contact when someone wants a call.
Use skip logic to tailor the why prompt by band: promoters see referral ask, detractors see service recovery contact preference, passives see improvement checklists.
Sampling cadence for relational and transactional NPS
- Transactional: embed in email after resolution, in-app after milestone completion, or SMS with a clear link—match channel to how the touchpoint happened.
- Relational: email or in-product modal on a published cadence; avoid blasting dormant accounts who have not experienced a recent product version.
Enable multilingual surveys when your customer base spans languages; translate the recommend stem carefully because literal wording shifts can move scores.
Reporting standards for trustworthy NPS dashboards
- Compute promoters (9 to 10), passives (7 to 8), and detractors (0 to 6) with the standard definition unless counsel approves a variant for your category.
- Always report n, response rate, population definition, and mode (transactional versus relational) beside the headline.
- Segment by tenure, plan, region, and channel before blaming product for a support-driven dip.
- Promoters: polite referral ask, case study opt-in, or community invite—only paths you can staff.
- Passives: targeted education or feature prompts tied to their verbatim themes.
- Detractors: human triage within a published SLA, root-cause tagging for product and ops backlogs.
Use e-mail notifications for low-score routing and website embedding when NPS lives beside help content or account settings.
NPS program mistakes that create false signals
- Changing scale labels or endpoints between waves.
- Surveying immediately after a known outage without annotating the event on charts.
- Incentivizing only promoters to respond—biases the score upward and erodes trust.
- Letting sales teams contest individual customer scores in CRM notes visible to the customer.
- Treating NPS as a commission metric without guardrails against gaming.
How NPS fits with CSAT and CES
NPS captures relationship-level advocacy — not the quality of any single interaction. Pair it with touchpoint metrics so a moving trend line is explainable:
Run NPS on a relationship cadence and let CSAT and CES explain why advocacy is rising or falling.
Resources for operational NPS rollout
Use create survey, numerical scale question guidance for consistent 0 to 10 rendering, free text questions for the why prompt, and connect Responsly to Zapier to sync scores and tags into your CX platform.
Then read implement NPS surveys guide, customer satisfaction index, and closed loop feedback to pair headline advocacy with operational metrics and a follow-up culture that actually closes tickets and narratives.
For workforce listening that resembles NPS mechanics, review employee Net Promoter Score (eNPS) separately so employee anonymity and labor norms are respected.