If GoHighLevel texts are not going out through Ready, the cause is almost always one of six things: registration, an opt-out, quiet hours, a landline, the local presence tag, or billing. Check them in that order, because each takes under a minute.
Start with the failed text
When Ready refuses a text, it tells GoHighLevel, and the failed message in the contact's conversation shows the reason in plain words. For example, "This number is on your do-not-call list" points at your Ban list. "This number is on our block list, so it can't be texted" means Ready's own system-wide list, which you cannot edit, so email support@tryready.com. "The number you are sending from is not active yet" points at the number or its registration. Read that line first; the six checks below are for when it does not settle it.
Work from one failed contact, not from the whole campaign. A single contact tells you which rule fired. If the same text goes to a different contact, the problem is the contact. If it fails for everyone, the problem is the account.
1. Registration status
An account can send up to 500 texts a month before it registers, at its normal per-text rate. After that, it has to register. Unregistered traffic also gets carrier-filtered, so a text can leave Ready and never arrive.
Open the Registration page in Ready and check where the brand and campaign are. Most approvals take 2 to 7 days. If you bought a number before registering, you send on Ready's shared registration at the same per-text rate while your own is in review. Our GoHighLevel 10DLC guide walks through the filing.
2. Opt-out or ban list
Ready honors STOP, UNSUBSCRIBE and clear phrases like "please stop texting me" and "take me off". A contact who opted out is refused up front, and you are not charged. Numbers on your Ban list are refused the same way.
A STOP always blocks that number in the sub-account that received it. Whether it also blocks your other sub-accounts is decided by Ready for every account, not by a setting you can change; check GET /v1/opt-outs/:phone for the answer on one number. Opt-outs from another tool do not carry over by themselves, which matters right after a migration.
3. Quiet hours
Ready enforces quiet hours by the recipient's area. What happens next depends on the kind of text:
| Kind of text | Inside quiet hours |
|---|---|
| Campaign, drip or automation | Waits up to 24 hours for the window |
| 1:1 or inbox text | Held and sent when the window opens; GoHighLevel shows it as pending |
| Reply to a contact who texted in the last 24 hours | Goes out at any hour |
A held text sends itself when the window opens, so don't send it again. A held text is charged only when it sends. An automation's after-hours reply is held like any automation text, while the Auto-reply outside business hours setting skips a reply that would land in quiet hours and does not send it later.
4. Landline numbers
A number Ready's own sends have already seen as a landline is refused up front on every account, with no charge. Landline validation, switched on in Settings under Compliance, catches more by looking numbers up at send time. It is off by default and adds a per-segment screening charge. A landline cannot receive a text, so the fix is to find a mobile number for the contact, not to retry.
5. The local presence tag
In GoHighLevel, the #from:local# tag picks the number closest to the contact's area code, and #from:rotate# spreads new contacts across numbers in the local area-code group. A contact keeps the number it already texts with.
Check three things: local presence is switched on in Ready, the account has a number near that area code, and the tag is spelled exactly. Local presence picks among numbers you already own, so it will not buy one. Every number sits on your registered campaign, so a number that is not attached to one will not send. See which tag to use.
6. Billing and balance
Billing is prepaid credits, and a card on file and a number of the account's own are required to send. Texts through a connected GoHighLevel sub-account are billed from the first one. If the balance is empty, texts will not go out. Top up, then resend.
Quick triage table
| Symptom | Check first |
|---|---|
| Nothing sends from anyone | Balance, then registration |
| One contact fails | Opt-out, Ban list, landline |
| Fails only at night | Quiet hours |
| Fails only with a tag | Local presence setup |
| Sends but not delivered | Registration and filtering |
If all six check out
Look at the message itself. Content that carriers flag can be filtered even on a registered route. Our post on why business texts are not sending groups causes by error type. For setup from scratch, the GHL SMS setup guide is the reference. If you are still stuck, email support@tryready.com with one failed contact's number and the time you sent.
Frequently asked questions
Why did my GoHighLevel text send but not arrive?
Most often the registration is not approved or the content got filtered. Check the Registration page before anything else.
Will a held text send by itself?
Campaign, drip and automation texts wait for the quiet-hours window, up to 24 hours. A 1:1 text sent from GoHighLevel is held and sends itself when the window opens, so do not send it again.
Am I charged for a refused text?
No. Opt-outs, ban-list numbers and known landlines are refused up front without a charge.
Are test texts through GHL charged?
Yes. Every text is billed from the first one, including texts sent through a connected GoHighLevel sub-account.