NPS Survey Templates by Trigger: 12 Ready-to-Run Surveys and the Follow-Up Each One Needs

TL;DR#

Every net promoter score survey uses effectively the same rating question — a 0–10 likelihood-to-recommend prompt that has barely changed since Fred Reichheld published it in Harvard Business Review in December 2003. What differs between one NPS survey template and the next is the trigger that fires it, the delay before it sends, the channel it lands in, and above all the follow-up question. The 12 templates below span five trigger families: relational (3), onboarding and activation (2), support and service (3), commercial moments (3), and product adoption (1). Each specifies the trigger event, exact rating-question wording, follow-up, send delay, channel, and detractor routing rule. The structural limit of every template is that it carries exactly one fixed follow-up, while the right follow-up depends on both the score and the reason behind it.

What Is a Net Promoter Score Survey Template?#

A net promoter score survey template is a reusable specification for one NPS touchpoint: the event that triggers it, the 0–10 rating question, the open-ended follow-up, the send delay, the channel, and the routing rule for each score band. A template that gives you question wording alone is missing the four fields that decide whether anyone answers and whether anything happens afterward.

Six fields make a template operational: trigger (the system event that fires the send), rating question (the 0–10 prompt, with the recommendation object named), follow-up (the open-ended question — the only field that meaningfully varies across triggers), timing (the delay, in hours or days), channel (email, in-app, in-widget, SMS), and routing (what happens to detractors, passives, and promoters).

For scoring mechanics rather than survey design, start with the NPS scale explained from 0 to 10 and how to calculate your NPS score. For the instrument decisions underneath these templates — scale labels, anchor wording, sampling — see the seven net promoter survey design choices that decide whether your score means anything.

Relational NPS Survey Templates#

Relational templates measure overall relationship health on a fixed calendar cadence, independent of any single interaction. Run them quarterly or annually, never both at full volume — transactional vs relational NPS covers the tradeoff.

1. Quarterly Relationship NPS#

• Trigger: Day 90 of tenure, then every 90 days.
• Rating question: "How likely are you to recommend {Company} to a friend or colleague?" (0–10)
• Follow-up: "What's the main reason for your score?"
• Timing: Tuesday–Thursday, 9–11 a.m. local; suppress anyone surveyed in the last 60 days.
• Channel: Email from a named human sender, never a no-reply address.
• If detractor: Account owner makes first contact within 48 hours, per Bain & Company's Net Promoter System.

2. Annual Full-Base NPS Census#

• Trigger: Fixed calendar month each year; every customer with ≥90 days tenure, no sampling.
• Rating question: "How likely are you to recommend {Company} to a friend or colleague?" (0–10)
• Follow-up: "What is the single most important thing we could change in the next year?"
• Timing: One send, one reminder at day 7, field closes at day 14.
• Channel: Email, with an in-app fallback for non-openers on day 7.
• If detractor: Monthly detractor review; escalate accounts above your ARR threshold to the exec sponsor.

3. Account-Level Executive-Sponsor NPS#

• Trigger: 30 days before a scheduled QBR, sent to 3–5 named stakeholders per account — not just the daily admin.
• Rating question: "How likely are you to recommend {Company} to a peer at another company?" (0–10)
• Follow-up: "What would have to be true a year from now for you to score us a 10?"
• Timing: At trigger, one reminder at day 5, closed before the QBR deck is built.
• Channel: Email from the CSM's own address, referencing the QBR by date.
• If detractor: Put the response on the QBR agenda as a named item — the quarterly business review is where customer truth goes to die explains why most reviews bury it.

Onboarding and Activation NPS Survey Templates#

Onboarding templates measure whether the first 30–60 days delivered what the sale promised, which is the window where a bad score is still cheap to fix. Fire them on a completion event, never a calendar date alone.

4. Post-Onboarding-Completion NPS#

• Trigger: Onboarding milestone flips to complete (final training delivered, or first production workflow live).
• Rating question: "Based on your onboarding experience, how likely are you to recommend {Company} to a colleague?" (0–10)
• Follow-up: "What was the hardest part of getting started?"
• Timing: 24 hours after the final onboarding session, while specifics are still recallable.
• Channel: In-app modal on next login, email fallback 48 hours later.
• If detractor: Route to the implementation lead — not the CSM — within 24 hours.

5. Day-30 Activation NPS#

• Trigger: Day 30 after signup, gated on at least one completed core action. Skip never-activated users entirely.
• Rating question: "How likely are you to recommend {Product} to someone with a similar job?" (0–10)
• Follow-up: "What did you expect {Product} to do that it hasn't done yet?"
• Timing: On the day-30 gate check; no resend before day 90.
• Channel: In-app slider, dismissible — in-app feedback widgets and why static forms miss the why covers the limits.
• If detractor: Open an expectation-gap review; this is the earliest reliable churn signal you get.

Support and Service NPS Survey Templates#

Support templates measure a single service interaction, so they need short delays and hard sampling limits. When the question is resolution quality rather than loyalty, CSAT or CES is the better instrument — CSAT vs NPS vs CES covers when each applies.

