30900: Campaign rejection - The campaign use case is ineligible for registration.

This error occurs when the A2P 10DLC campaign use case you submitted isn't eligible for the selected brand. You can only register a campaign with use cases that are available for that brand, and some use cases require additional carrier approval before registration can complete.

• The submitted use case isn't supported for the selected brand. Use the A2P 10DLC Usecases subresource to retrieve valid use cases for a specific brand.
• The selected use case isn't supported by one or more carriers, or it requires additional carrier review before approval.
• The brand isn't qualified for the selected campaign use case.
• The selected campaign falls outside the allowed sub-use case bounds for the brand.
• A public, for-profit brand hasn't completed Authentication+, which is required before you can create a new campaign.

• Retrieve the available A2P 10DLC use cases for the brand and submit one of the returned code values.
• Review your campaign description, message flow, sample messages, and opt-in and opt-out details. Make sure they match the selected us_app_to_person_usecase.
• If the selected use case requires carrier review, wait for that review to complete or choose a different use case that accurately reflects your messaging program.
• If you are registering a public, for-profit brand, update the brand_contact_email to use a company domain, complete Authentication+, and retry campaign registration. If you didn't receive the verification email, resend it from the Console or retrigger it with the 2FA verification resource after a failed verification.
• If the campaign should be eligible and registration still fails, contact Support with your brand SID, Messaging Service SID, and campaign details.

• Programmable Messaging and A2P 10DLC
• A2P 10DLC - Usecases subresource
• Troubleshooting A2P 10DLC Registrations