Skip to main content

Wait Action: Major Revamp

The Wait action has been completely redesigned with a new intent-based setup experience, recurring schedules, AI-powered configuration, dynamic wait durations, and simplified date-based waits.

Who This Is For

This update is for users who build workflow automations that depend on timing, scheduling, contact replies, appointment events, or conditional delays.

It is especially useful for:

  • Businesses building nurture or follow-up automations

  • Teams using appointment reminders or booking workflows

  • Users waiting for replies, clicks, or engagement events

  • Advanced workflow builders using dynamic timing logic

  • Users who previously struggled with configuring Wait actions

What Changed in the Wait Action

The Wait action now includes:

  • Intent-based wait type selection

  • Recurring wait schedules

  • AI-powered Wait setup

  • Single-step specific date waits

  • Dynamic wait durations

  • Seconds as a supported wait unit

  • Grouped wait types

  • Context-aware wait recommendations

The redesign simplifies workflow setup and reduces configuration confusion.

New Intent-Based Wait Selection

The old dropdown-based setup has been replaced with a card selection interface.

Instead of searching through nested dropdowns, users now select what they want the contact to wait for first, then configure the wait settings.

Available wait types include:

  • A set period of time

  • A specific date and time

  • A recurring schedule

  • An upcoming appointment or booking

  • The contact to reply

  • The contact to take an action

  • Specific conditions to be met

This structure makes Wait configuration faster and easier to navigate.

Recurring Wait Schedules

The Wait action now supports recurring schedules.

Users can configure waits that repeat:

  • Weekly

  • Monthly

  • Yearly

Weekly schedules support selecting specific days and times.

Example:

  • Every Monday, Tuesday, and Wednesday at 9:00 AM

This is useful for:

  • Recurring reminders

  • Weekly follow-ups

  • Subscription renewals

  • Scheduled check-ins

  • Annual or monthly workflows

Wait Until a Specific Date in One Step

Previously, users had to configure:

  1. A Set Event Start Date action

  2. A separate Wait action

Now, users can configure a specific date directly inside the Wait action.

Users can:

  • Select a fixed date and time

  • Choose how the contact should proceed

  • Define behavior if the selected date has already passed

This significantly reduces workflow complexity.

AI-Powered Wait Setup

The Wait action now includes a Set up with AI option.

Users can describe the desired wait behavior in natural language, and the AI Builder automatically generates a configured Wait action.

Example prompts:

  • “Wait 2 days then resume on weekday mornings”

  • “Wait until a specific date”

  • “Wait one hour before their appointment”

After generating the configuration, users can:

  • Add the Wait action directly to the workflow

  • Modify the generated setup before saving

This reduces manual configuration time for complex wait logic.

Dynamic Wait Durations

Wait durations can now use dynamic values instead of fixed numbers.

Users can pull wait duration values from:

  • Custom fields

  • Contact fields

  • Supported variables

This allows workflows to adapt automatically based on record data.

Example use cases:

  • Wait based on subscription length

  • Wait using onboarding timelines

  • Delay follow-ups based on customer-specific settings

Seconds Are Now Supported

The Wait action now supports seconds as a time unit.

Users can create rapid timing sequences using:

  • Seconds

  • Minutes

  • Hours

  • Days

This is useful for:

  • Rapid-fire automation sequences

  • Short engagement delays

  • Testing workflows

  • Multi-step action timing

Grouped Wait Types

Related wait conditions are now grouped together to reduce clutter.

Examples include:

  • Contact reply events grouped into one category

  • Contact actions grouped into one category

  • Appointment and booking waits unified into one selection area

This makes the Wait action easier to scan and configure.

Context-Aware Wait Recommendations

The Wait action now adapts based on workflow context.

Example:

If the Wait action is added immediately after:

  • Send SMS

  • Send Email

  • Send WhatsApp message

The option to wait for a contact reply is automatically prioritized at the top of the selection screen.

This helps users find the most likely wait condition faster.

Why This Matters

The Wait action was previously one of the most common sources of workflow support tickets.

Two major issues caused most confusion:

  1. Users did not realize that waiting until a specific date required a separate Set Event Start Date action.

  2. Contact Reply waits were hidden under CRM Events while Time Delay was the default option.

The redesigned Wait action solves these problems by:

  • Introducing a single-step date wait setup

  • Replacing dropdown-heavy navigation with intent-based cards

  • Automatically surfacing the most relevant wait types

  • Adding AI-assisted configuration

The result is faster workflow setup, fewer configuration errors, and a more intuitive automation experience.

FAQ

Can I create recurring waits in workflows?

Yes. The Wait action now supports recurring weekly, monthly, and yearly schedules.

Can I wait until a specific date without using another action?

Yes. Specific date waits are now configured directly inside the Wait action.

Can Wait durations use custom field values?

Yes. Wait durations can now dynamically pull values from supported fields and variables.

Does the Wait action support seconds?

Yes. Seconds are now available as a supported wait unit.

Can AI configure Wait actions automatically?

Yes. The Set up with AI feature allows users to describe wait behavior in natural language and generate a configured Wait action automatically.

Does the Wait action change based on workflow context?

Yes. Relevant wait types are automatically prioritized based on nearby workflow actions.

Did this answer your question?