How is this different from a standard NPS tool?

A standard tool records the score and the comment. This template interviews the person behind the score: an AI moderator reads the reason and asks the follow-up you would, so a 6 becomes a specific fixable complaint instead of a data point.

How often should I run it?

Monthly or quarterly works for most teams. Pick a cadence you can hold and keep the two anchor questions identical each cycle so the trend and the themes stay comparable over time.

Will regular users get annoyed by the follow-ups?

You control the follow-up depth budget, so a recurring pulse can be kept short. Skip is always allowed, and the one-response-per-device option keeps the same person from being counted twice in a cycle.

What do the results look like?

The score trend, themes with supporting quotes and counts, full transcripts of every interview, and a plain-language question box for asking things like "what did detractors say almost made them score higher?"

Templates / Product feedback survey

Product · Adaptive interview template

Product feedback survey template

A product feedback survey usually ends where it should begin. You collect a score and a one-line reason, chart the number, and never learn what "it's fine" or "love it" actually points at. The trend line moves and nobody can say which release moved it.

This template keeps the pulse short but makes it talk back. A score and its main reason are the two anchors, then the AI interviewer digs into the specific recent experience behind the number: what almost made them score lower, what almost made them score higher, and the single change that would matter most. Run it on a schedule and the themes accumulate against your release cadence, so a dip in the score comes with the transcripts that explain it.

When to use it

As a recurring monthly or quarterly pulse to the active user base
In-app after a user has spent enough time to have an opinion worth having
Right after a major release, to hear what changed for the people who noticed
Segmented by plan or tenure, so power users and newcomers stay separable

Running it well

Keep the cadence steady. A pulse is only useful as a trend, and a trend needs the same two questions asked the same way each cycle.
The score is the routing signal, not the deliverable. Read the detractor and passive transcripts first; promoters tell you what to protect, the others tell you what to fix.
Set the follow-up depth budget lower for a recurring pulse than for a one-off study. Regulars will not tolerate a long interview every month.
Tag the share link by surface, for example ?ref=in-app versus ?ref=email. The same question gets different answers depending on where you catch someone.

The questions, and why they're shaped this way

These are the anchor questions. You can edit, reorder, or add to them; the AI interviewer handles the depth between them.

NPS 0 to 10

How likely are you to recommend us to a friend or colleague?

The number is the tripwire, not the finding. It sorts respondents into promoters, passives, and detractors so the interviewer knows which conversation to have, but on its own it explains nothing.

Open text

What's the main reason for your score?

Asked immediately while the score is fresh, this is where the reason lives. A 9 and a 6 both start typing here, and the follow-ups pull each toward the specific experience that produced the number.

What the interviewer asks next

Follow-ups aren't scripted. The AI reads each answer and probes what a researcher would. Depending on what a respondent says, it might ask:

"You gave an 8 and mentioned the reporting. What would the reporting need to do for that to be a 10?"

"You said it's been reliable lately. Was there a specific moment recently where it worked exactly the way you needed?"

"You mentioned it feels slower than it used to. Where in your workflow do you notice that most?"

Live demo

Play the product feedback survey interview

This is the real interviewer, not a recording. Answer as yourself and watch the follow-ups adapt to what you write.

Prefer a full window? Open the demo.

Common questions

How is this different from a standard NPS tool?: A standard tool records the score and the comment. This template interviews the person behind the score: an AI moderator reads the reason and asks the follow-up you would, so a 6 becomes a specific fixable complaint instead of a data point.
How often should I run it?: Monthly or quarterly works for most teams. Pick a cadence you can hold and keep the two anchor questions identical each cycle so the trend and the themes stay comparable over time.
Will regular users get annoyed by the follow-ups?: You control the follow-up depth budget, so a recurring pulse can be kept short. Skip is always allowed, and the one-response-per-device option keeps the same person from being counted twice in a cycle.
What do the results look like?: The score trend, themes with supporting quotes and counts, full transcripts of every interview, and a plain-language question box for asking things like "what did detractors say almost made them score higher?"

Related templates

Customers

NPS survey template

The number is the easy part. The follow-up on it is the whole point.

Product

Feature validation template

Check a feature solves a real problem before you commit the roadmap.

Customers

Customer satisfaction survey template

A CSAT score you can act on, because the interviewer asks what moved it.

Run the product feedback survey with your own audience

Join the waitlist