Error code
30447: Toll Free verification rejection - phone number not provisioned to Twilio
Correctable and resubmittable. Stated by: Twilio error page for this code.
What this error means
You filed verification for a number that isn't (yet) on Twilio.
Causes, most likely first
- Verification submitted before porting to Twilio completed.
- The number simply isn't provisioned to Twilio.
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 porting or hosting is in flight, let it complete. Then delete the rejected verification and submit a new request after the port lands. If it isn't a porting scenario, contact Twilio Support.
Timing and resubmission
Documented path is delete-and-refile, not edit. That is a new submission with a new 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.
Fix it yourself
Send your email and we will send the fix playbook for registration rejections.
Verified against Twilio documentation on 2026-08-10.