Wait Action Major Upgrade: Recurring Waits, Smarter Setup, and a Better HighLevel Workflow Experience

As much as shiny new features get the spotlight, some of the biggest wins in HighLevel come from improving the things people use every single day.

That is exactly what happened with the Wait action.

This update is a major revamp of one of the most important pieces inside HighLevel workflows and automations. It tackles two long-standing pain points at once: making Wait easier to configure and finally bringing recurring schedules into the experience. If you have ever built automations and thought, “There has to be a cleaner way to do this,” this upgrade is for you.

The new Wait action introduces a cleaner user experience, support for recurring waits, dynamic wait durations using custom values, and even AI-powered setup to help configure the action faster. It is one of those changes that immediately makes workflow building feel less clunky and a lot more intuitive.

Why this upgrade matters

The Wait action is not some minor utility sitting off to the side. In a CRM and marketing automation platform like GoHighLevel, timing controls are foundational. They determine when contacts move forward, when actions fire, and how automation behaves over time.

That means when the Wait action is confusing, limited, or hard to set up, it creates friction across a huge part of the platform.

This revamp matters for a few simple reasons:

• Wait has historically been a major source of support tickets.
• Recurring schedules have been one of the most requested workflow items.
• The previous setup flow made some common use cases feel harder than they should have been.
• Automation builders need timing options that match real business processes, not awkward workarounds.

Instead of forcing users to wrestle with dropdowns, edge cases, and loop-heavy workarounds, HighLevel has redesigned the experience around intent. In other words, the platform now starts with a simple question: What are you trying to do?

A new Wait action UX built around intent

One of the best parts of this update is the new setup experience.

The old dropdown-based interface is gone. In its place is a cleaner card selection UI that makes the Wait action much easier to understand at a glance. Instead of digging through options and translating technical labels into your actual goal, you are presented with clearer paths based on the type of wait you want to create.

That shift sounds small, but it is a big deal in practice.

When you configure a Wait now, the experience is much more intuitive. You are essentially choosing the kind of timing behavior you need, such as:

• Wait for a period of time
• Wait until a specific date
• Wait on a recurring schedule

This is a smarter way to approach workflow configuration. It reduces guesswork and helps you move faster, especially when building automations for agencies, client accounts, or complex SaaS operations where clarity matters.

For teams managing a lot of campaigns, that kind of cleanup is not cosmetic. It directly improves speed, implementation consistency, and confidence when building.

Recurring waits are finally here

The headline feature in this update is the arrival of recurring schedule waits.

This has been one of the most requested workflow enhancements, and it is easy to see why. A huge number of automation use cases are not based on a one-time wait. They are based on regular, repeating timing patterns.

Now users can create recurring waits on schedules like:

• Weekly
• Monthly
• Yearly

You can configure waits to repeat on patterns such as:

• Every Sunday
• Every Tuesday
• A specific day of the month
• The nth weekday of a month

That opens up a much more natural way to build repeat-based automations inside HighLevel workflows.

Why recurring waits are so useful

Before this update, setting up recurring timing often meant creating awkward logic to imitate repetition. You might have had to wait until a very specific date, trigger an action, and then loop the contact back through the workflow to start the cycle again.

Technically, you could get there. Practically, it was messy.

This upgrade removes that friction by allowing the recurrence to be defined directly inside the Wait action itself. That means fewer hacks, fewer loops, and fewer chances for something to break or become hard to maintain later.

For agencies and businesses running repeatable operations, that is a big win.

Recurring waits can help support workflows for:

• Weekly reminders
• Monthly follow-up sequences
• Annual check-in automations
• Scheduled internal processes
• Repeating campaign actions tied to calendar patterns

The key point is not just that recurring waits exist. It is that they now exist in a way that feels native and easy to use.

Specific date waits are still supported

Recurring schedules are new, but HighLevel did not strip out the core wait options people already depend on.

You can still configure the Wait action for a specific date, which remains essential for one-time timing events inside workflows.

This matters for any automation that needs to hold until a known calendar date instead of repeating on a schedule. A specific date wait is still the right tool when the goal is to pause until a one-time event or a defined deadline.

The update improves how this option is organized and accessed by grouping wait types more logically. That means the feature is still there, but it is now easier to find and configure in the broader Wait experience.

Wait for a fixed duration, down to seconds

The classic “wait for a period of time” option is also still part of the upgraded experience.

Users can continue setting waits based on a fixed amount of time, including a certain number of seconds. That may sound basic, but it is an important part of building precise automations.

Sometimes you do not need a fancy schedule. You just need a workflow to pause for a defined duration and then move forward.

That kind of control is useful across all sorts of marketing automation and CRM processes, especially when timing between actions matters.

Dynamic wait durations using custom values

Another standout part of this upgrade is support for dynamic wait durations.

Instead of hardcoding the wait length, you can now have the Wait action use a custom value. In other words, the duration itself can be driven dynamically based on the value available in the workflow.

This is a really powerful step forward because it gives automations more flexibility without requiring separate workflow branches for every timing variation.

Dynamic waits help bring more personalization and adaptability into automation design. Rather than forcing every contact or process through the exact same timeline, the wait period can be based on data already available in the system.

For anyone focused on HighLevel agency setup and scaling, this kind of flexibility is especially helpful. It makes workflows more reusable and easier to adapt across multiple accounts or use cases.

It also reduces manual complexity. When timing can be set dynamically, you can often simplify workflow architecture and avoid building multiple copies of the same logic just to support different wait lengths.

AI-powered setup makes workflow building faster

One of the more exciting additions in this release is the new AI setup assistance for the Wait action.

