Configure onboarding checklists by verifying seven items: task limits, navigation paths, visibility rules, trigger logic, content structure, permission checks, and activation goals.
Direct answer to configuring onboarding checklists
To configure onboarding checklists effectively, you must verify seven specific items across your chosen tools. The first item is the task limit, which is how many tasks or steps you can add. The second is the navigation path, showing where the checklist creation interface resides. The third is the visibility rule, determining when and for whom the checklist appears. The fourth is trigger logic, defining the conditions that start the checklist. The fifth is content structure, focusing on how tasks are organized. The sixth is the permission check, confirming who can publish or edit the checklist. The seventh is the activation goal, ensuring the tasks align with user success metrics.
If you use Intercom, count the tasks in your current checklist and compare that count with Intercom's recommendation of 3-7 tasks.
Key takeaways for onboarding checklists in Appcues, Intercom, and Userpilot
- Userpilot allows a maximum of 15 tasks in one checklist, according to Userpilot.
- Intercom supports up to 25 steps in one checklist, according to Intercom.
- Intercom advises using between 3-7 tasks to keep checklists manageable, according to Intercom.
- Appcues recommends naming items as tasks rather than features to improve clarity, according to Appcues.
- Intercom requires the "Can set Product Tours, Checklists and Tooltips live" permission to create checklists, according to Intercom.
Verify your current tool’s task limit against these specific caps before adding new items. Check your user permissions to ensure you have the necessary rights to publish changes. Review your existing checklist item names to confirm they describe actions rather than feature labels. If an Intercom checklist exceeds Intercom's recommended 3-7 tasks, shorten that Intercom list.
Reference table for checklist limits and paths
The following table lists configuration limits and navigation paths for Userpilot, Intercom, UserGuiding, and Pendo. Each row is sourced directly from the official documentation for that publisher.
| Publisher | Maximum Tasks/Steps | Creation Path | Source Document |
|---|---|---|---|
| Userpilot | 15 | Click Create Checklist, then enter the title | Userpilot |
| Intercom | 25 steps | Not specified | Intercom |
| UserGuiding | Not specified | Checklist page under Widgets on the left-hand menu | UserGuiding |
| Pendo | Not specified | Left-side menu: Guides > Resource Center | Pendo |
Userpilot states that the maximum number of tasks that you can add to one Checklist is 15, according to Userpilot. Intercom notes that you can add up to 25 steps to one Checklist, according to Intercom. UserGuiding instructs users to navigate to the Checklist creation page under the Widgets on the left-hand menu to create a new Checklist, according to UserGuiding. Pendo directs users to select Guides > Resource Center in the left-side menu, according to Pendo.
Verify that your task counts remain within these specified maximums before publishing. Confirm that your team members can locate the creation interfaces using the provided navigation paths.
Setting task limits and visibility rules
Userpilot defines a hard upper boundary for checklist content. The maximum number of tasks that you can add to one Checklist is 15, according to Userpilot. This specific limit applies to the "Create a Checklist" functionality within the Userpilot Knowledge Base. When configuring your onboarding flow, verify that your task list does not exceed this count to remain within the documented system constraints.
Appcues handles the persistence of checklist visibility differently. It stays visible as they navigate your app until they complete or dismiss the checklist, according to Appcues. This behavior is defined in the "Create a Checklist" documentation. The checklist remains on the screen during user navigation, requiring explicit completion or dismissal to remove it from the interface.
Intercom provides guidance on managing the visual density of your tasks. If you only use a title you'll notice 5 tasks are now visible before the customer has to scroll to see more, according to Intercom. This observation comes from the "Checklist Best Practices" article. The number of visible tasks before scrolling depends on the specific layout choices you make, such as including or excluding a title.
Intercom also advises on the total volume of tasks to maintain usability. Don't overwhelm customers with really long checklists, make them look manageable by using between 3-7 tasks in your checklists, according to Intercom. This recommendation is found in the "Checklist Best Practices" guide. Keeping the task count within this range helps ensure the checklist appears manageable to the end user.
To apply these rules, count your current tasks against the Userpilot limit of 15 and the Intercom recommended range of 3-7. Verify that your Appcues checklist will persist through navigation as expected. If you only use a title in Intercom, 5 tasks are visible before the customer has to scroll. These steps ensure your configuration aligns with the specific limits and visibility behaviors documented by each publisher.
Defining navigation paths and permissions
Locating the checklist creation interface varies by platform, requiring specific menu navigation before configuration can begin. In Userpilot, you access the builder by clicking Create Checklist and entering the checklist title in the pop-up window, as described in the "Create a Checklist" documentation Userpilot. For UserGuiding, the interface is found by navigating to the Checklist creation page under the Widgets section on the left-hand menu, according to UserGuiding. Pendo users must select Guides > Resource Center from the left-side menu to access the onboarding module, according to Pendo.
Permissions represent a critical gate before any checklist can be published or edited. Intercom requires that you are using the newest version of the Messenger and possess the specific "Can set Product Tours, Checklists and Tooltips live" permission to proceed, as stated in the "Design your Checklist" help article Intercom.
When configuring your team’s access, verify that each member has the correct permission level before assigning them to build checklists. Use the Userpilot, UserGuiding, and Pendo menu paths above when you look for the checklist builder. For Intercom, confirm the "Can set Product Tours, Checklists and Tooltips live" permission is active for any user attempting to create a new checklist.
To streamline your workflow, map these navigation paths to your team’s standard operating procedures. If your team uses multiple tools, create a quick-reference guide that lists the exact menu path for each platform. For Userpilot, note the "Create Checklist" button location. For UserGuiding, note the "Widgets" menu item. For Pendo, note the "Guides > Resource Center" path. For Intercom, note the permission requirement. This reduces the time spent searching for the correct interface and minimizes errors caused by users lacking the necessary permissions.
Structuring content for activation goals
Aligning checklist tasks with user activation milestones requires specific naming conventions and trigger logic. According to Appcues, name items as tasks, not features: "Invite a teammate" is clearer than "Team Settings Configuration." Front-load your easiest item to build early momentum. This approach ensures the first step is immediately actionable, reducing initial friction for the new user.
When configuring the behavior of individual tasks, consider how they interact with the broader onboarding flow. According to Appcues, if the flow should only appear when launched from the checklist, set that flow's trigger to Show Manually in its settings. This specific trigger configuration prevents the task from appearing in other contexts, keeping the user's focus on the checklist structure.
The strategic purpose of these structures is to guide users toward specific outcomes. According to Userpilot, checklists are increasingly becoming a vital tool for guiding new users toward successful activation. By breaking down the path to value, the checklist serves as a navigational aid for the user.
Furthermore, the visual presentation of these tasks matters for user engagement. According to Appcues, checklists give users a visible path to activation by breaking onboarding into concrete tasks. This visibility helps users understand their progress and what remains to be completed.
To implement these principles, review your current checklist items. Ensure each label describes a specific action rather than a feature name. Verify that any flows attached to these tasks are set to Show Manually if they should not trigger independently. This alignment between naming, triggers, and activation goals creates a coherent onboarding experience.
Blank worksheet for checklist configuration
Document the checklist title, task count, activation goal, and visibility rule for each tool you configure. Record the checklist title, the exact number of tasks you plan to include, the specific activation goal the checklist targets, and the visibility rule that controls when the checklist appears to users.
When entering your visibility rule, note that UserGuiding requires an additional check for any guides embedded within the checklist. If the Guide you placed inside a checklist is inactive, it won't be visible in the live version of the Checklist until you activate the Guide too, according to UserGuiding. Ensure your visibility rule column reflects this dependency if you are using UserGuiding for your primary onboarding flow.
Record those four fields in your own notes for this setup. For the Visibility Rule cell, specify the user segment or trigger condition that makes the checklist visible. If your configuration involves embedded guides, verify their active status before finalizing the row. This worksheet serves as your configuration record for the current setup cycle.
Review each entry to ensure it matches your current tool settings. If you are configuring multiple tools, keep a separate note of those four fields for each tool. Keep this document updated as you make changes to your onboarding flow. The goal is to have a clear, auditable record of your configuration choices.
Related guides
FAQ: Checklist setup for Appcues, Intercom, Userpilot, and UserGuiding
What is the maximum number of tasks allowed in a Userpilot checklist?
Userpilot's maximum is 15 tasks in one checklist. You can add no more than 15 tasks to one Userpilot checklist.
How many steps can you add to an Intercom checklist?
You can add up to 25 steps to one Checklist, according to Intercom. This specific step limit defines the maximum complexity for a single checklist in this platform. Verify your step count against this figure during configuration.
Where do you find the checklist creation page in UserGuiding?
To create a new Checklist, navigate to the Checklist creation page under the Widgets on the left-hand menu, according to UserGuiding. This navigation path is the specific location for initiating a new checklist in the interface. Use this exact menu structure to access the creation tools.
What permission is required to create checklists in Intercom?
You must be using the newest version of the Messenger and have Can set Product Tours, Checklists and Tooltips live permission, according to Intercom. This specific permission requirement is necessary to proceed with checklist creation. Confirm your user role includes this exact permission before starting.
How should you name checklist items to improve clarity?
Name items as tasks, not features, according to Appcues. The source notes that "Invite a teammate" is clearer than "Team Settings Configuration." Front-load your easiest item to build early momentum, as suggested by the documentation.
Sources
Limits of this post
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.