6. Post-Ticket-Resolution NPS#

• Trigger: Ticket status changes to Resolved; sample 1 in 5 tickets, capped at one per requester per 30 days.
• Rating question: "Based on this support experience, how likely are you to recommend {Company}?" (0–10)
• Follow-up: "What one thing would have made this easier?"
• Timing: 2–24 hours after resolution, never inside the resolution email itself.
• Channel: Email threaded into the existing ticket, so context stays visible.
• If detractor: Auto-reopen the ticket and assign to a team lead, not the original agent.

7. Post-Live-Chat NPS#

• Trigger: Chat session ends with a resolution status; exclude abandoned and transferred sessions.
• Rating question: "How likely are you to recommend {Company} to a friend or colleague?" (0–10)
• Follow-up: "What's the main reason for your score?"
• Timing: Immediately, before the session closes — delay destroys in-widget response rates.
• Channel: In-widget, single screen, no page redirect.
• If detractor: Offer a callback in the same widget turn rather than queueing the response.

8. Post-Escalation NPS#

• Trigger: A Sev-1 incident, formal escalation, or complaint case is closed.
• Rating question: "After how we handled this, how likely are you to recommend {Company} to a peer?" (0–10)
• Follow-up: "Where did our handling fall short, and where did it hold up?"
• Timing: 5–7 days after closure. Sending during the heat measures the incident, not the recovery.
• Channel: Email from the account owner or the exec who ran the escalation.
• If detractor: Book a live conversation within one week — how to close the loop with detractors has the recovery playbook.

Commercial-Moment NPS Survey Templates#

Commercial templates fire around money-moving events, making them the highest-leverage sends in the program. A detractor here arrives with a dated, quantified consequence attached.

9. Post-Purchase NPS#

• Trigger: First order fulfilled, or first transaction completed by a new customer.
• Rating question: "How likely are you to recommend {Company} to a friend or colleague?" (0–10)
• Follow-up: "What almost stopped you from buying?"
• Timing: 3–7 days after delivery — long enough to have used it, short enough to remember buying it.
• Channel: Email, or SMS for consumer transactions with existing opt-in.
• If detractor: Route into the returns workflow before the return window closes, not after.

10. Pre-Renewal NPS#

• Trigger: 90 days before the contract renewal date.
• Rating question: "How likely are you to recommend {Company} to a peer evaluating this category?" (0–10)
• Follow-up: "What would make the renewal decision easy — and what makes it hard right now?"
• Timing: Send at T-90; hard-close at T-75 so the answer can still change the outcome.
• Channel: Email from the CSM, separate from commercial renewal correspondence.
• If detractor: Flag renewal-at-risk and open a save motion. Pair with customer retention metrics that actually predict renewals.

11. Post-Expansion NPS#

• Trigger: 45 days after an upsell, seat expansion, or tier upgrade closes.
• Rating question: "Since your recent upgrade, how likely are you to recommend {Company} to a colleague?" (0–10)
• Follow-up: "Has the upgrade delivered what you expected? What's still missing?"
• Timing: 45 days — the expanded scope is in real use, but the next renewal is still far off.
• Channel: Email from the CSM, naming the specific expansion in the first line.
• If detractor: Escalate as downgrade risk; expansion detractors revert to their prior tier fast.

Product and Feature NPS Survey Templates#

Product templates attach the score to a specific capability rather than the whole relationship, which makes the result usable by a product team instead of a CX dashboard.

12. Post-Feature-Adoption NPS#

• Trigger: User has used a specific feature at least 3 times within 14 days of first use.
• Rating question: "How likely are you to recommend {Feature} to someone doing the same job?" (0–10)
• Follow-up: "What were you trying to accomplish, and where did {Feature} get in the way?"
• Timing: On the third use, in-session — not on a nightly batch.
• Channel: In-app, anchored to the feature surface itself.
• If detractor: Route to the owning product manager with session context attached.

Beta variant: For an early-access cohort, move the trigger to day 14 of the program, change the follow-up to "What would need to be true for you to use this daily?", and skip detractor routing — in a beta, every response goes to the product team regardless of score.

All 12 NPS Survey Templates at a Glance#

The Follow-Up Question Is the Template#

Across all 12 templates the rating question changes almost nothing — only the object being recommended — while the follow-up changes every time. That asymmetry exposes the structural limit of template-based NPS: a static survey carries exactly one follow-up, but the right follow-up depends on the score and the reason behind it.

Take Template 10's fixed follow-up, "What makes the renewal decision hard right now?" Three customers answer it. A promoter writes "nothing hard, we're happy" — the right next question is a referral or case-study ask. A passive writes "it's fine, we just don't use half of it" — the right next question is which half, and why. A detractor writes "the reporting is unusable" — and the right next question depends entirely on whether that means missing fields, slow exports, or the wrong grain of data. The template can ask none of them.

