Toll-Free Verification vs A2P 10DLC (and Error 30032)

Updated

Short answer: They are separate programs for different kinds of numbers. A2P 10DLC registration, a brand plus a campaign, covers business texts sent from ordinary 10-digit US numbers, while toll-free numbers go through toll-free verification instead. Error 30032 means a toll-free number tried to text a US or Canadian mobile before its verification was approved.

Two programs for two kinds of numbers

Twilio says: "There are three options for SMS and MMS messaging in the US and Canada: long codes, Toll-Free numbers, and short code numbers. Each one has somewhat different registration requirements and characteristics."

A2P 10DLC covers long codes only: "Toll-Free numbers and short code numbers aren't part of the A2P 10DLC system and can also be used for messaging end-users in the United States." HighLevel agrees: "Toll-Free messaging uses a separate verification process and does not rely on A2P 10DLC Brand and Campaign registration."

So the type of number you text from decides which process you need.

Side by side

QuestionA2P 10DLCToll-free verification
Which numbers+1 10DLC numbers (US long codes)Toll-free numbers
Who needs it"Anyone sending SMS/MMS messages over a 10DLC number from an application to the US"Anyone texting US or Canadian mobiles from a Twilio toll-free number
What you submitA Brand (who sends) and a Campaign (opt-in, opt-out, help and the purpose of the messages)One request that covers the business, use case, sample content, website, opt-in, terms and privacy policy
Sending before approvalBlocked with error 30034Blocked with error 30032
Review time at TwilioUp to 5 business days for standard campaignsAbout 3 to 5 business days
Twilio feesBrand submission fees and a campaign vetting fee"Twilio offers this verification service free of cost."
After a rejectionEdit and resubmit the campaign; the vetting fee is charged onceCorrect and resubmit within the seven-day edit window, if eligible

Error 30032 explained

Twilio's title for this code is "30032: Toll-Free Number Has Not Been Verified". The error page says:

"This error is returned when you send a message from a Toll-Free number to a mobile subscriber in the United States or Canada before Toll-Free Verification is approved. As of January 31, 2024, traffic from unverified Toll-Free numbers in Restricted or Pending status is blocked and returns 30032."

Twilio lists three causes:

  • "The Toll-Free number has not been submitted for verification and remains Restricted or Not verified."
  • "The verification request is still in review, so the number is Pending or Verification in progress. Pending Toll-Free traffic to the United States and Canada is blocked until approval."
  • "The verification request was rejected, so the number is not approved for messaging traffic."

How to fix it, by cause:

  1. Not submitted yet. "If the number is not verified, submit a Toll-Free Verification request in Console or through the Messaging Compliance API. Do not send traffic from the number until the verification status is approved."
  2. Still pending. Wait for the review. Twilio says to "allow approximately 3-5 business days for this process."
  3. Rejected. "If the verification was rejected and the request is eligible for edits, correct the rejected information and resubmit it before the edit_expiration deadline. Twilio sets this edit window to seven days from the initial request." A website rejection, for example, comes back as error 30489. Some rejections cannot be fixed: "Rejections for content, or Acceptable Use Policy / Messaging Policy violations are ineligible, and can't be re-submitted."

Blocked messages still cost money. Twilio's toll-free help article says blocked messages return "Error 30032 (any message sent from a Restricted or Pending TFPN) or Error 30007 (if spam/unwanted on a verified TFPN), and are subject to messaging fees."

The A2P 10DLC side: error 30034

On a 10DLC number, the matching block is error 30034. Twilio says: "Twilio blocks messages to U.S. numbers when you send from a +1 10DLC number that is not associated with an approved A2P 10DLC Campaign." Our guide to error 30034 covers the fix, including the one-number limit for Sole Proprietor campaigns.

Which one fits your messages

Twilio describes where each sender type fits:

  • Toll-free "is a great choice for transactional use cases", such as one-time passwords and account alerts.
  • Marketing on toll-free is possible, "however it is extremely important to ensure that all recipients have opted-in and that you maintain a low opt-out ('STOP' reply) rate to avoid filtering."
  • "Short code numbers remain the best method of sending high-volume marketing or promotional messaging in the United States and Canada."
  • A verified toll-free number sends "3 SMS segments per second by default, but can be increased."
  • For long codes, "Registering for A2P 10DLC results in lower message filtering and higher messaging throughput."

Three practical notes:

  • Porting. Twilio says "there is no way to transfer toll-free verifications between providers" and recommends "submitting your verification request as soon as the porting process completes for your number."
  • Policy links. "Starting September 15, 2026, toll-free verification submissions must include separate URL fields for your Privacy Policy and Terms and Conditions. Submissions missing these links will be rejected with error 30493."
  • HighLevel. "Toll-free phone numbers do not use A2P campaign linking and follow a separate verification process."

Both reviews look at sample messages. Precheckly's free A2P 10DLC sample checker checks that each sample names the brand and that at least one has an opt-out instruction, and flags public link shorteners.

For rejection codes on either side, see the list of A2P 10DLC error codes.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.