NPS survey logic: 7 configuration checks to verify

Verifying NPS survey logic requires checking seven distinct configuration areas to ensure surveys reach the correct users. The first item is trigger rules, which determine when a survey initiates. The second is test commands, allowing you to bypass standard configuration for immediate verification. The third is display logic, which controls conditional visibility of specific questions. The fourth is preview settings, used to check how surveys appear on different devices. The fifth is logic operators, which define how multiple rules combine to trigger actions. The sixth is question order, ensuring the survey flow matches your intent. The seventh is survey setup, the final configuration before launch.

According to Vitally, selecting the correct trigger rules is a prerequisite before building Playbook automation. This step prevents unintended survey delivery. You must verify that your chosen rules align with your customer segmentation strategy. Incorrect trigger rules can lead to surveys firing for the wrong accounts.

Test commands provide a direct method to validate survey display without waiting for natural triggers. These commands allow you to force a survey to appear for a specific test user. This is critical for confirming that the survey renders correctly. Display logic ensures that conditional questions only show when specific criteria are met. You must verify that these conditions function as expected.

Survey setup is the final step before going live. This includes checking all fields, branding, and delivery settings. Each of these seven items requires individual verification. Skipping any one can result in survey failures or incorrect data collection.

Before you launch a major NPS campaign, verify that your survey logic triggers for the right users. The following points summarize the core verification steps across your tools.

1. Trigger rules. Configure your entry conditions carefully. For example, if you do not want Playbook automation to include churned enrollees, add a filter for "Churned at > date is not set" for Orgs and Accounts or "Deactivated at > is not set" for Users if your lifecycle tracking rules have been configured.

2. Test commands. Use built-in verification commands to bypass standard configuration. According to Vitally, the Vitally.nps('test') command force displays a survey to users and skips your configuration, allowing you to check the display without meeting trigger criteria.

3. Display logic. Ensure conditional questions behave correctly. According to Gainsight, if you select the Display Logic option, it allows you to show or hide a survey question, displaying it only to participants when they select a particular answer option to an earlier question.

In Vitally, your trigger rules are what control what goes in and out of your Playbooks, so it is very important that you start with the correct list of customers, according to Vitally. These rules control what goes in and out of your Playbooks. Before you activate a new NPS campaign, review the specific conditions that will add accounts to the playbook. If the initial list is too broad, you will send surveys to users who should not receive them. If the list is too narrow, you will miss key accounts that need feedback. The accuracy of this initial filter is the foundation for the entire automation sequence.

A common issue in customer success operations is the inclusion of accounts that have already left your platform. To prevent this, Vitally provides specific filter options for your lifecycle tracking. If you don't want your Playbook automation to include churned enrollees, simply add a filter for "Churned at > date is not set" for Orgs and Accounts or "Deactivated at > is not set" for Users if your lifecycle tracking rules have been configured, according to Vitally. These filters keep churned enrollees or deactivated users out of Playbook automation when lifecycle tracking is configured. You must apply these filters to the relevant entity types based on how you structure your customer data. For organization-level surveys, apply the Orgs and Accounts filter. For individual user-level surveys, apply the Users filter.

Verifying that a survey appears for the correct audience is often difficult because the standard display function adheres to your existing setup. Since Vitally.nps('survey') follows your NPS configuration, testing can sometimes be a bit cumbersome, according to Vitally. To bypass these constraints during verification, the platform provides specific commands that override standard logic. You can use Vitally.nps('show') to force display a survey to users and skip your configuration, according to Vitally. This command allows you to see the visual layout without needing to meet specific user criteria.

Similarly, Vitally.nps('test') force displays a survey to users and skips your configuration, according to Vitally. These two commands serve the same purpose of ignoring your rules to ensure the survey renders correctly. When using these commands, you are not testing the trigger logic itself, but rather the survey's appearance and functionality. This distinction is critical because a survey that displays correctly under a forced command may still fail to trigger for real users if the underlying rules are misconfigured.

