What's new

The Wait action has been completely redesigned with a new intent-based UI, recurring schedules, and AI-powered setup.

New intent-based card selection.

The old dropdown has been replaced with a card selection screen that asks "What should the contact wait for?" Users now pick their intent first, then configure — no more hunting through nested dropdowns to find options like "Wait for a contact reply."

Recurring wait schedule.

Set up recurring waits with weekly, monthly, or yearly frequency. Weekly supports specific days and times (e.g., every Sunday, Tuesday, Wednesday at 9 AM). Monthly supports a specific day or nth weekday. Yearly supports renewals, holidays, and annual check-ins.

Wait for a specific date — single-step setup.

Previously required two separate actions (Set Event Start Date + Wait). Now it's one step — pick a fixed date or pull from a custom field directly inside the Wait action.

Seconds as a wait unit.

Time delay now supports seconds, enabling rapid-fire sequences with two- or three-second pauses between actions.

Dynamic wait duration.

Wait durations can now be set dynamically using the custom value picker. Pull the duration from a custom field, contact field, or any supported variable instead of hardcoding a value.

Grouped wait types.

Related wait types are now grouped under single cards to reduce clutter. For example, "Wait for a contact action" now includes trigger link clicks and email events in one place. Appointment and service booking waits are similarly unified.

Contextual option reordering.

The card selection screen adapts to context. When Wait follows a Send action (SMS, Email, or WhatsApp), "Wait for the contact to reply" automatically surfaces as the first option.

Wait AI. A new CTA at the top of the Wait action lets users describe their desired wait behavior in natural language. The AI Builder agent generates a configured Wait action card that can be added directly or refined through conversation.

Why this matters

Wait was one of the highest support ticket drivers in Workflows. Two issues accounted for the bulk: users not realizing that waiting until a specific date required a separate "Set Event Start Date" action, and "Contact Reply" being buried under the CRM Events dropdown while Time Delay was the default. The new single-step date setup and intent-based card layout with contextual reordering directly eliminate both pain points.