{"id":252868,"date":"2026-07-23T14:01:16","date_gmt":"2026-07-23T14:01:16","guid":{"rendered":"https:\/\/userpilot.com\/blog\/userpilot-nps\/"},"modified":"2026-07-24T02:51:14","modified_gmt":"2026-07-24T02:51:14","slug":"userpilot-nps","status":"publish","type":"post","link":"https:\/\/userpilot.com\/blog\/userpilot-nps\/","title":{"rendered":"Userpilot NPS Feature: Use Cases, and Best Practices"},"content":{"rendered":"

Most NPS surveys end the moment someone clicks Submit. A score appears in the dashboard, the monthly report gets updated, and the responses slowly disappear into a spreadsheet. I’ve seen teams spend more time discussing whether their NPS moved three points than reading the comments customers took the time to write.<\/p>\n

That’s a missed opportunity. A score doesn’t explain why customers feel the way they do, which users are running into the same problem, or whether the issue comes from onboarding, missing functionality, support, or something else entirely. Those answers come from the feedback itself and the product experience<\/a> behind it.<\/p>\n

Userpilot brings those pieces together. You can build and target NPS surveys,<\/a> review responses alongside product behavior, and follow up while the feedback is still fresh. The rest of this article follows that process from the first survey to the next product change.
\n
\n\"demo<\/a><\/p>\n

What an NPS score tells you (and what it doesn’t)<\/strong><\/h2>\n

Start with what the number measures. NPS<\/a> measures customer loyalty and likelihood to recommend your product. It is a lagging signal rather than a leading KPI, and it should not be treated as a customer satisfaction metric.<\/p>\n

The math is simple to calculate<\/a>. You subtract the percentage of detractors from the percentage of promoters and multiply by 100, which puts every result on a scale from -100 to +100. Promoters rate you 9 or 10, passives sit at 7 or 8, and detractors land anywhere from 0 to 6.<\/p>\n

Here is the problem a bare score cannot solve: it never tells you why anyone picked their number. On its own, that makes NPS a vanity metric. It turns into something you can act on the moment you pair it with a qualitative follow-up<\/a> and the behavioral data behind the response.<\/p>\n

I treat NPS as a symptom to investigate. And before you can analyze feedback, you have to collect feedback worth analyzing, which starts with asking the right users the right question at the right time.<\/p>\n

\"NPS-loop\"
NPS feedback loop: collect, analyze, act, and repeat to turn customer feedback into product improvements.<\/figcaption><\/figure>\n

Collect: Build, target, and time the survey<\/strong><\/h2>\n

This is the longest part of the workflow, because data quality is decided here and not in analysis. Get the collection wrong, and no amount of clever tagging will save the responses.<\/p>\n

Build the survey<\/strong><\/h3>\n

You start in Userpilot under Feedback > NPS > Create NPS<\/a>. The default question follows the industry standard, \u201cHow likely is it that you would recommend [Company] to a friend or colleague?\u201d, and you can personalize it with dynamic variables like the user’s name or company.<\/p>\n

\"create-NPS\"
Create NPS.<\/figcaption><\/figure>\n

The setting that matters most for a workflow, and the one older guides skip, is the follow-up question. You can make it Universal, a single question regardless of score, or Score-Based, a different question for detractors, passives, and promoters. I keep the follow-up open-ended, because that free text is the qualitative material the rest of the loop runs on.<\/p>\n

\"Follow-up-questions-in-Userpilot\"
Follow up question.<\/figcaption><\/figure>\n

You can also set a custom thank-you message, made score-based if you want detractors and promoters to hear something different. Styling covers colors, logo, fonts, border, and a progress bar, which is worth a minute of attention and not much more.<\/p>\n

<\/p>\n

Target the right audience<\/strong><\/h3>\n

Targeting lives in the Settings tab. You pick the Platform first, either web app or mobile app, and running NPS on mobile is newer than most write-ups acknowledge. Then you set the Environment to production or staging, so you can test safely before anything reaches a real user.<\/p>\n

\"Target
Target the right audience.<\/figcaption><\/figure>\n

From there, you narrow by domain and page, then choose an audience: Only Me (for testing), a Saved Segment, or Custom Conditions based on user attributes, company data, or product usage. Who you ask decides whether the data means anything. A user who signed up yesterday produces noise, not signal.<\/p>\n

Time it so the answer is real<\/strong><\/h3>\n

Two controls decide when a user sees the survey. Behavioral triggers fire on the number of page visits or time spent on a page, and the sampling rate sets how many eligible users get asked on a given day. Timing is the difference between signal and noise.<\/p>\n

\"Time-your-NPS-survey-right\"
Time your NPS survey right.<\/figcaption><\/figure>\n

Userpilot’s own documented NPS recommendations<\/a> make this concrete: trigger the survey for users who signed up 30 to 90 days ago, use roughly a 10% sampling rate, re-show the survey 60 to 90 days after a completed response, and wait 3 to 7 days after someone clicks “Ask me later.” Those recommendations help you collect consistent feedback without overwhelming users.<\/p>\n

The failure mode is easy to picture. You get asked to rate a product you have used for twenty minutes, and your answer measures your mood rather than the product. That is exactly the response you do not want in your data set.<\/p>\n

I have come to treat every one of these settings as an experiment rather than a fixed answer. Every suggestion you gather, whether from feedback, from AI, or from a teammate, is a hypothesis you try out, and the product is all about experiments. So I set a trigger and a sampling rate as my best guess about who is ready to answer, then adjust both as the responses come back.<\/p>\n

As a small aside, NPS surveys support localization through a locale_code property following the ISO 639-1 standard, or the user’s browser language when no locale is passed. If you run in more than one market, it is worth setting once and forgetting.<\/p>\n

Analyze: turn responses into themes and root causes<\/strong><\/h2>\n

Read the dashboard<\/strong><\/h3>\n

Responses land on the NPS page<\/a> with the metrics that carry weight: Total Shown, Total Responses, Response Rate, and Qualitative Responses.<\/p>\n

One metric worth paying attention to is the response rate. While it varies by product and audience, many customer feedback benchmarks consider 20%<\/a> or higher a healthy response rate for NPS surveys. If your response rate is consistently lower, it’s often a sign to revisit your survey timing, targeting, or frequency before drawing conclusions from the score.<\/p>\n

\"Filter-responses\"
Filter responses to analyze trends<\/figcaption><\/figure>\n

An NPS History Chart tracks the score over time, so you can hold the period before a product change against the period after it.<\/p>\n

\"NPS
NPS History Chart.<\/figcaption><\/figure>\n

You can filter all of it by Segment, Company, Time Period, or Platform. That filtering is what turns one blended number into something you can reason about.<\/p>\n

Tag responses into themes<\/strong><\/h3>\n

Open the Responses tab and add tags to the qualitative answers, which lets you cluster free text into buckets like pricing or bugs. You create a new tag right there with the + Add a tag option, then apply it as you read through responses.<\/p>\n

\"Tag
Tag responses into themes.<\/figcaption><\/figure>\n

Each tag carries its own score breakdown, with promoters in green, passives in grey, and detractors in red. You can see at a glance which themes are dragging the score down and which ones your promoters keep bringing up.<\/p>\n

Segment to find where detractors concentrate<\/strong><\/h3>\n

Filter responses by persona, company, or platform to find the group your detractors<\/a> cluster in. A theme that looks minor across everyone can be severe inside one segment, and that narrow segment is the one to act on.<\/p>\n

You can also open individual account profiles, so a large account sitting on a low score gets routed to customer success before it quietly churns<\/a>. That single move has protected more renewals than any blended score average ever will.<\/p>\n

Root-cause with behavioral data<\/strong><\/h3>\n

This is where Userpilot stops being a survey tool. You pair each NPS response with product analytics, so the score arrives with the behavior behind it rather than as a standalone rating.<\/p>\n

Autocapture lets you analyze a respondent’s historical behavior without instrumenting events in advance. Session Replay lets you sit and watch how promoters and detractors actually move through the product, and Path Analysis<\/a> shows the journeys people take right before they submit an NPS response.<\/p>\n

\"session-replay-powered-analytics-userpilot\"
Session replay feeding Userpilot product analytics.<\/figcaption><\/figure>\n

James Mitchinson, Userpilot’s Head of Customer Success, put the value of this pairing in concrete terms. He described an account that logged in constantly while making no real progress, the kind of split a loyalty score alone would miss:<\/p>\n

\u201cIt was clear progress wasn’t being made, but there were still a lot of logins. Being able to look at the difference between those two things, lots of activity but the outcomes aren’t really materializing, gave us the opportunity to have a more frank conversation with the executive stakeholder about the challenges they were experiencing. We got them back on track before they gave up.\u201d<\/em><\/p>\n

A loyalty signal plus behavioral data caught that risk early. Either one on its own would have missed it entirely.<\/p>\n

Let AI do the synthesis<\/strong><\/h3>\n

Lia, Userpilot’s AI agent<\/a>, sits across NPS responses, surveys, session replays, product behavior, and content engagement, and pulls them into one connected view. You can ask it to summarize user sentiment or analyze a survey without exporting anything or stitching tools together by hand.<\/p>\n

\"Userpilot
Userpilot<\/a> AI agent.<\/figcaption><\/figure>\n

That churn work is the James scenario running on its own, combining NPS responses with behavioral signals to flag at-risk accounts. Automated tagging and sentiment analysis<\/a> of open-text NPS answers is still rolling out, so today Lia is the layer that connects and summarizes, with the full automation arriving rather than already live.<\/p>\n

Act: Close the loop<\/strong><\/h2>\n

Collecting and analyzing NPS is effort. Acting on it is the only part that changes the score next quarter, and it is the step most teams quietly skip.<\/p>\n

Route responses to where the work happens. NPS responses sync to HubSpot, Salesforce, or Webhooks<\/a>, so a detractor drops straight into your existing customer success or support workflow instead of waiting to be noticed in a dashboard.<\/p>\n

Keep the data clean as you go. You can exclude test responses, which pulls them from analytics while keeping them in the response log, switch on Never Show Again for specific users, and export the full set as CSV for deeper analysis or sharing.<\/p>\n

Two workflows show what closing the loop looks like in practice.<\/p>\n