Error code

30929: Campaign rejected: Emergency alert notifications are not a permitted use case

Eligible for resubmission. Stated by: GHL 155000007572.

What this error means

You described emergency alerting under a campaign type that doesn't allow it.

Causes, most likely first

  1. Description says you'll send emergency or public safety alerts.
  2. Samples include evacuation notices, severe weather warnings, AMBER alerts or similar.
  3. Selected use case doesn't match the traffic.
  4. The use case may qualify only as the EMERGENCY special use case, which needs additional review and isn't interchangeable.
  5. Emergency wording used for what are actually business notifications, account updates, fraud alerts, service notices.

How to fix it

If your numbers are managed by a platform

If your numbers sit inside a reseller platform, for example LeadConnector numbers inside GoHighLevel, you do not have access to the Twilio Console, and the interface shows the rejection without the code. Ask that platform's support team for the Twilio rejection error code, in writing, before you change anything. You can also read it yourself from your browser, which is faster: see how to get the code.

The substance of the fix is yours to make: the business details, the website, and the opt-in flow described in the Twilio path all belong to you, not to the platform. Make those changes first, confirm they are live, then ask support to resubmit. A resubmission filed before the underlying facts change will fail again on the same reason.

If you own the Twilio account

If the messages aren't true emergency notifications, switch to the matching business use case, SECURITY_ALERT, ACCOUNT_NOTIFICATION, or PUBLIC_SERVICE_ANNOUNCEMENT, and rewrite description and samples so they don't describe emergency alerting. If the traffic genuinely is public safety or health emergency messaging, review the EMERGENCY special use case requirements and complete the approval steps first. If you only send one-time passcodes, consider Twilio Verify instead.

Timing and resubmission

Edit and resubmit with the correct use case; the EMERGENCY special use case requires separate approval with no published SLA.

Twilio publishes an indicative review timeline for campaigns: Sole Proprietor campaigns are typically approved or rejected within hours to days, and Standard campaigns go through several layers of vetting and can take up to several weeks. Twilio also states that the vetting fee is assessed only once per campaign, so editing and resubmitting the same campaign does not incur a new fee, while deleting and recreating it does.

Two ways forward

Have it handled for you

A2P registration is handled for you on Growth at $597/mo and on Scale at $1,197/mo. Registration, resubmissions, and the compliance work behind them are included.

See Growth and Scale

Fix it yourself

Send your email and we will send the fix playbook for registration rejections.

Related errors

Verified against Twilio documentation on 2026-08-10.