Wait Action: Major Revamp | Clixio Changelog
The Wait action has been completely redesigned with a new intent-based user interface, 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 select their intent first, followed by configuration—eliminating the need to search through nested dropdowns for options such as “Wait for a contact reply.”
You can now set up recurring waits with weekly, monthly, or yearly frequency. Weekly supports specific days and times (e.g., every Sunday, Tuesday, and Wednesday at 9 AM). Monthly allows selection of a specific day or nth weekday, while yearly supports renewals, holidays, and annual check-ins.
Wait For a Specific Date — Single-Step Setup
What previously required two separate actions (Set Event Start Date + Wait) is now simplified to one step: choose a fixed date or select from a custom field directly within the Wait action.
The time delay now supports seconds, enabling rapid sequences with pauses of two or three seconds between actions.
Wait durations can now be set dynamically using the custom value picker. You can fetch the duration from a custom field, contact field, or any supported variable instead of hardcoding a specific value.
Related wait types are now grouped under single cards to reduce clutter. For instance, “Wait for a contact action” now includes trigger link clicks and email events together. Appointment and service booking waits are similarly consolidated.
Contextual Option Reordering
The card selection screen adjusts based on context. When Wait follows a Send action (SMS, Email, or WhatsApp), “Wait for the contact to reply” automatically appears as the first option.
Wait AI
A new call-to-action (CTA) at the top of the Wait action allows users to describe their desired wait behaviour in natural language. The AI Builder agent generates a configured Wait action card that can be added directly or refined through conversation.
Wait was one of the leading causes of support tickets in Workflows. Two main issues were responsible: users were unaware that waiting until a specific date required a separate “Set Event Start Date” action, and “Contact Reply” was buried within the CRM Events dropdown while Time Delay was the default. The new single-step date setup and the intent-based card layout with contextual reordering effectively resolve both of these issues.