Yes, you can build this logic into a single journey using the Wait for Trigger element. This element is designed to pause a user's journey until they either perform a specific action or a set time limit is reached, making it ideal for sending reminders.
Here is how to set up a workflow for an onboarding task with a reminder:
Initial Message: Start your journey by sending the user a message prompting them to complete the first task (e.g., "Welcome! Your first task is to...").
Add 'Wait for Trigger': Immediately after the initial message, add a
Wait for Triggerelement to your journey canvas.Configure the Element:
- Trigger Event: Set the event that signifies the task is complete. For example, you might use a custom event like
task_1_completedthat your app sends when the user performs the action. - Timeout Period: Define how long the journey should wait for this event before considering the user inactive. For example, set it to
2 days.
- Trigger Event: Set the event that signifies the task is complete. For example, you might use a custom event like
Connect the Output Paths: The
Wait for Triggerelement has two distinct paths for the user to follow:- Success Path (if the event occurs): Connect this path to the next primary step in your journey. For example, if the user completes Task 1, this path would lead to a message introducing Task 2.
- Timeout Path (if the time limit is reached): Connect this path to a reminder message (e.g., a Push Notification or Email saying, "Don't forget to complete your first task!").
Handle Post-Reminder Actions: After the reminder message on the Timeout Path, you can add another
Wait for Triggerelement. Configure it to wait for the same event (task_1_completed) to ensure that if the user completes the task after the reminder, they are merged back into the main journey flow (e.g., by connecting its Success Path to the message for Task 2).
Comments
0 comments
Please sign in to leave a comment.