30880: Campaign vetting rejection - Unknown Error

This error means your A2P 10DLC campaign was rejected during manual vetting, but the review did not return a specific rejection reason you can act on directly. A failed campaign can include more than one error, so review the campaign details for any additional rejection codes that identify a more specific issue.

• The campaign was rejected by an A2P ecosystem vetting party, but no specific rejection category was returned for this error.
• Another issue in the same campaign or in the associated Brand caused the rejection, and a more specific error appears elsewhere in the campaign details.
• The campaign details did not meet A2P 10DLC approval requirements for consistency, consent collection, or sample message quality, but the returned result did not identify which field failed review.

• Review the failed campaign in Console or in the API response and look for any additional error codes. Fix the more specific rejection reasons first if they are present.
• Review the campaign submission against A2P 10DLC approval requirements. Make sure the Brand, website, message flow, use case, and sample messages all describe the same sender and the same messaging program.
• Confirm that the registration includes a working website and a clear explanation of how end users opt in, opt out, and get help. Make sure sample messages reflect the actual traffic you plan to send.
• If the rejection reason is still unclear, contact Twilio Support to investigate. If Support identifies a correctable campaign or Brand issue, update the registration and resubmit it for review. If you believe the rejection was incorrect, ask Support whether an appeal is appropriate.

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