While these commands help with visual verification, you must also check the specific rule settings that govern normal operation. Scroll to the bottom section asking "Should a user be required to match a set of Playbook rules in order for the survey to show?", according to Vitally. This setting determines whether the survey relies on Playbook conditions to appear. If this option is enabled, the survey will only show when a user meets those specific Playbook criteria.

To properly test your NPS logic, you should first use Vitally.nps('test') to confirm the survey displays as intended for a test user. Then, review the Playbook rules section to ensure the conditions match your target audience. Do not rely solely on the forced display commands to validate your trigger logic, as they skip the very configuration you are trying to verify. Use the forced commands to check the survey design and then switch to standard testing methods to validate the rules. This approach ensures that both the visual presentation and the logical triggers are functioning correctly before you launch your survey to a broader audience.

Before building the survey structure, Gainsight recommends developing your survey questions and deciding which question types to use before you set them up in Gainsight, according to Gainsight. This preparatory step allows you to map out the flow before interacting with the platform's configuration tools. Once the questions are defined, you can use Display Logic to control which participants see specific items.

Display Logic allows you to show or hide a survey question, displaying it only to participants when they select a particular answer option (condition/rule) to an earlier question, according to Gainsight. This feature ensures that the survey remains relevant to the respondent's previous answers. If your survey requires complex conditions, you can change logic between multiple rules in the Expression option, according to Gainsight. This allows you to define how different conditions interact with one another.

When arranging the options for a specific question, you can click and hold the 6 dots icon right to an answer option to move it to another position to arrange them in a specific order, according to Gainsight. This drag-and-drop functionality lets you customize the sequence of choices presented to the user. You can repeat this action for each option to establish the exact order you need for your analysis.

To verify the logic works as intended, create a test survey with a simple conditional question. Set a rule so that Question 2 appears only if Question 1 is answered with a specific option. Use the 6 dots icon to reorder the answer options for Question 1 to match your desired presentation. Question 2 should appear only when Question 1 is answered with that specific option. Check the Expression option if you have added multiple rules to ensure the logic between them is set correctly. This verification process confirms that the survey flow matches your design intent before you launch it to your customer base.

When you prepare a customer loyalty survey in HubSpot, the interface distinguishes between web page surveys and email surveys. According to HubSpot, you should follow the specific instructions to customize the web page survey or email survey depending on which type you are creating. You can also select the On 50% page scroll option, according to HubSpot. This setting controls when the survey appears on the screen. Before you launch, you must verify that the survey looks correct on every device your customers use. To preview how your survey will appear on desktop, tablet, and mobile, click the Actions dropdown menu and select Preview, according to HubSpot.

Use this preview mode to check the layout, font sizes, and button placement. If you are using the On 50% page scroll option, confirm that the survey appears at the intended scroll depth. The preview function allows you to see the exact rendering without sending the survey to a live user. This step is part of your broader verification process. You are checking that the survey displays correctly for the right users.

The following table summarizes specific logic and automation features for Vitally, Gainsight, HubSpot, and Custify based on their respective documentation.

Use this table to cross-reference your current setup against these documented capabilities.

• Onboarding tools: compare 4 customer project plans
• Health score setup: 8 rules for weights and validity
• NPS survey configuration: 5 checks before launch

How do I force display an NPS survey in Vitally for testing?

You can use the Vitally.nps('test') command to force display a survey to users and skip your configuration, according to Vitally. Alternatively, the Vitally.nps('show') command also force displays a survey to users and skips your configuration, according to Vitally. These commands allow you to verify the visual output without relying on standard trigger rules.

How to change logic in the Expression option?

Gainsight allows you to change the logic between multiple rules in the Expression option, according to Gainsight. This setting lets you define how different conditions interact within your survey design.

How do I rearrange answer options in a Gainsight survey?

Click and hold the 6 dots icon right to an answer option to move it to another position to arrange or rearrange them in a specific order, according to Gainsight. This drag-and-drop feature allows you to customize the sequence of response choices for your respondents.

This post is general operational information, not legal advice about notice periods or renewal clauses. It does not promise that any method keeps a customer. A review model checked the facts once, and that check can miss errors, so open the sources before you act.