How to Use Wait Time in GoHighLevel — Recurring Timer Guide

Running flash sales, webinar countdowns, or product launches without manual timer rebuilds is the dream—and GoHighLevel's recurring wait time feature makes it real. If you're managing client campaigns or scaling your own business, this automation saves hours every month while keeping your sequences running on autopilot.

In this guide, I'll walk you through exactly how to set up custom wait time in GoHighLevel's recurring timer, plus real-world templates you can deploy today. Whether you're running a weekly flash sale or monthly product drop, this feature eliminates the manual work and keeps your campaigns firing on schedule.

Ready to see this in action? Start your free 30-day GoHighLevel trial and get hands-on access to all automation features.

What Is Wait Time in GoHighLevel's Recurring Timer?

The recurring timer wait time feature allows you to automatically pause a countdown timer, reset it, and restart it on a schedule—without touching the automation. Think of it as a timer that doesn't stay frozen after it expires; instead, it takes a break and counts down again.

This is fundamentally different from a standard one-time timer. A regular timer ends once it completes. A recurring timer with wait time:

• Completes its countdown (e.g., 3 days)
• Waits for a set period (e.g., 4 days)
• Automatically resets and starts the cycle again
• Repeats indefinitely until you disable it

This is perfect for recurring campaigns where the same workflow needs to trigger on a schedule. Instead of cloning workflows or rebuilding timers, you set it once and let GoHighLevel handle the repetition.

How to Set Up Custom Wait Time Between Cycles

Setting up a recurring timer with custom wait time takes just a few minutes. Here's the step-by-step process:

Step 1: Access Your Workflow Builder
Log into GoHighLevel, navigate to the CRM, and open the workflow you want to add the recurring timer to. Click the + button to add a new action where you want the timer to trigger.

Step 2: Select the Wait Action
Search for "Wait" in the action menu. You'll see two options:

• Wait — pauses a contact for a set duration
• Recurring Timer — the feature we're using today

Select Recurring Timer.

Step 3: Configure Your Timer Duration
Set the countdown length. For example:

• 3 days for a flash sale
• 7 days for a webinar registration deadline
• 30 days for a product launch

Step 4: Enable Recurring and Set Wait Time
Toggle Recurring: ON. Now you'll see a new field for Wait Time. This is the pause between timer cycles. If your timer is 3 days and you want it to run weekly, set the wait time to 4 days. The timer will:

• Count down 3 days
• Pause 4 days
• Reset and count down 3 days again

Step 5: Add Your Actions After the Timer
Chain actions after the timer completes. These actions trigger every time the timer cycles. For a flash sale, this might be:

• Send an email: "Your flash sale expires in 24 hours"
• Send an SMS reminder
• Update a contact tag

Step 6: Test and Deploy
Add a test contact to your workflow. Verify the timer starts and watch your actions fire. Once confirmed, your automation runs on autopilot.

Understanding Timer Lifecycle and Reset Logic

Understanding how the timer resets is critical for avoiding unwanted repeats or missed campaigns.

The Complete Cycle:

1. Contact enters the recurring timer action
2. Timer runs for your set duration (e.g., 3 days)
3. Actions trigger when the timer completes
4. Wait period starts (e.g., 4 days pause)
5. Timer resets automatically
6. Cycle repeats indefinitely until the contact exits or you disable the timer

A crucial point: the timer doesn't reset just because wait time expires. The entire workflow action resets, which means all downstream actions in that timer action block run again.

If you have 5 actions chained after your recurring timer, all 5 fire every cycle. Use this strategically—you might want different actions on the first cycle versus the second. In those cases, add a filter after the timer to check how many times a contact has cycled through.

This is built into GoHighLevel. Try it free for 30 days →

Real-World Use Cases: Flash Sales, Webinars, and Product Drops

Use Case 1: Weekly Flash Sales
Set a timer to 3 days with 4-day wait time. Every Friday, your timer starts and counts down. At expiration, send "Last 24 hours" emails to your list. The timer pauses, then next Friday resets and runs again for new registrations. Perfect for SaaS companies running consistent weekly promotions.

Use Case 2: Monthly Webinar Countdown
Create a recurring timer set to 30 days with 30-day wait time. Every month, new registrants enter and see a countdown to your webinar. On day 27, send "Your webinar is coming" emails. On day 29, send SMS reminders. The timer resets and the cycle repeats next month.

Use Case 3: Product Drop Automation
If you release products on a fixed schedule (every other Tuesday), use a 14-day timer with 0 days wait time. New customers added to your workflow immediately start the countdown to the next drop. Actions fire 48 hours before launch, then again 24 hours before. The timer resets and repeats.

Use Case 4: Multi-Tier Nurture Sequences
Run a 7-day nurture, wait 7 days, then repeat. On each 7-day cycle, send different educational content or case studies. Contacts continuously cycle through your nurture, staying engaged without manual intervention.

Best Practices for Recurring Timer Configuration

1. Match Your Timer and Wait Time to Your Campaign Cadence
If you run weekly flash sales, your timer should end exactly when you want the sale to close. Your wait time should position the next timer to start right before your next sale begins.

2. Use Contact Filters to Prevent Double-Counting
Add a workflow filter before your recurring timer to check that a contact isn't already in the timer. This prevents contacts from cycling multiple times simultaneously.

3. Tag Contacts When They Complete a Cycle
Add an action that tags contacts after each timer completion (e.g., "Flash Sale Participant - Week 1"). This data helps you track engagement and segment future campaigns.

4. Set Expiration Dates if Needed
For limited-time campaigns, add an exit condition that removes contacts after a set date or number of cycles. Don't let recurring timers run forever unless that's intentional.

5. Monitor Performance in Reporting
Track how many times contacts cycle through. If engagement drops after cycle 2 or 3, adjust your messaging or consider removing low-engagement contacts.

Troubleshooting Common Wait Time Issues

Issue: Timer isn't resetting after wait time expires.
Solution: Confirm the recurring toggle is enabled. Check that the timer has a wait time value greater than 0. If it's still stuck, manually remove a test contact and re-add them to reset the cycle.

Issue: Actions fire multiple times per cycle.
Solution: This happens if duplicate contacts enter the timer. Add a filter before the timer that checks Contact does not have tag [X]. Add an action that applies that tag after the timer completes.

Issue: Wait time isn't long enough; I want more spacing between cycles.
Solution: Increase the wait time value. If your timer is 7 days and you want 10 days between cycles, set wait time to 17 days (7 timer + 10 wait).

Issue: Contacts are cycling too frequently and unsubscribing.
Solution: Increase your wait time or reduce the number of actions that fire per cycle. Consider adding frequency caps to your emails or SMS messages to limit how often individual contacts receive messages.