Error code
30458: Toll Free verification rejection - Disallowed: SHAFT - Tobacco / Vape
Not eligible for resubmission. Stated by: Twilio error page for this code.
What this error means
Tobacco, vape or e-cigarette messaging, not supported on toll-free regardless of age gating.
Causes, most likely first
- Business description or use case indicates tobacco/vape/e-cig.
- Website, samples or opt-in data caused SHAFT classification.
- Reliance on age gating, which doesn't rescue this category.
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
Remove tobacco/vape/e-cig traffic from the toll-free use case. If the rejection is wrong, contact Support with a clear business explanation. Check the verification record: if edit_allowed is true, correct and resubmit before edit_expiration, but content/policy rejections are not eligible.
Timing and resubmission
Only resubmittable if edit_allowed is true and the classification was wrong. Otherwise ineligible.
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.