30913: Campaign rejected: Marketing and informational consent must be separate

Twilio rejects this A2P 10DLC campaign when your opt-in flow combines consent for marketing messages with consent for informational or transactional messages. For marketing use cases, collect explicit written consent that is separate from any non-marketing consent. Consent applies only to the specific campaign and sender.

• A single checkbox, form, or agreement covers both marketing messages and informational or transactional messages.
• Your call to action or signup language groups all message types together and does not give end users a separate choice for marketing messages.
• The campaign uses a Marketing use case, but the opt-in process relies on verbal consent instead of written consent.
• The message_flow does not clearly explain how marketing consent is collected separately, or it does not give reviewers enough evidence to verify the opt-in process.

• Create a separate opt-in control for marketing messages, such as its own unchecked checkbox, signed form section, or text-in keyword flow.
• Keep informational or transactional consent separate from marketing consent. If your campaign uses more than one opt-in method, list every method in message_flow.
• For Marketing campaigns, collect written consent. A website checkbox, signed paper form, or text-in opt-in can satisfy this requirement.
• If your opt-in flow is on a website, include the website URL, terms of service, privacy policy link, message frequency, and the "message and data rates may apply" disclosure.
• If reviewers cannot access the opt-in flow directly, provide a publicly accessible URL with hosted screenshots or other evidence that shows the separate marketing consent flow.
• After you update the opt-in process and campaign details, resubmit the campaign for review.

• Programmable Messaging and A2P 10DLC
• A2P 10DLC required business information
• A2P 10DLC Campaign Approval Best Practices