Instead of manually figuring out every configuration detail on your own, you can describe what you want to accomplish and let AI help walk you to the right setup.

That is a smart addition for a feature that has historically created confusion.

If the challenge with Wait has been translating intent into configuration, AI directly addresses that gap. You can tell the system what kind of timing behavior you want, and it helps guide you toward the correct implementation.

This does two important things:

• It lowers the learning curve for newer users building automations in GoHighLevel.
• It speeds up workflow creation for experienced users who just want to get the job done faster.

AI is most useful when it removes friction from common tasks, and this is a great example of that principle in action. It is not AI for the sake of AI. It is AI being applied to a real workflow problem that people encounter all the time.

A cleaner grouping of wait types

Another subtle but valuable improvement is how the different wait options have been grouped together.

Good workflow design is not only about what features exist. It is also about whether those features are organized in a way that makes sense when you are building under real-world conditions.

By grouping wait types more clearly, HighLevel reduces the mental load involved in configuration. You spend less time hunting for the right setup path and more time actually building useful automations.

That kind of usability improvement often gets overlooked, but it has a direct effect on:

• Build speed
• Error reduction
• Team training
• Workflow maintainability
• Overall confidence inside the platform

For agencies managing multiple client systems, clean UX matters. For business owners running their own CRM and marketing automation, it matters too. Better organization means less friction for everyone.

How this helps agencies and automation builders

If you work inside GHL every day, this update is more than just a nice interface refresh. It affects how efficiently you can build and maintain systems.

Here is where the impact shows up most clearly.

1. Fewer workaround-heavy workflows

Recurring schedules remove the need for some of the awkward looping logic that used to be required for repeated timing patterns. Simpler workflows are easier to troubleshoot, easier to hand off, and easier to scale.

2. Faster implementation

The new intent-based cards and AI assistance make setup faster. When your team is creating lots of automations, even small time savings per build add up quickly.

3. Better consistency across accounts

A clearer Wait action means it is easier to standardize how automations are built. That is especially useful in agency environments where multiple people may be working across multiple sub-accounts.

4. More flexible automation logic

Dynamic wait durations allow workflows to adapt without bloating them with extra branches or duplicate sequences. That makes systems more elegant and easier to manage long term.

5. Lower friction for adoption

When a feature is easier to understand, more people actually use it well. That helps teams unlock more value from HighLevel workflows without relying as heavily on support or advanced internal knowledge.

What makes this one of the more meaningful workflow updates

There is something especially satisfying about seeing a platform revisit a critical function and improve it based on real customer feedback.

This is not just feature expansion. It is product maturity.

The Wait action was already an essential part of building automations. The problem was that some common use cases were harder than they needed to be, and some desired behaviors were missing altogether. This update addresses both.

It improves the foundation of workflow automation in a practical way:

• Cleaner configuration
• Better discoverability
• Recurring schedule support
• Dynamic duration support
• AI guidance during setup

That combination makes this one of the more meaningful quality-of-life upgrades for anyone serious about using HighLevel as an operating system for agency systems, marketing automation, and CRM workflows.

Best ways to explore the updated Wait action

If you are already using HighLevel, the best thing to do is open your workflows and test the new Wait action directly.

Pay special attention to these areas:

• How the new card-based selection changes your setup flow
• Whether recurring schedules can replace older loop-based logic
• Where dynamic wait durations could simplify existing automations
• How AI can help configure wait behavior more quickly

This is the kind of update that becomes more impressive the moment you use it in a real workflow. If you have older builds that relied on clunky timing setups, this may be a good opportunity to clean them up.

And if you are newer to the platform, this upgrade makes one of the most important workflow actions much easier to learn from the start.

Final thoughts

The biggest platform improvements are often the ones that remove friction from everyday work.

That is what this Wait action revamp does.

By introducing recurring waits, supporting dynamic wait durations, replacing the old setup with a cleaner intent-based UX, and adding AI-powered configuration help, HighLevel has made workflow automation significantly easier to build and manage.

For agencies, business owners, and operators who depend on reliable automation, this is exactly the kind of update that matters. It saves time, reduces complexity, and makes the platform more intuitive where it counts most.

If you are building in GoHighLevel, this is absolutely worth checking out. And if you are evaluating systems for CRM, automation, and scalable agency operations, updates like this show why the platform continues to invest in making the fundamentals better, not just adding surface-level features.

You can also explore the change log and the help documentation inside HighLevel to get the full details on how the upgraded Wait action works.

FAQ

What is new in the HighLevel Wait action?

The Wait action now includes a redesigned user experience, recurring schedule waits, dynamic wait durations using custom values, better grouping of wait types, and AI-powered setup assistance.

Can I create recurring waits in GoHighLevel workflows?

Yes. HighLevel now supports recurring waits on weekly, monthly, and yearly schedules. You can set patterns like every Sunday, every Tuesday, a specific day of the month, or the nth weekday.

What are dynamic wait durations?

Dynamic wait durations allow the Wait action to use a custom value instead of a fixed hardcoded time period. This makes automations more flexible and helps reduce the need for duplicate workflow logic.

Does the Wait action still support specific dates and fixed time delays?

Yes. You can still wait until a specific date or wait for a fixed duration, including a certain number of seconds. Those options remain available inside the upgraded interface.

How does AI help with Wait action setup?

The AI setup option helps users describe what they want the Wait action to do and then guides them toward the right configuration. It is designed to make workflow setup faster and more intuitive.

Why is this update important for agencies using HighLevel?

It reduces workflow complexity, cuts down on workaround-heavy builds, speeds up implementation, and makes it easier to standardize automations across accounts. That is especially valuable for agencies managing multiple clients and scalable systems inside HighLevel.