Trace almost any 10DLC or toll-free rejection back to its root and you tend to land in the same place: the reviewer couldn’t confirm how consumers agreed to be texted. The opt-in is the load-bearing part of a messaging program. Get it right and most of the review takes care of itself; get it wrong and nothing downstream saves you.
What consent means to a carrier
Consent, in the A2P sense, is explicit, documented, and specific to messaging. A consumer has to take a clear affirmative action to receive texts from your program — not agree to a general terms-of-service that happens to mention SMS somewhere. If the agreement to be messaged isn’t distinct and demonstrable, it doesn’t count.
The disclosures reviewers look for
At the point of opt-in, a compliant flow makes all of the following visible:
- The program or brand name, so it’s clear who will be texting.
- The type of messages and their frequency — “recurring,” “varies,” or a specific cadence.
- “Message and data rates may apply.”
- STOP to opt out and HELP for help.
- Links to your Terms and your Privacy Policy, near the opt-in itself.
Where the disclosures go
Placement matters as much as presence. The disclosures belong at the moment of consent — beside the form field or submit button, not buried a click away or surfaced only after signup. Whatever the channel — web form, keyword, point of sale, or verbal — the consumer should see what they’re agreeing to at the moment they agree.
The privacy-policy trap
A surprising number of campaigns are undone by their own privacy policy. If your policy says you share or sell consumer data and doesn’t explicitly carve out messaging opt-in and consent information, a reviewer reads that as a contradiction and rejects. The fix is a clear line stating that mobile information collected for messaging isn’t shared with third parties for their marketing — and that opt-in data stays with the program.
Document it, and keep it live
Reviewers check your live opt-in against what you submitted. Screenshot the flow, keep the URL working, and make sure the page still says what your registration says it does. A description that no longer matches the live page is a rejection waiting to happen — and the same discipline carries straight over to toll-free verification.
Frequently asked questions
Do I need double opt-in?
Not universally, but a confirmed opt-in is the strongest evidence of consent and is expected for some use cases. When in doubt, confirm.
Can I message an existing list?
Only with prior express consent you can actually demonstrate for messaging specifically. A list gathered for email or general marketing doesn’t automatically carry SMS consent.
Is the opt-in different for toll-free?
The consent standard is the same; the submission path differs. The disclosures and documentation you build for 10DLC carry over directly to toll-free verification.
Disclaimer: This article is general information, not legal or compliance advice. Carrier rules, CTIA guidelines, and 10DLC and toll-free requirements change often and are enforced at the discretion of the carriers and their vetting partners. Tychron makes no warranty as to its accuracy or completeness and accepts no liability for actions taken in reliance on it — confirm current requirements with the relevant authorities and your own counsel before acting.