Architect Journey: Wait for Some Time

Wait for some time allows you to arrange the time duration so that it aligns with the action you expect users to take.

Take, for example, a retail company. New users sign up on average within one hour after they have come to the website. Also, users make a purchase in 15 minutes of adding an item to their cart. Lastly, 76% of users open your emails within one day.

• In case you consider to engage users to make them sign up after you interact, you can determine 1 hour for wait duration. After that, you can check whether they have signed up or not.
• In the case of sending a cart abandonment email, you can determine a 15-minute waiting time duration and then check whether users are still cart abandoners or have already become buyers.
• In case you would like to follow up on an email that you previously sent, you can determine a one day-long wait time duration before checking their ‘open’ action on the email to design your next step in the flow accordingly.

How does it work?

Wait for some time creates time gaps in the journey by letting users wait for a specific duration before they enter the next element. To determine the time duration, you can consider how long it takes for specific user behavior to change and how long it takes for them to take specific actions.

Wait duration starts when the user arrives at the wait element. For example, your journey flow is starter > wait > check > email. Wait duration is 30 minutes. You launch the journey today at 1 pm. User enters journey at 2 pm. User arrives at wait element at 2.01 pm. User will proceed to check element at 2.31 pm. Users are held in the ‘wait’ element on the flow until the time duration is over.

Use Cases

• Send a follow-up email after a specific time-space to not make the communication too frequent.
• Let users take desired actions by giving them the time according to your industry standard.