SMS opt-in language is the consent text a person sees right before they agree to receive your texts. Compliant wording names your business, says what kind of messages they will get, states that frequency varies and that message and data rates may apply, and explains how to reply STOP or HELP.
This guide gives copy-ready SMS opt-in language examples for web forms, chat widgets, keywords, booking forms and in-person sign-ups. It also covers where the text has to sit, the mistakes that get A2P 10DLC campaigns rejected, and how GoHighLevel forms handle consent. It is general information, not legal advice; confirm your final wording with counsel for your situation.
Why does SMS opt-in language matter for A2P approval?
SMS opt-in language matters because carriers review it before your A2P 10DLC campaign is approved. If the consent text on your form is missing the business name, message type, frequency, rates notice or STOP instructions, the campaign is rejected and must be fixed and resubmitted.
When you register a campaign through The Campaign Registry (TCR), you describe how people opt in and provide a link or screenshot of that flow. Carrier vetting teams then compare what you wrote with what a real visitor sees. Wording problems are one of the most common reasons a campaign comes back rejected.
- Carrier review: Twilio, one of the largest US messaging providers, lists “missing or non-compliant consent agreement language in opt-in flow” as its own rejection error.
- Legal exposure: marketing texts sent with an autodialer generally need prior express written consent under the Telephone Consumer Protection Act (TCPA).
If you want the whole registration handled for you, our GoHighLevel A2P 10DLC registration service reviews your opt-in wording before anything is submitted.
What must compliant SMS consent language include?
Compliant SMS consent language includes five elements: the business name, the type of messages, a frequency statement, a “message and data rates may apply” notice, and opt-out and help instructions. CTIA guidelines and HighLevel’s A2P guidance both expect them right next to the consent control.
Sending texts outside GoHighLevel too? A2P Ready keeps a platform-neutral SMS opt-in language guide with wording carriers approve.
| Element | What it tells the person | Example wording |
|---|---|---|
| Business name | Who will text them | “from Acme Plumbing LLC” |
| Message type | What the texts are about | “appointment reminders and service updates” |
| Frequency | How often texts arrive | “Message frequency may vary.” |
| Rates notice | Their carrier may charge | “Message & data rates may apply.” |
| Opt-out and help | How to stop or get support | “Reply STOP to opt out. Text HELP for assistance.” |
The CTIA Messaging Principles and Best Practices (May 2023 edition) add that the call-to-action should make clear the program description, the identity of the sender, any fees, and where to find terms and the privacy policy.
Match the wording to your campaign description
The message type in your checkbox must match the use case you register. If the campaign says “appointment reminders and rescheduling”, a checkbox that only says “updates” or “marketing messages” looks vague to a reviewer. HighLevel’s 2026 A2P guide also asks that the business name match your IRS CP 575 or 147C letter, the same record used for your EIN.
New to GoHighLevel? Try it free for 30 days
HighLevel's standard free trial is 14 days. Through our partner link you get 30 days plus HighLevel's free onboarding bootcamp. Rather have it built for you? Our US team sets up GoHighLevel accounts, websites, funnels and automations.
Partner link: we may earn a commission at no extra cost to you. Disclosure
Should SMS consent be a checkbox or a required field?
SMS consent should be an unchecked, optional checkbox, never a required field and never pre-selected. HighLevel says people must be able to submit a form without agreeing to texts, and marketing and non-marketing consent belong in two separate boxes so people can pick one, both or neither.
- Unchecked by default: the visitor has to take an action to give consent. A pre-checked box is not an opt-in.
- Optional: submitting the form cannot depend on agreeing to marketing texts.
- Two boxes, two purposes: one for marketing messages (offers, promotions) and one for non-marketing messages (reminders, account and service notices).
- Phone field is a separate decision: HighLevel’s guide says the phone number field may be required or optional, as long as the consent boxes stay optional.
SMS opt-in language examples you can adapt
The SMS opt-in language examples below follow the structure HighLevel publishes in its 2026 A2P approval guide and the CTIA call-to-action elements. Replace the bracketed parts with your legal business name and your campaign’s exact use case, and keep each statement beside its own checkbox.
Web form: marketing checkbox
“I consent to receive marketing text messages about special offers, discounts and service updates from [Legal Business Name] at the phone number provided. Message frequency may vary. Message & data rates may apply. Text HELP for assistance, reply STOP to opt out.”
Web form: non-marketing checkbox
“I consent to receive non-marketing text messages from [Legal Business Name] about [appointment reminders, order updates and account notifications]. Message frequency may vary. Message & data rates may apply. Text HELP for assistance, reply STOP to opt out.”
Calendar booking form
“Text me reminders and updates about this appointment from [Legal Business Name]. Message frequency may vary. Message & data rates may apply. Reply STOP to opt out, HELP for help.”
Website chat widget
Chat consent works the same way: the visitor sees the disclosure and actively agrees before the first text. In GoHighLevel’s pre-built A2P chat widget flow, the consent boxes and disclosure text are generated for you and locked, so you cannot accidentally edit out a required element. Choosing the “Mixed” option creates two independent, unchecked boxes.
Text-to-join keyword
Printed or on-screen call-to-action: “Text JOIN to [your number] to get offers and updates from [Legal Business Name]. Message frequency may vary. Msg & data rates may apply. Reply STOP to cancel, HELP for help. Terms and privacy: [your-domain]/terms.”
In-person or phone sign-up
For a paper form, front desk tablet or phone call, read or show the same five elements and record when and how the person agreed. The CTIA list of valid opt-in methods includes point-of-sale sign-ups and interactive voice response (IVR), as long as the consent is clear and documented.
What should the opt-in confirmation, STOP and HELP replies say?
The opt-in confirmation message is the first text after someone subscribes to recurring messages. Under CTIA guidelines it should name the program, give customer care contact details or HELP instructions, explain how to opt out, state that messages recur and how often, and disclose that charges may apply.
| Message | When it is sent | Example |
|---|---|---|
| Opt-in confirmation | Right after consent, before any other text | “[Business]: You’re subscribed to appointment and service updates. Msg frequency varies. Msg & data rates may apply. Reply HELP for help, STOP to cancel.” |
| HELP reply | Whenever someone texts HELP | “[Business] support: call [phone] or email [address]. Reply STOP to opt out.” |
| STOP reply | Once, after an opt-out | “[Business]: You’ve been unsubscribed and will receive no further messages.” |
- Honor normal language: CTIA says plain requests such as “stop”, “end”, “unsubscribe”, “cancel”, “quit” or “please opt me out” should be acted on, not only the exact keyword.
- Reasonable means: the FCC’s revocation-of-consent rule, in effect since April 11, 2025, lets people revoke consent by any reasonable means and requires honoring the request within 10 business days at most.
Where should opt-in language go on GoHighLevel forms and sites?
Opt-in language should sit directly beside the consent checkbox on every form, survey, quiz, chat widget and booking calendar that collects phone numbers. A terms link alone is not enough; carrier reviewers expect to see the full consent wording at the point where the person agrees.
- At the control: place the full statement next to each checkbox, not in a tooltip, pop-up or collapsed section.
- Footer links: HighLevel’s guide asks for visible Privacy Policy and Terms & Conditions links in the footer of every form, not hidden behind other elements.
- Every entry point: if one landing page has compliant wording and another funnel step does not, the weaker page is the one a reviewer may find.
- Chat and AI agents: if leads first reach a chat bot or GoHighLevel Conversation AI and Voice AI agent, the consent step must still happen before any automated texts start.
Privacy policy and SMS terms that back up the checkbox
Your privacy policy needs a clear statement that mobile information is not shared with third parties or affiliates for marketing or promotional purposes; HighLevel’s guide allows sharing with subcontractors for support services such as customer service. It must not mention buying, selling or sharing leads. Your SMS terms should identify the business, describe the messages, cover frequency, rates, STOP and HELP, note that carriers are not liable for delayed or undelivered messages, and link to the privacy policy.
Common SMS opt-in mistakes that cause rejections
The most common SMS opt-in mistakes are pre-checked or required consent boxes, one combined box for marketing and reminders, wording missing frequency or STOP instructions, and consent text hidden behind a link. Each one tells a carrier reviewer that the person may not have knowingly agreed to your texts.
| If your form has… | Then a reviewer sees… | Fix |
|---|---|---|
| A pre-checked SMS box | No active consent | Leave every consent box unchecked |
| One box for “all messages” | No choice between marketing and non-marketing | Split into two separate boxes |
| Consent required to submit | Consent as a condition of service | Make both boxes optional |
| Generic “updates” wording | Use case that doesn’t match the campaign | Name the real message types |
| Wording only in the terms page | Disclosure not visible at opt-in | Show the full statement by the box |
| Different business name than the EIN record | Brand and website mismatch | Use the legal name from the CP 575 or 147C |
Shared consent and purchased lead lists
Consent collected by one business does not carry over to another. The CTIA principles say an opt-in should not be transferable or assignable and should apply only to the sender and campaign it was given for. Rented, sold or shared opt-in lists should not be used, and a privacy policy that mentions selling leads is a red flag in review.
The same rules apply to toll-free numbers
Toll-free numbers go through toll-free verification instead of A2P 10DLC, but reviewers ask for the same kind of opt-in proof and consent wording. Our guide to toll-free verification in GoHighLevel explains how that review differs.
How do you prove consent if a carrier or customer asks?
You prove SMS consent by keeping a record of who agreed, when, how and to what. CTIA lists what to retain: a timestamp, the consent medium, the exact language and action shown, the campaign, the IP address where available, the phone number and the identity of the person who agreed.
- Keep the exact text: store the consent statement as it appeared on the date of opt-in, not today’s version.
- Keep opt-outs too: CTIA expects senders to retain opt-out requests so a former subscriber is never texted again.
In GoHighLevel, form submissions and their consent fields are saved on the contact record, which gives you a starting point.
Does opt-in wording affect email and calling too?
SMS opt-in language covers text messages only, but the same consent mindset protects email and calling. LC-Email sending still depends on DKIM, SPF and DMARC records being correct, and calls made with AI voices are treated as artificial voice calls under the TCPA, so they need consent as well.
- Email: collect clear email consent and authenticate your sending domain; consent wording alone will not fix a missing DKIM or DMARC record.
- Calls: if you plan outbound calls with Voice AI, state that in your consent wording rather than assuming the SMS box covers it.
- Missed-call text-back: a reply to someone who just called you is responsive, but if you later add them to recurring texts, get consent first. See how our missed-call text-back and speed-to-lead setup fits inside these rules.
A2P campaign rejected over opt-in wording?
An A2P campaign rejected for opt-in language usually needs three fixes together: the consent wording, the form setup and the campaign description, so all three tell the same story. Changing one and resubmitting can lead to another rejection and another wait.
Our A2P 10DLC registration service starts with a check of your forms, privacy policy, terms and campaign text, then submits once it is consistent. The service is a $50 flat charge; carrier fees of about $22 to $64 one-time and $1.50 to $10 per month per campaign are passed through, and prep takes 24 to 48 hours. If the problem is wider, such as old forms, broken automations or numbers texting people without consent, our GoHighLevel sub-account audit and rebuild finds and fixes it. You can compare plans on our GoHighLevel services pricing page, or read our GoHighLevel A2P rejection help guide first.
Frequently Asked Questions
What is SMS opt-in language?
SMS opt-in language is the consent statement a person sees before agreeing to receive text messages from a business. It names the business, describes the messages, states that frequency varies and message and data rates may apply, and explains how to reply STOP to opt out or HELP for support. Carriers review it during A2P 10DLC registration.
Does SMS consent have to be a checkbox?
A checkbox is the most common method on web forms, and HighLevel’s A2P guidance expects it to be unchecked and optional. Other valid methods include texting a keyword, starting a chat, a point-of-sale sign-up or an IVR phone menu. Whatever the method, the person must actively agree and see the full disclosure first.
Do I need separate checkboxes for marketing and non-marketing texts?
Yes, for GoHighLevel A2P registrations HighLevel asks for two separate checkboxes: one for marketing messages such as offers, and one for non-marketing messages such as appointment reminders. This lets a person choose one, both or neither. A single combined box for all messages is a frequent reason campaigns are rejected.
Can the phone number field be required on my form?
According to HighLevel’s 2026 A2P guide, the phone number field may be required or optional, because collecting a number and agreeing to texts are separate decisions. What must stay optional is the consent checkbox. Submitting the form, booking or buying cannot depend on agreeing to receive marketing text messages.
How fast must I honor a STOP request?
The FCC’s revocation-of-consent rule, effective April 11, 2025, requires honoring an opt-out within a reasonable time and no later than 10 business days after the request. People can revoke by any reasonable means, not just the word STOP. Plain-language requests such as “please stop texting me” count too, so make sure someone acts on them.
Can I text leads I bought from a lead vendor?
Consent given to one business does not transfer to another. The CTIA Messaging Principles say opt-ins should not be transferable or assignable, and rented, sold or shared opt-in lists should not be used. Collect your own consent through your own forms, and confirm with counsel before texting any list you did not build yourself.