This article provides real world examples of using the New Visibility Rules to determine when, where, and to whom your content and widgets appear.
The following table lists common use cases, their function, and how each rule can be applied in real-world scenarios.
Function | Use case | Rule used |
|---|---|---|
Show a Smart Tip when an error message appears | Consider an expense submission form. If a user enters an amount over $1,000, the application displays the error message: "Amount exceeds allowed limit." A Smart Tip can be configured to appear immediately alongside this message to guide the user on the correct action, such as suggesting they contact their manager or split the expense. | |
Trigger a Survey after a Flow completes | Your HR application requires new employees to complete a mandatory onboarding Flow on their first day. To gather timely feedback on the clarity and effectiveness of the guided steps, trigger a Whatfix Survey immediately after the Flow ends. This maximizes response rates while the experience is fresh in the employee's mind. | Events related to Whatfix Content → After the flow ends |
Use a Window Variable to show a Beacon only to specific user roles | A reporting dashboard contains advanced controls (such as a "Manage Access" button) meant exclusively for Admin users. By checking a backend window variable, such as userRole, a Beacon can be configured to appear only for users whose role is "Admin," effectively highlighting the feature without cluttering the view for standard users. | |
Trigger a Pop-up when a user performs a specific action | In a document management system, users click the "Download Contract" button. Before the download starts, a Pop-up appears explaining mandatory compliance rules or legal disclaimers associated with downloading sensitive documents. | |
Show a Pop-up before a Flow starts | For a company's new employee onboarding process, a Flow guides them through setting up their HR profile. To prevent incomplete submissions, a Pop-up appears before the Flow starts, reminding users to gather all necessary documents (for example, ID proof, bank account details). | Events related to Whatfix Content → Before the Flow starts |
Trigger a Pop-up after a Flow ends | Consider an onboarding flow for a payroll setup. After completing the Flow, a Pop-up appears thanking the user and suggesting optional best practices, such as verifying data consistency across departments. | Events related to Whatfix Content → After the flow ends |
Show a Pop-up only to users with a specific account type | A Pop-up is used to announce and provide access to a new set of beta features for Enterprise-level customers. This Pop-up uses the user's Enterprise Attribute to ensure only the premium customers receives the notification. | |
Block a UI element only for certain roles | On the analytics dashboard, buttons such as "Create Report" or "Edit Insights" are restricted. A Blocker is implemented for users assigned the "Viewer" Role Tag, preventing them from interacting with the buttons and optionally displaying a message explaining the restriction. | |
Show Pop-ups based on user-specific data | Your internal CRM application has a LicenseType attribute (for example, 'Pro', 'Enterprise'). You need to trigger a Pop-up announcing a new feature only for users who have the 'Enterprise' license type. The rule fetches the LicenseType from your application's user data and displays the Pop-up only if the value matches 'Enterprise'. | |
Show a Pop-up to new active users about a new feature | You want to announce the latest version of your application specifically to users who are still actively learning the system. You create a Cohort for users who have been in the system for 7 days or less AND have completed at least 3 Tasks. A Pop-up is displayed only to this group, introducing the new version and linking to a quick demo Flow. | |
Trigger a Survey when a user closes a Flow step | During an expense approval Flow, if a user closes a specific step midway, a Survey appears, asking the users for feedback on why they skipped the step (for example, "Was the instruction unclear?" or "Was any information missing?"). This helps improve the onboarding experience. | Events related to Whatfix Content → User closes the step |
Trigger a Pop-up after user submits a Survey | After completing a customer feedback Survey, a Pop-up appears thanking the user and linking to helpful resources (for example, knowledge base, tutorials). | Events related to Whatfix Content → User clicks on submit |
Show Smart Tip when a required field is empty | In a registration form, the "Phone Number" field is mandatory. A Smart Tip is displayed only when the field is empty, gently reminding the user to fill in the required information before submission. | |
Show Pop-up when an error message appears | If a user attempts a login and the application displays the text "Invalid Password," a Pop-up is triggered to appear. This Pop-up immediately guides the user to the "Reset Password" link or provides troubleshooting steps. | |
Trigger a Survey on successful task completion | A user has successfully completed a complex ticket submission or an asset purchase. The application displays a message, such as "Your order has been placed successfully. Order #12345." A Survey is triggered immediately based on the appearance of this specific success message. The survey can ask: "How would you rate the experience of placing this order?" This captures instant user satisfaction feedback at the peak of their engagement. | |
Remind users about pending action | An employee opens their expense dashboard which lists all submitted reports. If an expense report has been returned for correction, a status label reads "Action Required." A Beacon is displayed right next to this label to provide a highly visible and contextual reminder that the report needs immediate attention, preventing delays in the reimbursement process. | |
Show Pop-up for outdated data | A sales manager is viewing their monthly sales performance dashboard. The application displays a timestamp or a warning in a corner stating: "Data last updated: 48 hours ago. Please refresh." A Pop-up is triggered by this text to alert the manager that their view is not current, and it contains a clear link or instruction on how to initiate a data refresh to ensure decisions are based on the latest information. |