The opt-in page is evidence, not decoration. It should show the exact choice a recipient sees and connect that choice to the same business, message types, and policies described in the campaign.
Leave SMS consent optional
Provider rejection guidance says a user must be able to complete the main service action without being forced into messaging consent. A checkbox should be unchecked by default and separate from required service terms.
Separate message choices
When a campaign sends both informational and promotional messages, provider guidance calls for separate consent choices. A recipient can choose one, the other, both, or neither when messaging is not required for the main service.
Put the program details at consent
The consent language should identify the brand and message types, state the message frequency, disclose that message and data rates may apply, and explain how to use STOP and HELP. The campaign message flow should describe every opt-in method.
Keep policies public
Privacy and terms URLs should be publicly accessible and reviewable. Twilio guidance calls for privacy language stating that mobile information and opt-in consent are not shared with third parties or affiliates for marketing or promotional purposes.
- Link privacy and terms beside the consent language.
- Keep the pages on the business website or attached kit domain.
- Do not require login or a file download for review.
- Make the sender identity agree across consent, policies, and campaign copy.
Work through the filing
- 01
Publish the business identity
Show the legal or responsible business name and contact information on the public site.
- 02
Build the optional consent choices
Leave boxes unchecked and separate informational from promotional consent when both message types apply.
- 03
Add complete disclosures
Name the brand and message types, frequency, rates notice, STOP instruction, HELP instruction, and policy links.
- 04
Test every proof URL
Open contact, privacy, and terms pages without login and confirm they match the campaign description.
Questions
Can SMS consent be required to submit a contact form?
Provider rejection guidance says messaging consent cannot be required as a condition of the main service, account, or purchase. Keep the messaging choice separate and optional.
Do marketing and informational messages need separate choices?
When both message types apply, provider guidance calls for independent consent choices so the recipient can choose each category.
What must the privacy policy say about mobile data?
Twilio guidance requires a clear statement that mobile information and opt-in consent are not shared with third parties or affiliates for marketing or promotional purposes.
How does the kit help?
Each kit publishes contact, privacy, and terms pages from the same client facts and includes their URLs in the platform copy.
Provider sources
- Twilio: Gather the Required Business Information
- Twilio error 30923: Consent cannot be required
- Twilio error 30924: Missing consent language
- Twilio error 30932: Privacy policy data-sharing disclosure
- HighLevel: A2P Campaign Registration Step-by-Step Guide
Source links point to HighLevel and Twilio provider documentation. Check the current version before filing.