Error code

30032: Toll-Free Number Has Not Been Verified

What this error means

Your toll-free number tried to text a US/Canada mobile before its toll-free verification was approved, so Twilio blocked it.

Causes, most likely first

  1. TFV was never submitted, number sits in Restricted / Not verified.
  2. TFV is submitted and still in review (Pending), since 31 Jan 2024 pending traffic is blocked too, not throttled.
  3. TFV was rejected, so the number never reached approved state.

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

Console → Phone Numbers → Manage → Active numbers → select the number → Regulatory Information tab to read status. If unverified, submit TFV in Console or via the Messaging Compliance API. If rejected and still editable, correct and resubmit before edit_expiration.

Timing and resubmission

Twilio sets the TFV edit window to 7 days from the initial request (edit_expiration). Miss it and you cannot edit, you must delete and file a fresh submission, which restarts the review clock.

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.