GoHighLevel SMS compliance: opt-in, old lists and carrier filtering
Heads up: the trial and plan buttons on this page use my affiliate links. If you sign up through one I get a commission. It doesn't cost you more.
No, you shouldn't text contacts from GoHighLevel who never opted in to texts from that business. Under US law marketing texts need the person's prior express written consent, HighLevel's own LC Phone policy says SMS should only go to opted-in contacts, and carriers filter or block numbers that text people who didn't ask for it.
This is the "am I allowed to text this person" guide: the consent rules in plain English, what counts as opt-in on a HighLevel form, STOP and the FCC's new opt-out rules that start November 25, 2026, how to win back an old list without texting it cold, sending limits, and the businesses HighLevel won't let text at all. It's not legal advice. I run my agency on HighLevel and this is how I read the rules and the docs as of November 19, 2026, so run anything risky past a lawyer.
30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →
Short version
- 01Marketing texts need express written consent: a checkbox or signature that names the business and isn't a condition of buying. A form field with just a phone number isn't it.
- 02If they texted you first, replying is fine. Ongoing reminders need express consent. Promos need written consent.
- 03Consent belongs to one business. Bought, shared or "we had it at my old company" lists don't count, and HighLevel bans them.
- 04Since April 11, 2025, stop, quit, end, revoke, opt out, cancel or unsubscribe all revoke consent, and you have at most 10 business days to honor it. HighLevel blocks some of these words automatically. Build a workflow for the rest.
- 05From November 25, 2026 you can name one opt-out method (reply STOP), as long as every text says so.
- 06Old list? Email it first, ask for a fresh opt-in, and only text the people who say yes.
- 07New LC Phone sub-accounts start at 500 texts a day. There's no legit way around the ramp, and "unlimited SMS" gateways put the account at risk.
The TCPA in plain English: three kinds of consent
The Telephone Consumer Protection Act (TCPA) and the FCC's rules under it (47 CFR 64.1200) treat texts as calls. Automated texts to a cell phone need the person's prior express consent, and texts that advertise or sell need prior express written consent. Carriers enforce their own version through the CTIA's messaging guidelines, which split texts into three buckets. This is how I explain it to a client.
The law has real teeth. A person can sue for $500 per violating text, and a court can triple that if it finds the violation was willful or knowing (47 U.S.C. 227(b)(3)). On a list of a few thousand numbers that adds up fast, which is why I don't treat this as a carrier problem only.
Written consent doesn't mean paper. The FCC's definition allows an electronic signature, so a web form checkbox can count, as long as the wording clearly says this business may send marketing texts to this number and that agreeing isn't a condition of buying anything.
| Type of text | Example | Consent you need |
|---|---|---|
| Conversational | They text the business first, you reply about what they asked | None extra. Their text is the permission for that reply |
| Informational | Appointment reminders, order updates, a welcome text after they gave you their number | Express consent: they gave the number for that purpose |
| Promotional | Offers, discounts, "we're running a promo", reactivation pitches | Express written consent: a checkbox or signature naming the business |
CTIA Messaging Principles and Best Practices (May 2023) and 47 CFR 64.1200, read Nov 19, 2026. Examples are mine. Not legal advice.
What counts as opt-in on a GoHighLevel form
HighLevel's deliverability guide (Sep 4, 2026) says that when the phone field is required, the form needs separate consent checkboxes for marketing and non-marketing texts, never pre-selected and always optional, with privacy policy and terms links in the footer. If the phone field is optional, it says a consent checkbox isn't required. I'd still add one, because the checkbox is your written consent for anything promotional.
The exact checkbox and privacy policy wording HighLevel accepts for A2P is in A2P rejected? Fixes, and the whole registration is in A2P 10DLC registration. I won't repeat it here. The short version: name the business, say what kind of texts, frequency, rates, HELP and STOP.
Two things that don't count. A phone number on a form with no checkbox is a number, not written consent for promos. And consent given to one business doesn't move to another: CTIA says an opt-in "should not be transferable or assignable", and HighLevel's forbidden-categories doc bans purchased and shared consent outright.
Where the consent lives in HighLevel:
- Forms and surveys: the Custom Checkbox element in the Form Builder. The answer is saved on the contact.
- Chat Widget: Chat window > Additional options > Compliance notice & consent. There's a "Pre-check the box by default" option. Leave it off for SMS, because a pre-ticked box is an A2P rejection (30925) and not real consent.
- Calendars: the booking consent checkbox, with wording you can edit.
- Text-in keywords: a Customer Replied workflow with Reply Channel set to SMS and an Exact Match Phrase like JOIN. HighLevel's keyword doc says not to use STOP or HELP as keywords.
- Facebook lead forms, paper and verbal: they can count, but they need the same disclosures, and you need a record. For A2P you also have to describe every method you use.
What time can you send texts?
Federally, no telephone solicitation before 8 a.m. or after 9 p.m. in the recipient's local time (47 CFR 64.1200(c)(1)), and the rule covers marketing texts to cell phones too. Some states set tighter windows or extra rules. Texas is one HighLevel calls out: its SB 140 took effect September 1, 2025, and HighLevel added a Texas SMS Safeguard toggle in the Messaging Compliance settings that blocks texts to Texas recipients or from Texas area codes. Its doc also notes the Texas Secretary of State says businesses texting with prior consent don't need the state's telemarketing registration.
In HighLevel the setting that does the work is in each workflow's Settings: Timezone (pick Contact Timezone) and Time Window (start time, end time, days). Anything scheduled outside the window waits for the next slot. If a contact has no time zone, HighLevel uses the account's, so a client in New York texting a lead in California at 8:05 a.m. their time is 5:05 a.m. for the lead. Set the time zone on import, or keep the window to something like 10 a.m. to 7 p.m.
Drip Mode on bulk actions has its own Process Between hours, and those run on the account's time zone. Same fix: keep the window narrow.
STOP, opt-outs and DND: what HighLevel does and what you have to do
When a contact replies STOP, STOPALL, UNSUBSCRIBE, CANCEL, END or QUIT, HighLevel turns on SMS DND for them and blocks every later text (that's error 21610 in SMS not delivering). Only the contact can undo it by texting START or YES. You can't re-subscribe them yourself, and HighLevel's DND doc says permanent DND only comes off with that reply or proof of opt-in sent to support.
The federal rule is wider than that keyword list. Since April 11, 2025, 47 CFR 64.1200(a)(10) says a reply of "stop," "quit," "end," "revoke," "opt out," "cancel" or "unsubscribe" always revokes consent, and any other reply counts too if a reasonable person would read it as "stop texting me". Revocations have to be honored within 10 business days, and a voicemail or email asking to stop counts as well. You can send one confirmation text with no marketing in it, and it's presumed fine if it goes within five minutes.
HighLevel's 21610 doc doesn't list revoke or opt out, so don't assume they're caught. My fix is a workflow: trigger Customer Replied, Reply Channel SMS, Contains Phrase filters for revoke, opt out, remove me, stop texting and don't text. Actions: DND Contact (SMS, outbound), Remove from Workflow set to all workflows, and an Internal Notification so a human reads it. Turn on Stop on Response in your sales workflows too, so a reply pulls the contact out of the sequence.
The rules change again on November 25, 2026 (table below). Keep "Reply STOP to unsubscribe" in the first text and turn on the periodic re-insert, because from that date that line is how you'd name STOP as your opt-out method. The FCC also opened a new proposal on a one-step "revoke all" option, with comments due November 25 and replies December 28, 2026, so this may move again.
| Rule | Until Nov 24, 2026 | From Nov 25, 2026 |
|---|---|---|
| How people can opt out | Any reasonable way: text, voicemail, email, website | Same, unless you name one method (like reply STOP) and say so in every text |
| Words that always count | stop, quit, end, revoke, opt out, cancel, unsubscribe | Same seven. Showing just one (STOP) in the text is enough, but all seven still work |
| Deadline to honor it | 10 business days at most | 10 business days at most |
| What the opt-out covers | All robocalls and texts from you (the "revoke all" part was delayed) | Marketing opt-out covers all marketing. An informational opt-out can cover only that kind of message |
| Confirmation text | One, no marketing, within 5 minutes to be safe | Confirmation only, no marketing, within 5 minutes to be safe |
47 CFR 64.1200(a)(10) to (12) as in force Nov 19, 2026, and FCC 26-67 (91 FR 67214, Oct 26, 2026, effective Nov 25, 2026). Not legal advice.
Can you text an old list? Run a re-permission campaign
This is the question I get most from people selling database reactivation. In my reactivation case study I said "aged leads are not dead. They're just uncontacted." That's true, but uncontacted isn't the same as opted in. Sort the list before anyone hits send.
- Opted in to texts from this business, recently: you can text them. HighLevel's own rule is to reconfirm opt-in every 18 months because numbers get reassigned.
- Opted in years ago, or you can't find the record: treat them as no consent. Re-permission by email first.
- Past customers with no SMS checkbox: an appointment reminder they asked for is informational. A promo is marketing and needs written consent. Email first.
- Bought, rented, scraped or shared from another company: don't text them at all. HighLevel calls this purchased consent and it's banned.
- Anyone with DND or a past STOP: leave them alone. Filter them out of the Smart List.
The re-permission flow I'd build in HighLevel
Start with a Smart List of contacts with no SMS consent on record, then send an email (from the client's own domain, following CAN-SPAM, which I covered in Prospecting tool review) that says who they are and asks if they want texts about the offer. The button goes to a short HighLevel form with the SMS checkbox, or tells them to text JOIN to the client's number. A form submission or keyword reply fills Consent Source and Opt-in Timestamp and adds them to the SMS sequence. Nobody gets a cold first text.
Then write the first text like a person. In the same case study I said the opener "had to seem human, not like a broadcast", and that the goal is to "remind them who we are" without trying to sell them anything. Name the business, mention how they signed up, ask a question and include STOP. Space the follow-ups out: reviewing an AI-built reactivation workflow, I said "what this missed, is the wait step" and that I'd "wait probably 24 hours or a day and then send the second SMS." The money is made in the follow-ups, but only to people who said yes.
How many texts can you send a day? The ramp and Drip Mode
Every LC Phone sub-account created since February 1, 2024 follows an 8-level ramp that starts on the day its first text is delivered, not the signup date. To move up a level, the sub-account has to send its full daily limit within 24 hours. Then SMS pauses for 24 hours and the next level opens. HighLevel's ramp doc says one-to-one texts and Missed Call Text Back count toward the limit, and one-to-one texts can't go out during that pause either.
You'll find the current level under Settings > Phone System > Messaging > Messaging Limit. Some locations are on the separate Messaging Limits model, where an agency that's been on HighLevel 3+ months and isn't in a trial can raise the limit itself. Either way, HighLevel says to scale volume gradually, because a sudden jump is exactly what carrier filters look for.
For a big list, use Drip Mode on the bulk action: Contacts > select the Smart List > Send SMS > Drip Mode, then set Batch Quantity, Repeat After, Send On days and Process Between hours. A few hundred a day to people who opted in will beat 5,000 in one go every time. If a client's account has already been paused for high opt-outs or filtering, the thresholds and how to get sending back are in SMS not delivering.
| Level | Texts per 24 hours |
|---|---|
| 1 | 500 |
| 2 | 750 |
| 3 | 1,000 |
| 4 | 1,500 |
| 5 | 2,000 |
| 6 | 3,500 |
| 7 | 5,000 |
| 8 | 5,000+ |
LC Phone Messaging Policy (updated Oct 13, 2026) and Messaging Ramp Progress Card (Sep 9, 2026), read Nov 19, 2026.
Why "unlimited SMS" gateways and cold blasts put the account at risk
Every few weeks someone on the HighLevel subreddit asks for an "unlimited SMS" provider or how to send a cold text blast to a giant list. I don't teach either. The TCPA doesn't care which gateway sent a text, so a cold text is still a cold text, and if a client wants to reach people who never opted in, the honest options are a person dialing by hand, CAN-SPAM-compliant email, or ads that send people to an opt-in form.
On top of the law, here is what HighLevel's and the carriers' own rules say:
- Grey routes: CTIA's guidelines say business texts shouldn't go through routes carriers haven't authorized for business messaging. Cheap "unlimited" gateways often work by sending business traffic as if it were a person texting.
- Snowshoeing: spreading the same message across lots of numbers to dodge filters is banned in HighLevel's LC Phone policy and in CTIA's guidelines.
- Purchased consent: HighLevel's policy says consent "can't be bought, sold, or exchanged". A cold list has none.
- Carrier fines: HighLevel's forbidden-categories doc lists T-Mobile Severity-0 fines of $2,000 per incident for Tier 1 violations, $1,000 for Tier 2 and $500 for Tier 3, which includes lead generation without proper consent. That's on top of number suspension or filtering.
- The platform: HighLevel reserves the right to suspend or remove access for anyone breaking the policy, sometimes with limited notice for serious violations.
Businesses and topics HighLevel won't let you text
Some clients can't use SMS for promotions no matter how good their consent is. HighLevel's Prohibited and Restricted SMS/MMS Message Categories doc (updated Sep 3, 2026) covers the US and Canada on every number type, local, toll free and short code, and it says picking an A2P use case doesn't make banned content OK. Check this list before you sell a texting build.
One catch: HighLevel's LC Phone Messaging Policy (Oct 13, 2026) still says messages must not relate to alcohol, firearms, gambling, tobacco or adult content. With the two docs out of step, ask HighLevel support before you build texting for a bar, a vape shop or a gun store. HighLevel suggests email for some of these businesses, but the doc is clear the channel switch doesn't remove the legal rules.
| Status | Categories |
|---|---|
| Prohibited | Phishing, smishing and fraud |
| Prohibited | Cannabis, CBD, prescription drugs and other controlled substances, even where legal |
| Prohibited | Gambling: sports betting, casinos, paid sweepstakes, lottery promos, fantasy sports |
| Prohibited | Sexual content and hate content |
| Prohibited | High-risk financial: payday loans, third-party auto and mortgage loans, student debt relief, crypto investment |
| Prohibited | Third-party debt collection (a business texting its own customer about their own balance may be OK) |
| Prohibited | Get-rich-quick schemes and third-party lead generation |
| Restricted | Alcohol, tobacco and vaping (age gating required), firearms. Case by case at campaign registration |
From HighLevel help article 48001219617 (modified Sep 3, 2026), read Nov 19, 2026.
Carrier filtering in one minute
Carriers decide what gets delivered, and they judge you on two numbers: how many people reply STOP and how many of your texts they filter as spam (error 30007). HighLevel watches both per sub-account over a rolling 7 days, once it has sent at least 500 texts. Under the safeguards rolling out since November 10, 2026, a sub-account gets a warning at a 4% opt-out rate or 15% filtering, and bulk and workflow texts pause for 12 hours at 6% or 25%. One-to-one replies in Conversations keep working.
Almost all of it comes back to consent. Texting people who didn't ask is what drives both rates up. The full error code list, the 30007 content rules (no bit.ly, no ALL CAPS, sender name and STOP every 30 days) and how to appeal a filter are in SMS not delivering. If you're deciding between LC Phone and your own Twilio, the same rules apply on both: Phone system.
Pre-send checklist
I'd run this before any bulk send or new SMS workflow in a client account.
| Check | Where in HighLevel | Pass if |
|---|---|---|
| Consent for this kind of text | Contact record, Consent Source field, form submission | Written consent for promos, express consent for reminders, from this business |
| Consent is recent | Opt-in Timestamp field | Within 18 months, or re-permission done |
| No bought or shared contacts | Smart List filter on source | Every contact came from the client's own forms, calls or customers |
| DND and opt-outs excluded | Smart List filter: DND SMS is off | No one who sent STOP or similar |
| Sender name and STOP in the text | Settings > Phone System > Messaging | Both toggles on, periodic re-insert on |
| Business isn't on the banned list | Help article 48001219617 | Not prohibited, restricted ones cleared with support |
| A2P approved and number linked | Settings > Phone System > Trust Center | Campaign approved and the sending number attached |
| Send window | Workflow Settings > Timezone and Time Window, or Drip Mode hours | Contact time zone, between 8 a.m. and 9 p.m. their time at the widest |
| Volume | Settings > Phone System > Messaging > Messaging Limit | Under today's limit, or dripped |
| Opt-out catcher live | Customer Replied workflow with DND action | Non-standard opt-outs set DND and notify a human |
| Error alerts | Messaging Error - SMS workflow | Someone hears about 30007 and 30034 the same day |
Built from 47 CFR 64.1200, CTIA's guidelines and HighLevel's help docs, read Nov 19, 2026. Not legal advice.
Set up a sub-account for compliant texting
- 01
Turn on sender ID and opt-out language
Settings > Phone System > Messaging. Switch on "Make SMS compliant by adding an opt-out message" and "Make SMS compliant by adding sender information", put the client's business name in the sender text, and turn on periodic opt-out every 30 days. New sub-accounts have it on by default. Older ones don't.
- 02
Fix the opt-in on every form
Two separate SMS checkboxes (marketing and non-marketing), unticked, optional, with the business name, message type, frequency, "message and data rates may apply", HELP and STOP. Privacy and terms links in the footer. The exact wording HighLevel accepts is in A2P rejected? Fixes.
- 03
Record where consent came from
Create contact fields like Consent Source and Opt-in Timestamp (HighLevel's DND doc suggests both) and fill them from the form submission workflow. That's your proof if a contact or support asks.
- 04
Set the time zone and send window
In each workflow that texts, open Settings, set Timezone to Contact Timezone and add a Time Window. Contacts without a time zone fall back to the account's, so fill it in on import.
- 05
Catch opt-outs HighLevel doesn't
Build a Customer Replied workflow on SMS that turns on SMS DND and notifies the owner when a reply contains words like revoke, opt out, remove me or stop texting. Details below.
- 06
Check the sending limit before any bulk send
Settings > Phone System > Messaging > Messaging Limit shows the ramp level. Use Drip Mode for anything bigger than today's limit.
30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →
Other ways to start
My bonuses come with every one of these.
Best if you're new and want live help setting up
30-day trial + a free live setup bootcamp
Same 30-day trial, plus a seat in HighLevel's free live bootcamp: a click-by-click Zoom class with a HighLevel coach and small breakout rooms, every weekday at 11am CT, 60 minutes max. You set up your account during the class instead of figuring it out alone. HighLevel says you can launch in 48 minutes.
Best if you're not sure which plan you need
Compare all 3 plans first
HighLevel's own pricing page with Starter ($97), Unlimited ($297) and Founder ($497) side by side, monthly and yearly. Every plan there has a 14-day free trial.
Best if you'll resell HighLevel as your own software
Go straight to the $497 Founder plan
HighLevel's top plan (it used to be called Agency Pro), with a 14-day free trial. Everything in Unlimited plus SaaS mode, rebilling with your own markup, Founders Club and HighLevel Partner Network access. For when you're ready to resell the software, not for day one.
FAQ
Can I text contacts without opt-in in GoHighLevel?
You shouldn't. Marketing texts need prior express written consent under the TCPA rules, HighLevel's LC Phone policy says SMS should only go to opted-in contacts, and cold texts drive the opt-out and filtering rates that get a sub-account paused. The exception is replying to someone who texted you first. This isn't legal advice.
Can I text old leads or past customers?
Only the ones with SMS consent from that business on record, ideally reconfirmed in the last 18 months. Email the rest first and ask them to opt in with a form checkbox or a keyword like JOIN, then text the ones who say yes.
Is a phone number on a form enough consent to text?
Not for marketing. Promotional texts need written consent, which in practice is an unticked, optional checkbox that names the business and the kind of texts, with STOP and HELP instructions. A required phone field alone isn't that.
Does GoHighLevel handle STOP automatically?
Yes for STOP, STOPALL, UNSUBSCRIBE, CANCEL, END and QUIT, which turn on SMS DND for the contact. The FCC's list also includes revoke and opt out, plus any reply a reasonable person would read as stop, so add a Customer Replied workflow that sets DND for those.
What changes in the FCC's opt-out rules on November 25, 2026?
Senders can name one opt-out method, like replying STOP, as long as every text discloses it, and then they don't have to process opt-outs made other ways. All seven standard words still count, and the 10 business day deadline stays.
How many texts can a new GoHighLevel sub-account send?
On LC Phone the ramp starts at 500 texts in 24 hours and climbs through 750, 1,000, 1,500, 2,000, 3,500 and 5,000 to 5,000+. You move up by sending the full limit in a day, then waiting through a 24 hour pause.
What businesses can't send SMS through GoHighLevel?
HighLevel prohibits cannabis and CBD, gambling, sexual content, payday and other high-risk loans, third-party debt collection, get-rich-quick offers and third-party lead generation. Alcohol, tobacco, vaping and firearms are restricted and need case-by-case approval.
Sources / last checked Nov 19, 2026
- FCC rules (eCFR). 47 CFR 64.1200, Delivery restrictions, ecfr.gov (version as of Nov 17, 2026): (a)(1) to (a)(2) consent, (a)(10) to (a)(12) revocation, (c)(1) 8 a.m. to 9 p.m., (e) texts to wireless numbers, (f)(9) prior express written consent. Read Nov 19, 2026.
- Federal Register. Strengthening the Ability of Consumers To Stop Robocalls, 89 FR 82518 (Oct 11, 2024; revocation rules effective Apr 11, 2025) and Enhancing the Ability of Consumers To Control the Robocalls, FCC 26-67, 91 FR 67214 (Oct 26, 2026, effective Nov 25, 2026), plus the proposed rule at 91 FR 67239. Read Nov 19, 2026. fcc.gov itself returned an access error, so the FCC is cited through these.
- TCPA statute. 47 U.S.C. 227(b)(3), private right of action, law.cornell.edu/uscode/text/47/227, read Nov 19, 2026.
- CTIA. Messaging Principles and Best Practices (May 2023), api.ctia.org, read Nov 19, 2026: consent types, one opt-in per sender, opt-out handling, shared lists, grey routes and snowshoeing.
- HighLevel help docs: compliance. Prohibited and Restricted SMS/MMS Message Categories (Sep 3, 2026), LC Phone Messaging Policy (Oct 13, 2026), SMS Compliance Settings (Sep 1, 2026), Auto-Updating Opt-Out & Sender Info (Oct 6, 2026), Texas SMS Safeguard (Aug 18, 2026) and How to Get Customer Consent (Sep 1, 2026), read Nov 19, 2026.
- HighLevel help docs: opt-outs, limits and workflows. Error 21610 (Sep 8, 2026), Do Not Disturb (Sep 28, 2026), Messaging Ramp Progress Card (Sep 9, 2026), How to Increase Messaging Limits (Sep 11, 2026), LC Phone messaging quality monitoring (Nov 10, 2026), SMS Deliverability Best Practices (Sep 4, 2026), Error 30007 (Jul 23, 2026), Workflow Settings (Oct 14, 2026), Drip Mode for Bulk Actions and SMS keyword campaigns (Oct 15, 2026), read Nov 19, 2026.
- My videos. My database reactivation case study (Jun 8, 2026), quoted only and not embedded, my review of an AI-built reactivation workflow (Jul 2026), quoted only, and my Feb 2026 video for the follow-ups line. I don't have a video on SMS compliance, so there's no video on this page.

Author
Hamza Baig / Hamza Automates
Founder, Hexona Systems
I run Hexona Systems on GoHighLevel. HighLevel gave it the SaaSpreneur Platinum award in 2024 and Diamond in 2025 and 2026, and I spoke at their LevelUp event in 2026. Hexona powers 1,000+ agencies, we've served 1,500+ businesses, and I've taught 45,000+ students. Everything on this hub is something I use myself or have shown on camera.
- Platinum SaaSpreneur
- 2024
- Diamond SaaSpreneur
- 2025, 2026
- LevelUp speaker
- 2026
- YouTube subscribers, Oct 2026
- 34,200