🎡 Make it optional:

• Don't force users into using your product.
• Give them an overview of the functions they'll find most valuable, and allow them to check out other parts of your app as they wish.
• Whether they are exploring on their own or learning via a tour, consider it a great thing; users are engaged.
Chameleon tours are built such that a user can close out of them as they choose!

🚗 Don't be invasive:

Choose the best use case for each step of your tour.

Modals are excellent at the beginning or end of a tour for providing overall context on a page, but we wouldn't recommend using them in every step.

Utilize Infotips to offer a less-invasive way for prompting users to take action on a page. Infotips will display in the bottom-right of a page, so users can refer to them while figuring out where to click next.

Lightboxes and Hotspots will highlight a specific element on a page, and can be used when pointing out non-obvious or very critical things you want users to see.

🎯 Choose the right timing:

Carefully consider the timing of when you want to present a tour to your user base. Naturally, new users will find a tour helpful when they're seeing your product for the first time. Also think about how you can add depth to a returning user's experience. If they're executing more advanced functions in your tool, build a tour for when they click these links / pages to learn about them as well.

🏇🏽 Drive to action:

The first thing users want to do when they find themselves in a new product is jump in and use it!

Rather than creating a tour that just gives a bunch of information about your app, make sure to incorporate ways to get users interacting with your product! In doing so, users will learn your product much more quickly. Not to mention, they'll be far more engaged in the tour. 

📕 Build for the right length:

Reaching that sweet spot in the length of your tour is important; if it's too short, it won't be very helpful, and if it's too long, users will become frustrated or disengaged.

We recommend 2-3 steps in each tour.

Understandably, you might have many more features to showcase to users. Consider building multiple tours that are triggered after specific user actions (e.g. clicking a link). That way, users learn in a format that's easily digestible and relevant to the actions they want to take in that very moment.

☝🏽 Understand tour priority:

If you create multiple tours that would otherwise be shown to a user at the same time, then the tour that is higher in your list will be show first. Then following the completion of the first tour, the second will be shown.

You can easily change the priority of tours by hovering over it and using the up-down arrows on the right:

Example

Assume two tours A and B. A has Step 3 (A3) matching on /settings B has Step 1 (B1) matching on /settings

If a user has

  • clicked button on A2 and then loads /settings then they will see A3.
  • not clicked button on A2 (e.g. is still on A1) or has already completed A3 (clicked the button) then they will see B1

If you have any questions about this, we'd love to hear from you (green bubble on the bottom right of screen)! 💬

Did this answer your question?