Adding more boxes doesn't fix it. Each extra required field cuts completion, and response rate is already the binding constraint: email NPS commonly lands in the 5–15% range, and general survey response has fallen for two decades — Pew Research Center recorded telephone survey response rates dropping from 36% in 1997 to 6% by 2018. Our own guidance on improving your NPS response rate points the same way: fewer fields, better timing.

The score's explanatory weakness is documented, not a vendor talking point. A 2007 Journal of Marketing study by Timothy Keiningham and colleagues, a longitudinal examination of Net Promoter and firm revenue growth, failed to replicate the claim that NPS predicts growth better than established satisfaction measures, and Nielsen Norman Group makes the parallel usability argument that the number shows sentiment moved but never what to change. Both point at the open text after the score — the exact field a template freezes.

The alternative is adaptive follow-up: an AI interviewer that reads the 0–10 score plus the first open answer, then asks the question that actually fits. A 3 citing price gets a pricing-sensitivity probe; a 3 citing a bug gets reproduction detail and business impact; a 9 gets a referral ask. Everyone answers two to four questions instead of one, and nobody gets a question that doesn't apply. That is what Perspective AI's interviewer agent does at the follow-up step, and the mechanism behind closing the loop on NPS with a conversational approach. For the probe bank itself, see NPS follow-up questions that capture the why behind the score and what to ask after the score in 2026.

How to Choose Which NPS Survey Template to Run#

Choose by the business question your team is arguing about this quarter, not by what your survey tool ships as a default. Running all 12 at once produces overlapping sends, fatigued respondents, and a blended score nobody can act on.

Two rules make the selection stick. Cap total NPS contacts at one per customer per 60 days across all templates, enforced by a global suppression list every trigger checks. And pair every template with a named owner and an SLA — Bain's guidance is to close the loop with detractors within 24 to 48 hours, and a template with no owner is a data-collection exercise, not a program. The Net Promoter System vs the Net Promoter Score covers that organizational half. Before setting a target, calibrate against 2026 NPS benchmarks by industry or, for subscription software, NPS benchmarks for SaaS by segment.

Frequently Asked Questions#

What is the standard NPS survey question?#

The standard NPS question is "How likely are you to recommend {Company} to a friend or colleague?" on a 0–10 scale, with 9–10 counted as promoters, 7–8 as passives, and 0–6 as detractors. Reichheld published this wording in Harvard Business Review in December 2003 and it has stayed essentially unchanged. Swapping a product or team name for the company name is the only variation most programs need — see the definition and formula behind the score.

How often should you send an NPS survey?#

Send relational NPS every 90 days at most, and cap total NPS contacts across all templates at one per customer per 60 days. Transactional templates fire on events rather than a calendar, so the suppression list — not the cadence — protects response rates. Quarterly is the most common relational cadence in B2B SaaS; annual census sends suit large consumer bases where quarterly volume is unmanageable.

Should an NPS survey be sent by email or in-app?#

Send transactional NPS in the channel where the trigger happened and relational NPS by email. In-app prompts reach active users in context and typically beat email on response rate, but they systematically miss disengaged users — exactly the population a renewal or churn signal depends on. Most mature programs run in-app for event triggers and email for relational cadence, with an in-app fallback for email non-openers.

What is a good response rate for an NPS survey?#

Email NPS response rates commonly land between 5% and 15%, while in-app and in-widget prompts run meaningfully higher because they catch users mid-session. Rates below 5% usually signal a timing or sender problem rather than a question problem. Response rate matters more than list size for B2B programs: a 5% response from 400 accounts yields 20 answers, too few to segment reliably.

How many follow-up questions should an NPS survey have?#

A static NPS survey should have exactly one open-ended follow-up, because each additional required field measurably reduces completion. That ceiling is why adaptive follow-up exists — a conversational survey can ask three or four questions and still finish, since each is chosen from the previous answer rather than shown to everyone. One fixed question in a form; three to four adaptive ones in a conversation.

Can you run transactional and relational NPS at the same time?#

Yes, but only with a shared suppression list that every trigger checks first. Without one, a customer who files a ticket in week 10 of the quarter can receive a post-ticket survey and a quarterly relational survey days apart, which depresses both response rates and contaminates the relational score with a service moment. Transactional vs relational NPS covers how to keep the reporting lines separate.

Start With One Template, Then Fix the Follow-Up#

Pick the one net promoter score survey template above that answers the question your team is actually arguing about — renewal risk, onboarding quality, or feature investment — and ship it with all six fields filled in, owner and detractor SLA included. A template with a trigger, a delay, a channel, and a routing rule beats a beautifully worded question blasted to everyone on the first of the month.

Then fix the part no template can fix. The rating question is solved; the follow-up is not. To see what happens when the question after the score adapts to the answer, run one of these triggers as an AI interview: start a conversation with Perspective AI, adapt the customer interview template to your trigger, or see how customer success teams use Perspective to turn detractor scores into recovery conversations. For the adjacent moments, the churn interview template and the customer satisfaction survey template are ready to run.