Wait Steps & Conditions
Module: Automations • 11:42
Overview
Wait steps and if/else conditions are two of the most-used actions in the automation builder. If/else lets you fork the customer journey into different paths based on tags, fields, or activity, while wait steps hold a contact in place until a time, date, reply, or condition is met. This lesson walks through every type of if/else branch and every wait option so you can build precise, conditional workflows.
Step-by-Step Instructions
Add an if/else condition
Inside a workflow, add an Internal → If/Else action. This breaks the customer journey into different paths depending on conditions set on the contact record or in the automation itself.
Use scenario recipes or build your own
Recipe templates include branches based on your availability (open/closed hours), contact tags, last confirmed appointment, active in another workflow, email events, opportunity pipeline stage, and order submitted. Some recipes require a specific trigger or a preceding wait step — otherwise build your own condition.
Configure branch filters
For each branch, select Contact Details → Standard Fields → Tags and choose 'includes' (or does not include / is empty / is not empty), e.g. 'includes active client'. Rename each branch (e.g. 'Active client', 'Inactive client') so the logic is readable without clicking in. You can add more AND/OR filters, add more branches, and reorder them.
Understand the 'none' branch
Every if/else has a 'none' branch that catches contacts who match no condition. Save the action and rename it so you can see at a glance which path each contact takes — active client down one path, inactive client down another, everyone else down the none path.
Add a wait step — set period of time
Add a Wait action to hold a contact until a condition exists or they reply. 'For a set period of time' waits a literal number of minutes, hours, or days (e.g. wait one day). Use the advanced window to restrict sending to specific hours/days (e.g. Mon–Fri 9am–5pm) so nothing goes out on weekends.
Wait until a specific date/time
Choose a fixed date and time (e.g. Dec 25, 2026 at 9am) and decide what happens if the day has already passed — usually 'skip all outbound communication' so it skips ahead to the next wait or event start date.
Wait until a recurring window or scheduled date
Recurring window repeats weekly/monthly/yearly on set days at a set time (e.g. weekdays at 9am). Scheduled date/time is ideal for appointment triggers — e.g. wait one day before the scheduled appointment time, using the calendar event tied to that contact.
Wait until a reply or action
Wait until the contact replies (needs a preceding SMS, with an optional timeout that branches if they don't reply), wait until a user on your team replies, wait until the contact takes a specific action (clicks a trigger link or triggers an email event like open/click), or wait until specific conditions are met (e.g. tag 'client paid' is added in another automation).
Common Mistakes
- Forgetting to save changes before navigating away.
- Not testing the configuration after setting it up.
- Skipping the prerequisites mentioned in the overview.
OS University™