21720: A2P Use Case is Invalid

The us_app_to_person_usecase value in your A2P 10DLC Campaign request is not valid for the Messaging Service and brand you are using. When you create a Usa2p resource, submit one of the supported use case code values returned by the A2P 10DLC Usecases subresource.

• The request includes a us_app_to_person_usecase value that does not match a supported use case code.
• The selected use case is not available for your brand type. Standard, Low-Volume Standard, Sole Proprietor, and Special campaigns support different use case values.
• The request uses a display name or free-form label instead of the exact API code value, such as ACCOUNT_NOTIFICATION, LOW_VOLUME, or SOLE_PROPRIETOR where applicable.
• The campaign details do not align with the intended use case. Campaign description and sample messages must match the selected us_app_to_person_usecase.

• Retrieve the allowed use cases for the Messaging Service and brand, then resubmit the request with one returned code value exactly as provided.
• Confirm your brand type before choosing a use case. Standard brands can use values such as 2FA, ACCOUNT_NOTIFICATION, CUSTOMER_CARE, and MARKETING. Low-Volume Standard brands can use LOW_VOLUME. Sole Proprietor brands must use SOLE_PROPRIETOR.
• Update your campaign registration details so the description, opt-in flow, and sample messages clearly match the selected use case.
• If you are unsure which use case fits your traffic, review the A2P 10DLC onboarding guidance and choose the campaign type that matches the messages you actually plan to send.

• A2P 10DLC Usecases subresource
• A2P 10DLC: Gather the Required Business Information
• Programmable Messaging and A2P 10DLC