Discover · Satisfaction

An NPS survey that asks why

A lone 0-10 score tells you that something's wrong, never what. This template branches on the score, so detractors, passives, and promoters each answer the follow-up that actually matters, in under a minute.

Discover BusinessesProduct teamsCommunities NPS questionSkip logicChained calculated fieldsTestimonial capture
What it showcases

Features most survey bots don't have

🔀

Three paths, one number

Detractors (0-6) tell you what broke. Passives (7-8) tell you the one thing that would win them over. Promoters (9-10) tell you what they love, and whether you can quote them.

Turn fans into testimonials

Promoters get a consent question, so your happiest users become marketing assets you're cleared to use, captured in the same flow as the score.

🧮

A tailored closing line

Chained calculated fields read the score and give each respondent a tier-appropriate sign-off automatically: encouraging for fans, empathetic for detractors.

🔟

The standard question, natively

The 0-to-10 ask is Subo's built-in NPS question: eleven tap targets with 'Not at all likely' and 'Extremely likely' anchors, translated for every respondent. Nobody types 11 or 'seven'.

🌐

Discord and web

Run your recurring pulse where your audience already is; export the score column for the headline NPS.

Worked example This template comes with a any product or community running a satisfaction pulse example so you can see exactly how it plays. Edit the questions and content to make it your own.

Most NPS surveys stop at the number, which is where they go wrong. A 3 and a 9 both mean something, but the score never says what. This template asks the standard 0-10 recommend question, using Subo’s native NPS question so respondents tap a point instead of typing a number, then branches on the answer so each respondent goes down the path that fits their score.

Detractors tell you what let them down. Passives tell you the one thing that would move them to a 10. Promoters tell you what they love, and get a consent question that turns them into a testimonial you’re cleared to use. Same thirty seconds, three targeted conversations, and a headline NPS you compute from the exported scores.

A close that fits the score

Two chained calculated fields read the 0-10 answer and generate a tier-appropriate closing line, warm for fans and empathetic for detractors, with no extra blocks to manage. It’s a small touch that makes the survey feel human, and a live demo of calculated fields feeding each other, something almost nobody knows Subo can do.

Variants

  • CSAT or CES: reword the number question and adjust the bands.
  • Route detractors to support: open a ticket or ping a channel on the detractor branch.
  • Reward reviewers: grant a “Featured Reviewer” badge to promoters who consent.
  • Anonymous pulse: drop personalization for candor, at the cost of follow-up.
How to run it

Live in a few minutes

  1. 1

    Swap in your product

    Replace the [Product] placeholder once, and the question, branches, and close all update.

  2. 2

    Keep the score bands

    0-6 detractor, 7-8 passive, 9-10 promoter are the NPS standard. The branches are wired to them; leave them or adjust.

  3. 3

    Run it as a pulse

    Send it monthly, quarterly, or after a big release. Thirty seconds per respondent.

  4. 4

    Act on the segments

    Fix what detractors flag, win over passives, and publish the testimonials promoters cleared. Compute the headline NPS from the exported scores.

FAQ

Common questions

What is NPS?

Net Promoter Score asks how likely you are to recommend a product on a 0-10 scale. The headline number is the percentage of promoters (9-10) minus the percentage of detractors (0-6), calculated across all respondents.

How do respondents answer the 0-to-10 question?

It's a native NPS question, so they tap one of eleven points instead of typing a number, with translated 'Not at all likely' and 'Extremely likely' anchors at the ends. The answer is stored as a number, which means you get an average and a 0-to-10 distribution in the report and a clean numeric column in every export. Subo does not roll the responses up into a promoter-minus-detractor headline; you compute that from the exported scores.

Why add follow-up questions?

The number alone isn't actionable. Branching on the score means detractors tell you what to fix, passives tell you what would win them over, and promoters tell you what to market. That's the actionable half of NPS.

How does it capture testimonials?

Promoters get a short consent question after describing what they love, so you leave with quotable praise you're cleared to publish.

Can I use it for CSAT or CES instead?

You can reword the number question and adjust the bands, and the same branch-and-follow-up structure works. There are also purpose-built versions: the CSAT template for satisfaction and the CES template for effort, each using the instrument's own scale.

Use this template

Clone it into your community, swap in your content, and share it. No building from scratch.