Announcement throttling

Preventing your users from dismissing a modal only to get another one.

Emily Wang avatar
Written by Emily Wang
Updated over a week ago

One of the hardest things to manage as you scale is the number of concurrent activation experiences.

In most companies, PMs have to meet regularly and horse-trade so one PM turns off a flow and another can turn one on. Otherwise you're met with screenshots of miffed customers who get modals on modals, or one after the next.

Bento's throttling logic

Bento reduces this likelihood by throttling modals and banners 1x user session, unless it's explicitly launched via a CTA. Let's look at two scenarios:

Scenario 1

  1. PM 1 announces a new feature targeted to all users on any page.

  2. PM 2 announces a new feature on page url = settings for users where role = admin

All else equal, Modal #2 is launched at a higher priority than Modal #1

User A

Let's say an admin user shows up and lands on the homepage. Voila! They get Modal 1.

Then they navigate to Settings.

  • In this session, they won't get the second modal but the next time they log in, they will

User B

Now let's say a different admin user logs in and goes straight to Settings. Since the modal targeting Settings is prioritized higher, the user will get that modal.

As they navigate around the app, have no fear, they won't be bombarded with that other Modal 1 (until their next session)

Scenario 2

  1. PM 1 announces a new feature targeted to all users on any page. One of the CTAs on this modal is to kick off a 2-step product tour where the final experience is another modal.

  2. PM 2 announces a new feature on page url = settings for users where role = admin.

All else equal, Modal #2 is launched at a higher priority than Modal #1

User A

Let's say an admin user shows up and lands on the homepage. Voila! They get Modal 1.

  • They opt into the tour. Because each step of the tour only continues on click, the user gets the final modal.

Then they navigate to Settings.

  • In this session, they won't get the second modal but the next time they log in, they will

User B

Now let's say a different admin user logs in and goes straight to Settings. Since the modal targeting Settings is prioritized higher, the user will get that the Settings modal.

As they navigate around the app, they still won't get the other modal and tour until their next session.

Note: If you want to launch multiple modals back to back you can use a CTA to launch the second modal from the first.

Did this answer your question?