30925: Campaign rejected: Opt-in must be unchecked by default; active consent required

Your A2P 10DLC campaign was rejected because the opt-in flow you provided does not show clear, affirmative consent for messaging. For website-based opt-in, the consumer must actively choose to receive messages. A checkbox or similar consent control cannot be pre-selected by default.

• Your web form does not include a separate consent control for the consumer to actively opt in to messaging.
• The messaging consent checkbox or toggle is pre-selected, so the consumer is opted in by default.
• Your form only captures acceptance of general Terms of Service or Privacy Policy and does not capture separate consent to receive messages.
• Your submission does not provide enough publicly accessible evidence of the opt-in flow, such as a live page or hosted screenshots.

• Add a separate checkbox or similar control for messaging consent. Leave it unchecked by default and require the consumer to actively select it.
• Keep messaging consent separate from acceptance of general Terms of Service or Privacy Policy.
• If you collect opt-in on a website, include the website URL in your campaign message_flow and make sure the site includes publicly accessible Terms of Service and Privacy Policy links.
• Make sure your privacy policy includes the required messaging disclosures, including non-sharing of mobile numbers, message frequency, and a "message and data rates may apply" disclosure.
• If the opt-in flow is behind a login or is not yet public, host screenshots of the form and consent language on a publicly accessible URL and submit that evidence when you resubmit the campaign.

Run through this list before submitting or resubmitting your campaign:

• message_flow names every opt-in method used for this campaign (website, keyword, paper form, verbal, QR code, or other mechanism).
• message_flow includes a link to your privacy policy and a link to your terms and conditions.
• Your privacy policy states that mobile numbers are not shared with third parties, includes message frequency, and includes a "message and data rates may apply" disclosure.
• If opt-in happens on a website, the URL is publicly accessible. If it is not public, you have provided a URL with hosted screenshots of the full consent flow.
• If end users opt in by texting a keyword, opt_in_keywords and opt_in_message are populated. The opt_in_message includes the brand name, confirmation of enrollment, message frequency, and opt-out instructions.
• If the campaign uses multiple opt-in paths, all paths are described in the same message_flow field.
• Sample messages match the declared use case, identify the brand by name, and include opt-out language.
• The messaging consent checkbox or toggle is unchecked by default — the consumer must actively select it.
• Messaging consent is captured by a separate control, not bundled with general Terms of Service or Privacy Policy acceptance.

Edit the rejected campaign rather than deleting and recreating it. Resubmitting triggers a fresh review by The Campaign Registry (TCR).

• Vetting fee: A vetting fee is assessed only once per campaign. Resubmitting the same campaign does not incur a new fee.
• Timeline: Sole Proprietor campaigns are typically approved or rejected within hours to days. Standard campaigns go through several layers of vetting and can take up to several weeks.
• Check status: Monitor your campaign status in Console > Messaging > Regulatory Compliance > Campaigns, or fetch the UsAppToPerson resource and check the campaign_status field.

To resubmit in Console, go to Messaging > Regulatory Compliance > Campaigns, click the failed campaign, then click Edit Campaign to correct the fields and resubmit. To resubmit via API, update the campaign resource with corrected field values. See Troubleshooting and rectifying A2P Campaigns for detailed instructions.

• A2P 10DLC - Gather the Required Business Information
• message_flow field reference
• Troubleshooting and rectifying A2P Campaigns