Skip to content
A2PCheck

Twilio Error 30032: Toll-Free Number Has Not Been Verified

Error 30032 is the toll-free equivalent of the 10DLC registration wall: unverified toll-free numbers can't message US/Canada mobiles.

Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.

What Twilio error 30032 means

You tried to send from a toll-free number to a US or Canadian mobile subscriber, but the number hasn't been verified. As of January 31, 2024, traffic from toll-free numbers in Restricted or Pending status is blocked.

Official Twilio name: 30032: Toll-Free Number Has Not Been Verified A2P 10DLC-specific

Why error 30032 happens

The toll-free number was never submitted for verification (so it's Restricted), a verification request is still Pending review, or a prior verification request was rejected. Toll-free verification is the toll-free analog to A2P 10DLC campaign registration.

How to fix error 30032

  1. Check the number's verification status in Console under Phone Numbers > Manage > Active numbers.
  2. Submit a toll-free verification request through the Console or the Messaging Compliance API.
  3. If a request was rejected but is still editable, correct the submission within the seven-day edit window.
  4. If it's ineligible for resubmission, update your business information and submit a fresh verification request.
  5. Until verified, route the traffic through a registered A2P 10DLC long code instead.

Related error codes

Official reference

For the authoritative definition and any changes to this code, see the Twilioerror catalog. A2PCheck is an independent pre-scan layer for the campaign packet you submit — it can't change carrier behavior.

Twilio error 30032 documentation

Frequently asked questions

Can I send from a toll-free number while verification is pending?

No. Since January 31, 2024, toll-free numbers in Restricted or Pending status are blocked to US/Canada mobiles and return 30032. You must reach Verified status first, or send from a registered 10DLC number in the meantime.

Free — no signup required

Catch the campaign issue behind this error before you resend

Many of these errors trace back to an unregistered, mis-scoped, or non-compliant A2P 10DLC campaign. Paste your campaign details for a free readiness scan — no signup.

Independent pre-submission check
No Twilio or TCR submission
Use campaign metadata, not customer PII

Use representative templates and public URLs only. Do not paste real customer phone numbers, customer records, API keys, or internal/signed URLs.

New here? Try a realistic example

Load a complete, carrier-friendly campaign to scan in one click — then tweak it for your own.

01

Campaign Info

Basic details about your messaging campaign.

0 characters — Too short — describe who opts in, what you send, and how often.

02

Sample Messages

Provide at least 2 example messages you'll send.

STOP foundHELP foundchecked across your keywords & messages
03

Opt-In / Message Flow

How users consent to receive your messages.

Consent evidence readiness

Describe where and how subscribers consent — name the opt-in location and the consent language they agree to.

  • Name the opt-in location (web form, checkout, keyword, QR code, paper form, etc.).
  • Spell out the consent language — what the subscriber explicitly agrees to.
  • State the message frequency (e.g. recurring, varies, msgs/month).
  • Include a "Message and data rates may apply" disclosure.
  • Link a privacy policy describing how you handle subscriber data.
  • Clarify that consent isn't a condition of purchase, where that applies.
  • Capture and retain opt-in evidence (timestamp, source URL, exact consent text/screenshot) for each subscriber.

Guidance only — consent requirements can vary by use case and jurisdiction.

or sign up to run a Full scan
Scan my campaign for this issueAll A2P 10DLC error codes