30929: Campaign rejected: Emergency alert notifications are not a permitted use case
MESSAGING, PHONE NUMBERS
ERROR
You receive this error when your A2P 10DLC campaign submission describes emergency alert notifications in a way carriers do not accept for the campaign type you registered. In A2P 10DLC, emergency messaging is handled as the EMERGENCY special use case and can require additional carrier review. If your traffic is not true public safety or health emergency messaging, register the campaign under the correct business use case and remove emergency alert language from your campaign details and sample messages.
- Your campaign description says you will send emergency or public safety alerts.
- Your sample messages include emergency language such as evacuation notices, severe weather warnings, AMBER alerts, or similar public safety notifications.
- The selected campaign use case does not match the traffic you plan to send.
- Your use case may qualify only as the
EMERGENCYspecial use case, which requires additional review and is not interchangeable with standard campaign types. - Your campaign uses emergency wording for messages that are actually business notifications such as account updates, fraud alerts, or service notices.
- If your messages are not true emergency notifications, update the campaign to the business use case that matches your traffic, such as
SECURITY_ALERT,ACCOUNT_NOTIFICATION, orPUBLIC_SERVICE_ANNOUNCEMENT. - Rewrite the campaign description and sample messages so they clearly reflect the actual purpose of the messaging and do not describe emergency alerting if that is not your use case.
- If your traffic is legitimate public safety or health emergency messaging, review the requirements for the
EMERGENCYspecial use case and complete any required approval steps before resubmitting. - Make sure your campaign description, message flow, and sample messages are consistent with each other and with the selected use case.
- If you are sending one-time passcodes only, consider using Twilio Verify instead of registering that traffic under a different A2P 10DLC use case.