Set a relative or fixed wait interval between steps or actions to define the timeline of how you want contacts to flow through your program.
All blueprints in both programs and classic programs provide suggested wait time intervals that can be changed to suit your program goals. You can configure relative (days, weeks, months) or fixed (calendar or manual entry) wait times before each step.
- Use a 0 days wait time between event-triggered entry and the first step to send the first message as quickly as possible.
- Prevent sending all messages in a single processing cycle by using a wait time between a series of steps.
- Hold contacts for an extended period of time using a wait. This can be useful if you are planning to add additional content at a later time.
- Use fixed date wait settings to ensure that messages are sent on a specific date.
Wait times function differently when they are placed before the Remainder path of a decision. By default, the Remainder path continuously evaluates contacts until they meet the criteria of the decision. Attach an Exit or another interaction to the Remainder path to define waits and how the contacts within it should proceed.
- Click the wait time icon on a connector line to open the wait time configuration box.
- Set a wait time by selecting the Relative or Fixed
- Relative waits are configured in days, weeks, or months.
- Fixed waits are configured by clicking the calendar icon and choosing a fixed date or by manually entering a date that the message will be scheduled to send. The day of week start date is Sunday. Dates are formatted based on the users language/locale settings. After set, dates display as m/dd/yy format. Hovering over the date displays abbreviated month, date, and year format. If a contact reaches a step after the step's fixed date has passed, the contacts do not pass this step. The contact waits there indefinitely unless you change this date.
- Click Apply.