30888: Campaign vetting rejection - Age Gate Not Present / Not Acceptable

Twilio rejected your campaign because you indicated that it includes age-gated content, but the website or opt-in flow submitted for review does not include an acceptable age gate. During A2P 10DLC review, Twilio checks the campaign details you submit, including how end users opt in and whether age-gated content is identified correctly.

• The website URL in your campaign submission does not show an age gate before users can access age-restricted content.
• The opt-in flow does not verify age before a user enrolls in messaging.
• The age verification method is not acceptable, such as a simple yes or no prompt.
• The submission says the campaign includes age-gated content, but the website, opt-in flow, or supporting materials do not clearly demonstrate the age gate.

• Add a robust age gate to your website or opt-in flow before users can access age-restricted content or opt in to messages.
• Use an age verification method that can demonstrate the required minimum age, such as collecting a full date of birth or using a third-party age verification service.
• Update your campaign submission so the message flow clearly explains where age verification happens and how it works.
• Resubmit the campaign after you update the age gate information.

• Programmable Messaging and A2P 10DLC
• Troubleshooting and rectifying A2P Campaigns
• A2P 10DLC Campaign Approval Best Practices