How to prioritize guides

Bento's air traffic control system gives you fine grained controls while protecting end users from spam and collisions

Meera Kanani avatar
Written by Meera Kanani
Updated over a week ago

In order to build successful "everboarding" end-users must feel like their activation experiences are thoughtful and not spammy.

For Growth and Product teams, however, it's easier said than done. There are often multiple teams building and launching experiences, and coordination is expensive.

Here, we'll review the controls you have today, as well as a peek into the controls you'll have in the future.

Guides must be prioritized at launch

When setting guides to auto-launch, you must set a priority relative to all other guides.

  • By default, a guide is slotted into the lowest priority rank. If you believe your guide should rank higher, you can drag it higher.

  • Guides that are manually launched from the customers table will respect the priority set at the template level.

Command center

You can always review the priority of live guides, as well as make edits from within the Command Center.

To see relevant details about a guide, hover over its name

Call-outs

If you have a live onboarding guide, the sidebar will animate open to make the user aware of it one time

  • This happens because Onboarding are generally more important than a new feature or marketing announcement

  • This is also to ensure your users are aware of the sidebar, and the kinds of experiences that can be found there.

  • This only happens once. If it is important to you that the sidebar never auto-animates open, please let us know and we can turn it off for you.

Announcements are throttled to one per session

We only allow 1 modal to appear per user web session to avoid spam. You can read more here.

  • Modals that are launched explicitly (i.e. when an end-user clicks a button that launches a modal) are not included in this throttling. Read more about launch CTAs here.

  • We plan on adding more throttling controls in early 2024.

When an end-user is in the middle of a flow, we will not interrupt them

When creating a product tour, or a multi step contextual guide that goes to different pages, we want to ensure your user isn't interrupted.

  • Even though other guides may be prioritized to launch on a certain page, they won't just pop-up and interrupt the user.

  • When the user ends their journey, either by completing or dismissing it, then the next highest priority guide will be shown.

Did this answer your question?