GoHighLevel Wait Steps & Business Hours (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 19 September 2026 · 10 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.
GoHighLevel wait steps are the most misunderstood part of the Workflow builder, and they are why a perfectly good nurture sequence ends up texting a plumbing lead at 3:04am on a Sunday. The Wait action is not a delay — it is a scheduler with day restrictions, hour windows, timezone logic and fallback branches.
Most Australian agencies I audit have the delay right and the window blank. That works in testing, because you test during business hours, then breaks the first time a contact enters at 11pm. This guide covers every mode of the HighLevel workflow wait step, how the Advance Window differs from the account-level Time Window, and how timezone choice plays out across our states.
Quick Facts
| Where it lives | Automation → Workflows → add step → search "Wait" |
| Wait modes | Eight: set period, specific date/time, recurring schedule, appointment or booking, contact reply, contact action, conditions met, user reply |
| Day/hour control | Advance Window inside the Wait step: Resume On, Resume Between Hours, Additional Filter |
| Timezone source | Workflow Settings → Timezone: Account or Contact Timezone (account is the fallback) |
| Time Window setting | Pauses communication actions outside the set start/end time and days, resuming at the next slot |
| Scope of Time Window | Communication actions (email, SMS, calls) only — not tags or field updates |
What the Wait action actually does inside a HighLevel workflow
The Wait action holds a contact until a timing rule, event, reply or condition is satisfied, then releases them onward. Everything downstream is frozen while they sit there — which is why a badly configured wait throws no error, it just fires at the wrong hour.
Per the official HighLevel Wait action documentation, the selection screen offers eight plain-language options, not a single delay field.
Name every Wait step. "Wait — 1 Day After Enquiry, Business Hours Only" tells you the intent six months later; "Wait" tells you nothing. Same discipline as a naming convention for your workflow folders.
The wait modes compared
| Wait mode | What it does | When to use it | The trap |
|---|---|---|---|
| A set period of time | Fixed duration in seconds, minutes, hours or days | Standard nurture spacing | No Advance Window: a 2-day wait started at 1am releases at 1am |
| A specific date and time | Holds until an exact date/time, fixed or from a field | Renewals, contract end dates, birthdays | Leaving "if this date has already passed" unset |
| A recurring schedule | Releases at the next weekly, monthly or yearly run | First-of-month statements, weekly check-ins | Not checking the "next 5 recurrences" preview |
| An upcoming appointment or booking | Waits before, at or after an appointment, booking or invoice due date | Reminders 24 and 1 hour out | Appointments already past skip straight through |
| The contact to reply | Holds until the contact responds on a channel | Two-way SMS qualification | Needs a Send action before it; no timeout parks contacts |
| The contact to take an action | Holds until a trigger link click or email event | Proposal-viewed branches | Silent failure if the link was never in the message |
| Specific conditions to be met | Holds until any AND/OR segment evaluates true | Waiting on a payment, field update or tag | Segments are OR'd — one true segment releases them |
| A user to reply | Holds until a team member replies | Response-time SLAs and escalations | Resolves on delivery of the reply, not on send |
How to stop a GoHighLevel workflow texting a lead at 3am
There are two independent controls, and knowing which to reach for is most of the battle. The first lives inside the Wait step: toggle on Advance Window for Resume On (weekdays), Resume Between Hours, and an Additional Filter.
A 10-minute delay entered on a Saturday, with a window of Monday to Friday 9:00am–5:00pm, does not release at 9:10am Monday — the clock resumes inside the window, so the contact continues from 9:00am.
Advance Window is per-step; Time Window is per-workflow. The second control sits in Workflow Settings and is your safety net: enable the Specific Time toggle, set a start time, end time and included days, and any communication action scheduled outside it pauses until the next slot.
Which control to use where
- Advance Window — for one step needing different timing to the rest, such as a Monday-morning-only re-engagement text.
- Time Window — the blanket rule. Set it on every outbound-messaging workflow.
- Both together — the Time Window catches what a step misses, including a fast-path branch that skips the wait entirely.
Note the scope limit: the Time Window governs communication actions — email, SMS, calls — not internal actions like adding a tag. So an internal task or a notification pushed to your own team can still land overnight unless you gate it separately.
Timezone handling: account timezone versus contact timezone
Workflow Settings has one Timezone dropdown, applying to the entire workflow — you cannot set different timezones per step. Account Timezone runs every time-dependent step on the sub-account's timezone. Contact Timezone uses each contact's own, falling back to the account timezone when a record has none.
For an Australian business this matters more than most operators expect, because we run three standard offsets and only some states observe daylight saving.
| Zone | States/territories | Standard offset | Daylight saving |
|---|---|---|---|
| AEST / AEDT | NSW, VIC, ACT, TAS | UTC+10 | Yes — clocks go forward in October |
| AEST | QLD | UTC+10 | No |
| ACST / ACDT | SA | UTC+9:30 | Yes |
| ACST | NT | UTC+9:30 | No |
| AWST | WA | UTC+8 | No |
The consequence: a Sydney account texting Perth contacts at 8:00am lands at 5:00am or 6:00am in WA. Run it the other way and a Perth account's 9:00am send reaches Sydney at 11:00am, or midday once eastern daylight saving starts.
If your list crosses state lines, switch to Contact Timezone and confirm the field is actually populated. It is only as good as your data capture — if your forms do not collect a state or postcode, every contact silently falls back to the account timezone and nothing has changed.
Daylight saving and running workflows
Two documented behaviours matter. Account Timezone changes do not affect contacts already running through a workflow, only new entries. And contacts sitting in a Wait action keep their existing wait if you edit that step.
So when the eastern states shift in October, contacts mid-sequence carry on with the timing they were given. Plan for a week of slightly-off send times rather than retrofitting a fix.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
What Australian rules actually say about message timing
The Spam Act 2003 governs commercial email and SMS around three obligations: consent, accurate sender identification, and a working unsubscribe honoured within five working days. The ACMA's guidance on avoiding spam sets no permitted hours for marketing email or SMS.
Phone calls are a different regime. Under the telemarketing rules the ACMA publishes, calls are permitted Monday to Friday 9am to 8pm and Saturday 9am to 5pm, are not allowed on Sundays, and must not be made on national public holidays:
| Call type | Mon–Fri | Saturday | Sunday |
|---|---|---|---|
| Telemarketing calls | 9am–8pm | 9am–5pm | Not allowed |
| Research calls | 9am–8.30pm | 9am–5pm | 9am–5pm |
Source: ACMA, "Say no to telemarketers", accessed September 2026. This is general information, not legal advice — check your own obligations.
Treat the call window as your floor for everything. If your workflow contains a Call action, those hours are a compliance boundary, not a preference. A Time Window of roughly 9am–6pm weekdays covers it and keeps SMS inside what recipients expect — the real cost of a 3am text being complaints and opt-outs.
How waits interact with re-entry, Stop on Response and drip
Wait steps do not exist in isolation. Four other settings change what a wait actually means in production.
- Allow Re-entry — a contact can re-enter after completing or being removed, but not while still active. Someone parked in a 30-day wait cannot. Appointment- and invoice-based triggers always allow multiple entries regardless.
- Stop on Response — ends the workflow for that one contact when they respond. For Call actions, voicemail detection stops a voicemail being read as a response by default.
- Drip — releases contacts in batches at set intervals rather than all at once. Batch and interval changes only apply to contacts entering after the update.
- Conversation AI — a reply-based Wait and Stop on Response can both fire on the same inbound message; decide which owns the exit.
The combination that catches people most is a long wait plus re-entry disabled. Someone held in a 14-day wait cannot be pulled back in, which quietly breaks your renewal reminder sequence when a customer re-enquires early.
A reply or click that never registers is usually a wiring problem, not a wait problem — check the Send action contained the trigger link you are waiting on, then read the execution history, as our guide to diagnosing failed workflow steps sets out.
Common mistakes to avoid
- Setting a delay but leaving both the Advance Window and Time Window blank — the contact's entry time then decides your send time.
- Assuming the Time Window holds back tags, tasks and internal notifications; it governs communication actions.
- Switching to Contact Timezone without checking the field is populated, so everything silently falls back to the account timezone.
- Leaving "if this date has already passed" unset on date and appointment waits, so backdated records rush through.
- Using a reply-based or condition-based wait with no timeout, parking contacts indefinitely and blocking re-entry.
- Editing a live Wait step and expecting contacts inside it to pick up the new timing — they keep the original wait.
If you want your GoHighLevel workflows rebuilt with proper send windows, timezone handling and compliant call timing, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Where is the Wait action in GoHighLevel?
Go to Automation, open Workflows, then click the plus icon to add a step and search for "Wait". Select it, give the step a descriptive name, then choose what the contact should wait for.
What is the difference between the Advance Window and the workflow Time Window?
The Advance Window sits inside one Wait step and controls which days and hours that step can resume on. The Time Window lives in Workflow Settings and restricts when communication actions across the whole workflow can execute. Use the Time Window as your blanket rule and the Advance Window for exceptions.
Does the Wait action use the contact's timezone or the account's?
Whichever you select in Workflow Settings under Timezone. Account Timezone runs all time-dependent steps on the sub-account's timezone; Contact Timezone uses each contact's own. If a contact has no timezone on their record, HighLevel falls back to the account timezone.
How do I stop a GoHighLevel workflow texting a lead at 3am?
Open Workflow Settings, enable the Time Window with a start time, end time and applicable days, and save. For tighter control, toggle on Advance Window inside the Wait step and set Resume On days plus Resume Between Hours. Do both on any workflow that sends SMS.
What happens to contacts already sitting in a Wait step if I edit the workflow?
Contacts already inside that Wait action keep their existing wait — editing the step does not update the timing for anyone already in it. Changes to steps after the wait do apply as those contacts continue through, including newly added actions.
Can a Wait step wait for a contact to reply?
Yes. Choose "The contact to reply", select the channel, and toggle on a timeout so contacts move forward after a set duration even without a reply. A Send Email or Send SMS action must sit before the wait. A separate "A user to reply" mode covers team response-time SLAs.
Are there legal restrictions on what time I can send marketing SMS in Australia?
The ACMA's spam guidance sets consent, sender identification and unsubscribe obligations under the Spam Act 2003, but publishes no permitted hours for marketing email or SMS. Telemarketing calls are restricted to Monday to Friday 9am to 8pm and Saturday 9am to 5pm, with none on Sundays or national public holidays. General information only — confirm your own obligations.
Does Stop on Response remove a contact who is mid-Wait?
Stop on Response ends the workflow for the contact who responds to a message sent from it, including contacts held in a Wait step. It affects only that contact. With Call actions, voicemail detection prevents a voicemail counting as a response unless you disable it.
Related Articles on HL Growth Partner
Workflow foundations
- Workflow Troubleshooting: Fix Errors
- Manual Actions in Workflows
- Workflow Folders & Naming Conventions
