A lead fills out your Facebook lead form at 11:45 PM on a Saturday, and your workflow blithely fires an automated SMS 45 seconds later. You just woke up a prospect, risked a TCPA violation fine, and practically guaranteed an angry “STOP” reply.
I’ve seen this exact mistake cost agencies clients and get numbers carrier-blocked. Today, we’re building a bulletproof quiet hours setup in GoHighLevel workflows. We’ll configure execution windows, handle multi-state timezones properly, and make sure internal sales alerts still fire instantly even when customer-facing texts sit on hold until morning.
The Two Ways HighLevel Handles Sending Windows
HighLevel gives you two mechanisms to control when messages go out: Workflow-Level Execution Windows and Wait Steps with Time Windows. Mixing these up is the single most common reason automations fail silently.
- Workflow Settings Window: Freezes the entire workflow trigger until the window opens. If an event fires outside the window, nothing runs—no tags are applied, no pipeline stages update, and no internal alerts reach your team.
- Action-Level Wait Steps: Lets the workflow trigger instantly to update your CRM, ping your staff, and dispatch webhooks, but holds the outbound SMS in a queue until acceptable daytime hours.
For 95% of lead gen funnels, you should never use global workflow-level windows for SMS compliance. When a hot lead lands at 10:00 PM, you want your CRM updated, a pipeline deal created, and an internal Slack or email alert sent to on-call reps immediately. You only want to hold the outbound text message.
Setting Up a Granular Wait Step for SMS Quiet Hours
To hold messages without stalling your entire automation, drop an isolated queue directly ahead of your SMS action in the builder.
- Open your workflow in HighLevel and add your trigger (e.g., Form Submitted, Inbound Webhook, or Tag Added).
- Add all immediate CRM actions first: Add Contact Tag, Create Opportunity, or Internal Notification.
- Click the + icon and pick Wait.
- Switch the Wait For dropdown from Time Delay to Time Window.
- Choose your operational days (Monday through Sunday or weekdays only).
- Set the window start time (e.g.,
08:30 AM) and end time (e.g.,08:00 PM). - Under Window based on, select Contact Timezone (with fallback to Account Timezone).
- Directly below this Wait step, place your Send SMS action.
When a contact enters this workflow at 1:00 AM, HighLevel handles tags and pipeline updates instantly. The moment execution hits the Wait action, the contact pauses until 8:30 AM in their local timezone before sending the text.
If you haven’t registered your numbers yet, make sure you finish your A2P 10DLC campaign registration in GoHighLevel first, or carriers will reject these queued messages no matter what time they fire.
The Contact Timezone Trap: How to Prevent False Deliveries
Federal TCPA rules mandate quiet hours between 9:00 PM and 8:00 AM in the recipient’s local timezone, per FCC Telemarketing and Robocalls guidelines. State mini-TCPA laws in Florida, Oklahoma, and Washington restrict this further to 8:00 PM to 8:00 AM.
The trap in GoHighLevel is that brand-new contacts often don’t have a defined timezone. If a lead opts in from Los Angeles (Pacific Time), but your sub-account is set to New York (Eastern Time), HighLevel defaults to your account timezone unless the contact record specifically has one set.
If your window opens at 8:00 AM Eastern, that Los Angeles lead gets their “morning” text at 5:00 AM Pacific. That is an outright compliance violation.
How HighLevel Resolves Contact Timezones
HighLevel evaluates timezone priority in this exact order:
- Explicit
timezonefield on the contact record (usually set via booking calendars or API). - Area code lookup from the contact’s primary phone number.
- Sub-account location timezone configured in Settings > Business Profile.
If your lead forms only capture an email and name without a phone area code, or if the lead uses an out-of-state VoIP number, the area code resolution fails. If you’re running multi-region campaigns, check our guide on how to fix GoHighLevel calendar timezone mismatches to keep contact profiles synced properly.
Testing Your Sending Window Using Custom Webhook Payloads
Don’t wait until 10:00 PM to test if your workflow pauses an SMS. You can simulate an inbound payload with an explicit timezone parameter to verify the execution path right away.
Here’s a sample JSON payload you can post to a HighLevel Inbound Webhook trigger to test Pacific Time behavior against an Eastern Time sub-account:
{ "first_name": "QuietHour", "last_name": "Tester", "phone": "+12065550199", "email": "test.quiet.hours@example.com", "timezone": "America/Los_Angeles", "custom_fields": { "lead_source": "webhook_test" }
}After sending this into your test workflow, open the Execution Logs tab. Look for the Wait step. You should see a status badge marked Waiting with the scheduled execution timestamp converted to your local time.
If the timing looks wrong, check the contact details view to confirm the America/Los_Angeles string parsed cleanly into the contact record.
The 8:01 AM Delivery Spike: Fixing Carrier Filtering and Rate Limits
When you hold 200 leads overnight, a nasty side effect happens at 8:30 AM: all 200 messages blast out in the exact same second. This sudden burst triggers automated spam filters at major carriers.
The CTIA Messaging Principles and Best Practices specifically flag sudden, un-ramped volume spikes from a single 10DLC number as a major trigger for carrier filtering.
When downstream carriers see 200 identical texts leave a single standard number in under 3 seconds, your delivery rates will crater. If you run into delivery drops, see our guide on how to fix GoHighLevel LC Phone SMS carrier filtering.
How to Stagger the Morning Queue
To keep from tripping carrier rate limits when your morning window opens, add a simple random delay after your quiet hours window:
- Directly after the Wait for Window step, insert another Wait action.
- Select Time Delay.
- Set a random duration between 1 to 10 minutes, or split leads using an If/Else condition on Contact ID (odd vs. even) to break up the dispatch queue.
Building an Out-of-Hours Autoresponder with If/Else Logic
Sometimes you don’t want to sit in silence until morning. For emergency niches like 24/7 plumbing or roofing, prospects need to know right away whether someone is on call. In that scenario, use branching logic instead of a simple hold step.
Set up an If/Else branch using Date/Time > Current Time conditions:
// Logical branching model inside GoHighLevel
if (CurrentHour >= 8 && CurrentHour < 20) { // Day Branch: Send standard follow-up sendSMS("Thanks for reaching out! Our team is reviewing your request now.");
} else { // After-Hours Branch: Set expectations sendSMS("Thanks for contacting us. Our office is closed for the night, but you are first in line when we open at 8:00 AM.");
}Notice the after-hours copy clearly explains why they received an immediate text and sets expectations for regular business hours. Always keep your compliance language intact. Check our guide on how to automate SMS opt-out and DND compliance in GoHighLevel to ensure your opt-out handling stays airtight.
Frequently Asked Questions
What happens if a lead replies while paused in a quiet hours wait step?
If a contact texts back while sitting in a quiet hours Wait step, they’ll stay in that step unless you turned on Stop on Response in the Workflow Settings. If Stop on Response is enabled, the workflow cancels for that contact immediately, preventing the scheduled morning message from sending.
Does the Workflow execution window affect appointment reminder workflows?
Yes. If you add a global Workflow Settings window to an appointment reminder workflow, reminders for 7:00 AM appointments get held until 8:30 AM—delivering after the meeting has already started. Never use global execution windows on time-sensitive reminder campaigns.
How do state mini-TCPA laws impact quiet hour settings?
States like Florida, Oklahoma, and Washington enforce an 8:00 PM to 8:00 AM blackout window instead of the federal 9:00 PM rule. If you run campaigns across the US, set your workflow Wait windows strictly between 8:30 AM and 7:45 PM contact local time to stay safely within every state’s boundaries.
To streamline this across all your sub-accounts, check out our guide on how to use Custom Values in GoHighLevel for dynamic workflows to manage sending hours and legal disclaimers globally.
