Note: This article is based on current public information about Userpilot’s NPS feature, established Net Promoter Score methodology, and widely accepted SaaS survey best practices. It is written as original, publish-ready content with no source links or citation placeholders.
Introduction: Why Creating an NPS Survey in Userpilot Matters
Creating an NPS survey in Userpilot is one of the simplest ways to turn customer feelings into product decisions. That sounds dramatic, but it is true. Your users are already having opinions about your product every day. Some are quietly cheering. Some are mildly confused. Some are one bug away from writing a breakup letter that starts with, “It’s not me, it’s your onboarding.” An NPS survey helps you catch those signals before they become churn, support overload, or missed expansion opportunities.
NPS, short for Net Promoter Score, measures how likely users are to recommend your product to someone else. In SaaS, that question is powerful because recommendation is not casual. Nobody recommends software that makes them look foolish in front of their team. When a user says they would recommend your product, they are also saying, “I trust this enough to attach my name to it.” That is customer loyalty wearing a tiny business suit.
Userpilot makes the process practical for product teams, customer success teams, growth managers, and SaaS founders who want feedback inside the product experience. Instead of sending yet another email survey into the inbox swamp, Userpilot lets you create in-app NPS surveys, customize follow-up questions, target the right audience, trigger the survey based on behavior, and analyze responses. The real magic is not only collecting a score. It is learning why users gave that score and what to do next.
What Is NPS?
Net Promoter Score is a customer loyalty metric built around one famous question: “How likely are you to recommend this product, company, or service to a friend or colleague?” Users answer on a scale from 0 to 10. The answers are grouped into three categories: promoters, passives, and detractors.
Promoters: Scores 9–10
Promoters are your happiest users. They understand the product, see value from it, and may become advocates, reviewers, referral sources, beta testers, or case study candidates. In SaaS, promoters are especially valuable because they often reveal which features are creating the strongest product-market pull.
Passives: Scores 7–8
Passives are satisfied but not excited. They are not angry, but they are not wearing your product’s hoodie either. These users may continue using your product, but they are vulnerable to competitors, pricing changes, or unresolved friction. Passives are often where product teams find quick wins: better onboarding, clearer feature discovery, improved documentation, or more relevant use-case guidance.
Detractors: Scores 0–6
Detractors are unhappy users. Some may be blocked by bugs, poor onboarding, confusing workflows, missing features, or unmet expectations. A detractor is not automatically a lost customer, but they are waving a red flag. The faster your team responds, the better your chance of repairing the relationship.
How NPS Is Calculated
NPS is calculated by subtracting the percentage of detractors from the percentage of promoters. Passives are not included in the formula, although their feedback still matters.
For example, imagine 100 users respond to your NPS survey. If 55 are promoters, 25 are passives, and 20 are detractors, your NPS is 35 because 55% minus 20% equals 35. The score can range from -100 to +100. A positive score usually means you have more promoters than detractors, but the most useful benchmark is often your own trend over time. A team that moves from 12 to 28 after improving onboarding has a story worth telling, even if another company claims a higher industry benchmark.
Why Use Userpilot to Create an NPS Survey?
Userpilot is designed for product-led teams that want feedback connected to actual product behavior. That matters because timing changes the quality of answers. Asking a user for feedback after they complete a key workflow is more useful than asking at a random moment when they are half-focused, under-caffeinated, and possibly searching for the “close” button.
With Userpilot, teams can create NPS surveys without relying on engineering resources. The no-code setup helps product managers and customer success teams move quickly. You can customize the survey question, add follow-up questions, style the widget to match your brand, preview the experience, define targeting rules, and analyze responses after launch.
The biggest advantage is context. Userpilot can help you show surveys to specific users, segments, pages, domains, environments, or platforms. That means your NPS program can become more thoughtful than “spray survey everywhere and hope wisdom appears.” You can ask the right users at the right moment and connect their responses to product usage patterns.
How to Create an NPS Survey in Userpilot
Step 1: Go to Feedback > NPS
To create an NPS survey in Userpilot, start from the navigation menu and go to Feedback > NPS. From there, click Create NPS. This begins the setup process for your Net Promoter Score survey.
This first step is intentionally simple. The goal is to help teams start collecting customer sentiment without building a custom survey system from scratch. That is good news because “let’s build our own feedback tool” is how many innocent product roadmaps disappear into a foggy cave.
Step 2: Customize the NPS Question
Userpilot provides the standard NPS question format: “How likely is it that you would recommend [Company/Product] to a friend or colleague?” You can personalize the wording to match your product and brand voice. For example, a B2B SaaS company might ask, “How likely are you to recommend Acme Analytics to another operations leader?” A design platform might use, “How likely are you to recommend this workspace to a teammate?”
The key is to preserve the meaning of the NPS question. Do not turn it into a five-part riddle. Keep it direct, clear, and easy to answer. A good NPS question should feel like a tap, not a tax form.
Step 3: Add Follow-Up Questions
The number is useful, but the follow-up answer is where the gold lives. Userpilot allows teams to add follow-up questions after the score. These can be universal or score-based.
A universal follow-up asks every respondent the same question, such as: “What is the main reason for your score?” This is simple and effective, especially when your team wants consistent qualitative feedback.
A score-based follow-up changes depending on whether the user is a promoter, passive, or detractor. This usually produces more actionable insights because each group needs a different conversation.
- For promoters: “What do you like most about the product?”
- For passives: “What would make this product more valuable for you?”
- For detractors: “What is the biggest issue preventing you from getting value?”
Open-ended questions are especially useful because they let users explain their score in their own words. A score of 4 says “problem.” A comment that says “I could not invite my team because permissions were confusing” says exactly where the fire extinguisher should go.
Step 4: Create a Thank You Message
Userpilot lets you add a thank you message after users submit their answers. This may seem small, but it matters. A user just gave you feedback. Acknowledge it like a human, not like a vending machine that swallowed a coin.
You can also personalize thank you messages based on score. For promoters, you might say, “Thanks for the great feedback. We are glad the product is helping your team.” For detractors, try something more empathetic: “Thanks for sharing this. Your feedback helps us understand what needs to improve.”
A good thank you message should be short, warm, and respectful. Do not promise immediate miracles. Promise that the feedback is heard and will be used.
Step 5: Style the NPS Survey
Userpilot includes styling options so your NPS survey looks like part of your product, not a mysterious pop-up from the year 2009. You can adjust primary colors, background colors, logo, font family, text color, box style, border, shadow, corner radius, and progress indicator.
Brand consistency matters because users trust experiences that feel native. If your product has a clean, modern interface and your survey looks like it escaped from a discount newsletter template, response quality may suffer. The survey should be visible, readable, and friendly without screaming for attention like a toddler near a cake display.
Step 6: Preview on Web and Mobile
Before publishing, preview how the NPS survey appears on web and mobile. This step is easy to skip and painful to regret. Mobile layouts can behave differently, especially if your question is long, the widget overlaps important UI, or the scale buttons feel too small.
A responsive NPS survey should be quick to answer, easy to close, and clear on every device. If users need tweezers and monk-level patience to tap a score, your response rate will not thank you.
Configure NPS Targeting in Userpilot
Creating the survey is only half the job. The other half is deciding who should see it, where it should appear, and when it should trigger. Userpilot provides settings that help teams control NPS targeting and avoid survey fatigue.
Choose Platform and Environment
Userpilot allows you to target web app users, mobile app users, or specific environments such as production or staging. Testing in staging or limiting the survey to internal users first is a smart move. It lets your team catch awkward wording, styling issues, and timing problems before real users see the survey.
Use Domain and Page Targeting
You can display the NPS survey across all domains where Userpilot is installed or limit it to specific domains. You can also control page targeting by showing the survey on any page, specific pages, or URL paths.
This is helpful when the survey should appear after meaningful product exposure. For example, a project management tool might target users after they visit the dashboard several times or complete a project setup. A customer support platform might show NPS after users have handled enough tickets to form a real opinion.
Target Segments and Custom Conditions
Userpilot supports audience targeting through all users, only-me testing, saved segments, and custom conditions based on user attributes, company data, or product usage. Segmentation makes NPS more valuable because different users experience your product differently.
A new trial user, a long-term admin, and a power user on an enterprise plan should not always be treated as the same audience. Their scores may reflect different journeys. Segmenting responses helps you identify whether a problem belongs to onboarding, activation, feature adoption, account management, pricing expectations, or product depth.
Set NPS Triggers and Frequency
Userpilot also lets teams control triggering and frequency. This is important because even a beautifully designed survey becomes annoying if it appears too often. Nobody wants to feel like your SaaS product is following them around with a clipboard.
Behavioral Triggers
You can trigger NPS based on user activity such as page visits or time spent on a page. Behavioral triggers help ensure the user has enough context to answer meaningfully.
For example, a SaaS company may trigger NPS only after a user has completed onboarding, used a core feature, or returned to the product several times. This produces cleaner feedback than asking immediately after signup, when the user may still be wondering where everything is and whether they spelled their company name correctly.
Sampling Rate
Sampling rate controls how many eligible users see the NPS survey. Showing the survey to 100% of eligible users may be useful for smaller products or early feedback collection, but larger user bases may prefer a lower sampling percentage to reduce interruption while still collecting enough responses.
Frequency Settings
NPS should be measured regularly, but not relentlessly. Many SaaS teams run relational NPS quarterly or every six months, while transactional NPS may be tied to specific moments such as onboarding completion, support resolution, or feature use. The ideal cadence depends on your product cycle, customer lifecycle, and how quickly your team can act on feedback.
Localize Your NPS Survey
If your product serves users in multiple markets, localization is not a nice-to-have. It is a trust signal. Userpilot supports localization options that help teams translate NPS content for different audiences. This matters because survey clarity affects response quality.
Localization should go beyond word-for-word translation. The question should sound natural in the user’s language, maintain the intent of the NPS methodology, and avoid confusing phrasing. A poorly translated survey can turn a simple loyalty question into linguistic soup, and soup is not a metric.
Analyze NPS Responses in Userpilot
Once responses come in, the real work begins. Userpilot’s NPS analytics help teams understand sentiment, view responses, monitor score trends, and identify patterns among promoters, passives, and detractors.
A good NPS dashboard should answer several practical questions:
- How many users viewed the survey?
- How many responded?
- What is the response rate?
- What is the overall NPS?
- How is the score trending over time?
- Which user segments are happiest or most frustrated?
- What themes appear in open-ended responses?
Tagging responses is especially useful. If many detractors mention “setup,” “permissions,” or “reporting,” your product team has a direction. If promoters keep praising “automation,” “templates,” or “speed,” your marketing team has messaging fuel. Feedback should not sit in a dashboard like a decorative houseplant. It should guide action.
Turn NPS Feedback Into Action
The most common NPS mistake is treating the score like the finish line. It is not. The score is the doorbell. Someone is at the door with useful information, and your team should probably answer.
Follow Up With Detractors
Detractors deserve fast attention. Their comments can reveal friction that leads to churn. A customer success manager might reach out personally, offer help, or route the issue to support. Product teams should review recurring complaints and prioritize improvements based on severity, frequency, and strategic impact.
Learn From Passives
Passives are often one improvement away from becoming promoters. Their feedback may show missing “aha moments,” weak onboarding, unclear value, or underused features. In Userpilot, teams can use segmentation and in-app experiences to guide passive users toward features that match their goals.
Activate Promoters
Promoters can support growth. Depending on the relationship, you might invite them to leave a review, join a beta program, participate in a case study, refer peers, or share feedback on upcoming features. Do this respectfully. A promoter is not a free marketing intern. Ask at the right time and make the request easy.
Best Practices for Creating an NPS Survey in Userpilot
Keep the Survey Short
The strongest NPS surveys are brief. One score question and one thoughtful follow-up are usually enough. If your survey starts asking about pricing, onboarding, documentation, favorite sandwich, and childhood dreams, users will flee.
Ask After Meaningful Product Use
Do not ask too early. A user who signed up three minutes ago cannot fairly recommend your product. Trigger NPS after the user experiences core value, completes onboarding, uses a key feature, or reaches an important lifecycle milestone.
Use Score-Based Follow-Ups
Score-based follow-ups produce clearer insights because each sentiment group needs a different question. Promoters can tell you what is working. Passives can tell you what is missing. Detractors can tell you what is broken or frustrating.
Segment the Results
Overall NPS is helpful, but segmented NPS is where decisions become sharper. Compare scores by plan type, company size, role, lifecycle stage, feature usage, region, or onboarding completion. A low score among new users may point to onboarding. A low score among enterprise admins may point to permissions, reporting, or scalability.
Close the Feedback Loop
When users give feedback, respond when appropriate. Closing the loop shows users that their input matters. This does not mean every comment needs a personal essay. It means serious issues get attention, common themes get reviewed, and improvements are communicated back when possible.
Common Mistakes to Avoid
Asking Everyone at the Same Time
Blanket surveys are easy, but they can create noisy data. A better approach is to target users who have enough experience to answer well.
Ignoring Open-Ended Responses
The score tells you what happened. The comment tells you why. Ignoring comments is like reading only the star rating on a restaurant review and missing the part where someone says the soup arrived in a shoe.
Over-Surveying Users
Survey fatigue is real. If users see too many pop-ups, banners, and feedback requests, they may stop responding or provide rushed answers. Use frequency controls and sampling wisely.
Comparing Scores Without Context
Industry benchmarks can be useful, but they are not the whole story. Product type, audience maturity, pricing model, customer expectations, and survey timing all affect NPS. Track your own trend and connect changes to product actions.
Example NPS Setup for a SaaS Product
Imagine a SaaS company called FlowStack, a workflow automation tool for operations teams. The team wants to create an NPS survey in Userpilot to understand customer loyalty after users have completed meaningful setup.
The team creates the main question: “How likely are you to recommend FlowStack to a colleague?” Then they add score-based follow-ups. Promoters see, “What is the biggest reason you would recommend FlowStack?” Passives see, “What would make FlowStack more useful for your team?” Detractors see, “What is the main issue preventing you from getting value?”
Next, the team targets users who have created at least three workflows and invited at least one teammate. They exclude brand-new users because those users do not yet have enough experience. They set the survey to appear in production, only on the dashboard, after the user has spent enough time in the product. They use a moderate sampling rate and prevent the survey from showing too frequently.
After launch, the team reviews responses weekly. They discover promoters love automation templates, passives want better reporting, and detractors struggle with permissions. This gives the team three practical next steps: promote templates in onboarding, prioritize reporting improvements, and improve permissions documentation with an in-app guide. That is NPS doing its job.
Experience-Based Insights: What Creating an NPS Survey Teaches Product Teams
In real SaaS teams, creating an NPS survey often starts as a measurement project and quickly becomes a mirror. The team expects a number. Instead, they get a collection of user truths, some delightful and some slightly spicy. That is the value. A well-placed Userpilot NPS survey can reveal the emotional temperature of your product in a way that dashboards alone cannot.
One common experience is discovering that happy users are not always happy for the reasons your team expected. Product teams often assume users love the newest feature because it took three sprints, two roadmap debates, and one heroic engineer with a suspicious amount of cold brew. Then the NPS comments arrive, and promoters are praising something much simpler: speed, reliability, templates, or the fact that the product “just works.” That feedback can sharpen positioning, onboarding, and feature prioritization.
Another useful lesson comes from detractors. Negative feedback may sting, but it is usually more useful than vague praise. A detractor who says, “The setup process was confusing after step two” has given your team a map. The issue may not require a massive rebuild. It may need better microcopy, a checklist, a tooltip, a help article, or a guided flow. Userpilot is helpful here because the same platform used to collect feedback can also support in-app guidance and targeted experiences.
Passives are often the most interesting group. They are not furious, but they are not convinced. Their comments tend to reveal missing value. For example, a passive user might say, “It works, but I am not sure what to do next.” That is not a product failure. It is an activation opportunity. The team can respond with better onboarding, lifecycle messaging, contextual education, or use-case-based guidance.
A practical experience many teams share is that NPS becomes more useful when reviewed cross-functionally. Product managers see feature gaps. Customer success sees account risks. Support sees recurring confusion. Marketing sees language that can improve campaigns. Sales sees proof points and objections. When NPS feedback stays trapped in one team, its value shrinks. When it becomes part of weekly product and customer conversations, it starts changing decisions.
The best teams also learn not to obsess over one score movement. NPS can fluctuate based on sample size, timing, product releases, incidents, and audience mix. A single dip is not always a disaster, just as a single jump is not proof that everyone should throw confetti into the office ventilation system. Trends matter more. Segments matter more. Comments matter more. The goal is not to worship the number. The goal is to understand loyalty and improve the experience behind it.
Finally, creating an NPS survey teaches humility. Users experience your product in the wild, not in the polished demo environment where the Wi-Fi behaves and every dropdown opens like poetry. Their feedback reveals reality. Userpilot helps teams collect that reality inside the product, organize it, and act on it. That is why an NPS program should not be treated as a one-time survey. It should become a repeatable feedback loop: ask, analyze, act, measure, and improve.
Conclusion
Creating an NPS survey in Userpilot is more than setting up a quick customer loyalty question. It is a structured way to understand who loves your product, who is unsure, who is frustrated, and why. Userpilot gives SaaS teams the tools to create the survey, customize the question, add meaningful follow-ups, style the experience, target the right audience, control triggers, localize content, preview across devices, and analyze responses.
The best NPS programs are simple on the surface and disciplined behind the scenes. Ask one clear question. Add one useful follow-up. Show the survey at the right moment. Segment the results. Read the comments. Respond to the themes. Use promoters for learning and advocacy, passives for activation opportunities, and detractors for urgent improvement signals.
When used well, NPS becomes a practical customer feedback system, not just a number in a dashboard. It helps product teams prioritize better, customer success teams intervene earlier, marketing teams understand real value drivers, and leadership teams track customer sentiment over time. In short, Userpilot NPS helps you stop guessing what users feel and start building from what they actually say. Radical concept, right?
