Error code

30528: Toll Free verification rejection - Disallowed: Non-federally compliant use case

Not eligible for resubmission. Stated by: Twilio error page for this code.

What this error means

Your use case is legal somewhere but not compliant federally across all 50 states.

Causes, most likely first

  1. Content legal in some states but federally prohibited.
  2. Activities violating federal communications law.
  3. Federally regulated products or services without proper licensing.
  4. Use cases explicitly prohibited by federal guidelines.

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

This content is ineligible for resubmission. Messaging use cases must comply with federal regulations applicable in all 50 states; state-level legality isn't sufficient. Future submissions must focus on fully federally compliant use cases.

Timing and resubmission

Explicitly ineligible for resubmission.

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.

Verified against Twilio documentation on 2026-08-10.