30912: Campaign rejected: A2P 10DLC is for application-to-person messaging only

Your A2P 10DLC campaign was rejected because the campaign details describe personal or peer-to-peer messaging instead of business messaging sent from an application to a person. A2P 10DLC campaigns must represent a valid application-driven business use case.

• The campaign description suggests personal communication between individuals instead of messages sent by a business application to end users.
• The campaign description does not clearly explain who the sender is, who the recipients are, and why the recipients are receiving messages.
• The selected use case, message flow, or sample messages do not match a valid A2P business campaign. Campaign details must align with the registered use case and the actual messages you plan to send.

• Update the campaign description so it clearly explains the business or application sending the messages, the intended recipients, and the reason each recipient receives them. Make sure the description aligns with the selected us_app_to_person_usecase.
• Describe the application layer in your submission. Explain what system, software, or workflow triggers the messages, because A2P messaging must be sent from an application rather than from one individual to another.
• Review and revise your message_flow and message_samples so they match the actual business use case and consent flow for the campaign. If the campaign failed review in Console, edit the failed campaign details and resubmit after correcting the flagged fields.
• If your traffic is truly personal or peer-to-peer, do not submit it as an A2P 10DLC campaign. Use A2P 10DLC only for business messaging sent from an application to end users.

• Programmable Messaging and A2P 10DLC
• A2P 10DLC - Gather the Required Business Information
• A2P 10DLC Campaign Approval Best Practices