Sparkforge A2P 10DLC Opt-In Compliance Requirements
A2P 10DLC approval requires distinct, unchecked consent checkboxes for marketing and non-marketing SMS, opt-in that is not required for form submission, and a privacy policy plus terms of service with specific language and footer links.
A2P 10DLC registration is the U.S. carrier process (Verizon, AT&T, T-Mobile, and others) for verifying who sends SMS and what is being sent. Follow these guidelines to avoid rejections and stay compliant.
Overview
A2P 10DLC registration is a mandatory carrier requirement for businesses sending application-to-person SMS in the U.S. Carriers verify sender legitimacy, consent integrity, and message transparency. Get the opt-in flow right the first time and approval is straightforward.
Opt-in form rules
Whether the phone number field is required or optional in a form, survey, quiz, web chat, or calendar booking, users cannot be forced to agree to SMS messaging in order to submit. The phone field and the consent choice are separate decisions.
Separate marketing and non-marketing consent
Consent checkboxes must be distinct so subscribers can opt into marketing, non-marketing, both, or neither. Use these exact texts:
I consent to receive marketing text messages, about special offers, discounts, and service updates, from [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.
I consent to receive non-marketing text messages from [BUSINESS NAME] about [USE_CASE_FROM_CAMPAIGN_DESCRIPTION]. Message frequency may vary, message & data rates may apply. Text HELP for assistance, reply STOP to opt out.
[BUSINESS NAME] must match what is on the CP 575 or 147C document. If you have an EIN but use a different brand for messaging, follow DBA guidelines.
No pre-checked boxes
Consent checkboxes cannot be pre-selected. The user must take the affirmative action of ticking them.
Consent is always optional
Even if the phone number field is required, ticking the consent boxes must remain optional for form submission. Submitting cannot be conditional on marketing consent. After submission, communicate only on the channels the user actually consented to.
Footer requirements
Every form must include both a Privacy Policy link and a Terms & Conditions link in the footer. They must be clearly visible — not buried under design elements or pop-ups.
Campaign description must match opt-in language
Campaign descriptions submitted for A2P review must align with the consent checkbox language word-for-word in spirit:
- Non-marketing example: if the campaign description includes appointment reminders, order updates, or service notifications, the consent checkbox must reference those exact use cases — not a generic phrase like "non-marketing messages".
- Promotional example: if the campaign description mentions special offers or discounts, the consent checkbox must reference those, not a generic phrase like "marketing messages".
The campaign description must also match the website's actual business niche. A pizza restaurant cannot register an appointment reminder use case — the carriers will reject it.
Privacy Policy essentials
The policy must never mention affiliation, selling, or buying of leads. Contact information in the privacy policy and terms must match the brand registration submission.
Required non-sharing clause
Include this exact language about third-party sharing:
No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. Information sharing to subcontractors in support services, such as customer service, is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
Terms of Service clauses
The Terms of Service must identify the sender, give opt-out and support instructions, disclose frequency, and reference the privacy policy.
Business identity
State the business name and a brief description of the messages users will receive.
Opt-out and support
Cover how users opt out (reply STOP) and request help (reply HELP), with confirmation that opt-outs are honored immediately.
Message frequency and rates
Disclose that message frequency may vary and that message and data rates may apply.
Privacy policy reference
Link or reference the privacy policy directly inside the terms.
Frequently Asked Questions
Can I make the SMS consent checkbox required?
Can I default the consent checkbox to checked?
Why does my campaign description need to match my consent language?
What does the non-sharing clause have to say exactly?
What happens if my privacy policy mentions selling leads?
Was this article helpful?
Thanks for the feedback.