If a GoHighLevel workflow text shows as pending late at night or early in the morning, it's almost certainly being held for quiet hours, not failing. Ready holds the text and sends it by itself when the recipient's sending window opens. Tell your rep not to resend it, because a resend can put two copies in the queue.
This comes up a lot with agencies running follow-up workflows after hours. The status looks alarming, the contact hasn't replied, and the natural move is to click send again. This post explains what's actually happening, how to check, and what to say to your team. It assumes your sub-account's texting runs through Ready, which installs natively into GoHighLevel.
Why the text shows as pending
Quiet hours are based on the recipient's area, not yours. A workflow that fires at 9 PM Pacific is already late evening for a contact in Eastern time and may be outside the window for them. Ready checks the contact's area, and if the send falls outside allowed hours, it holds the text.
Two facts matter for a GoHighLevel sender:
- A one-to-one or workflow text sent from GoHighLevel in quiet hours is held with no six-hour limit.
- It sends itself when the window opens. Nobody has to retry it.
GoHighLevel shows a held text as pending because it hasn't been sent yet. That's the whole story. Nothing is broken, nothing needs a resend, and nothing is charged until the text actually goes out.
What to tell your reps
Put one line in your team's playbook:
- Pending after hours means held for quiet hours, not failed.
- Don't resend it. It will go on its own.
- Check again once the contact's morning window has opened.
Resending is the only real mistake available here. The original is still waiting, so a second copy risks the contact getting the same message twice when the window opens. Our GoHighLevel SMS not sending guide covers the other, genuine failure causes if a text stays pending well into the daytime.
How to tell a hold from a real problem
| What you see | Likely cause | What to do |
|---|---|---|
| Pending, and it's evening or early morning for the contact | Quiet hours hold | Wait, don't resend |
| Pending, and it's midday for the contact | Something else | Check the number, registration status and balance |
| Failed with an error | A genuine refusal | Read the error, then fix the cause |
| Sent, but no reply | Delivered normally | Nothing to fix |
The time that counts is the contact's local time, which can differ from yours by several hours. If you're not sure where a contact is, their area code is the guide Ready uses.
An example, with assumptions
Say a lead fills out a form at 10:30 PM Pacific, and your workflow texts them straight away. The lead's number has an Eastern area code, so it's 1:30 AM for them, well outside a normal sending window. The workflow step runs, GoHighLevel shows the message as pending, and Ready holds it.
Assume the window opens at 8 AM Eastern. The text goes out then, by itself, and your rep sees the status change. If the rep had clicked resend at midnight, the contact might have received the greeting twice at 8 AM. That's the situation the don't-resend rule prevents. The numbers here are an illustration, not a measurement, and the exact window depends on the contact's area.
What quiet hours cover and what they don't
This is a risk reduction measure. Texting outside reasonable hours is one of the things that creates TCPA exposure, so holding the text lowers it. Compliance stays the sender's responsibility, and Ready's hold doesn't make a campaign immune to complaints.
Some other cases behave differently:
- Campaigns, drip campaigns and automations built in Ready wait up to 24 hours for the window.
- A text typed in the Ready dashboard or inbox to one person is scheduled for the recipient's next allowed time, and it shows in the thread. The sender retypes nothing.
- A reply to a contact who texted this account in the last 24 hours goes out at any hour.
- The Auto-reply outside business hours setting skips a reply that would land in quiet hours and never sends it later. If you want an after-hours reply that's sent later, build it as an automation, which is held like any automation text.
For the wider rules about timing across regions, see our post on quiet hours across time zones.
Designing workflows around the window
You can't skip quiet hours, but you can stop being surprised by them.
- Put time-sensitive first touches in the contact's daytime, not at the moment of form submission, when you can.
- For speed-to-lead flows, expect an evening lead's first text to wait until morning, and plan the rep's follow-up around that.
- Don't stack a second workflow step that retries a text "if not delivered in 10 minutes". A held text isn't undelivered in the failure sense, so a retry step creates duplicates.
If you set up the connection, the GHL setup guide covers the basics.
Frequently asked questions
How long will a held workflow text wait?
There's no six-hour limit for a one-to-one or workflow text sent from GoHighLevel. It waits until the window opens and then sends itself.
Will I be charged while it's pending?
A held text is charged only when it sends.
Can I force it out now?
Not through a resend. If the contact texted you in the last 24 hours, a reply goes out at any hour. Otherwise, wait for the window.
Is pending always quiet hours?
No. It's the likely cause in the evening or early morning for the contact. At midday, look for another cause, starting with the number's registration status.
Next step
Add the three-line rule to your agency's playbook and mention it to anyone who works after-hours follow-ups. If a text is still pending the next afternoon, work through the troubleshooting guide linked above.