Twilio Error 30034: What It Means and How to Clear It

Twilio's error page, last modified on 21 April 2026, gives the full name as US A2P 10DLC, message from an unregistered number. The description says Twilio blocks messages to US numbers sent from a +1 10DLC number that is not linked to an approved campaign.

The same page states what registered means. To send application-to-person traffic over a US long code, the business has to complete A2P 10DLC registration and attach the number to the Messaging Service that is tied to its approved campaign.

A2P 10DLC is the system US carriers use for business texting from ordinary 10-digit numbers. Twilio's sole proprietor article summarizes it as three requirements: the business identifies itself to the carrier networks by registering a brand, it registers what type of messages it sends by registering a campaign, and it associates every 10DLC number it sends from with a campaign. Error 30034 is what the third requirement looks like when it has not been met.

The first cause is the plain one: the number is not associated with an approved campaign. This covers a business that never registered and a business that registered one number and is sending from another.

The second is timing. Brand or campaign registration is not finished, so the number remains unregistered for US traffic. Twilio's vetting FAQ says a newly submitted campaign sits in an in-progress state until it has passed manual vetting, and that customers can send on the A2P route only once the campaign is fully approved.

The third is the sender pool. The campaign is approved, and the number was never added to the Messaging Service linked to it. This is the cause to suspect when the error starts after a new number is bought.

The fourth applies to sole proprietors. Twilio's error page says only one number can be registered per sole proprietor campaign, so any others added to it stay unregistered.

Twilio's listed solutions follow the causes. Finish brand and campaign registration before sending to US numbers from a +1 10DLC number. Add the number to the sender pool of the Messaging Service linked to the approved campaign. Check the number's registration status, and if it is still unregistered, update the association between the Messaging Service and the campaign. For a sole proprietor campaign, keep only the one number in use in that Messaging Service.

The structure behind these steps is set out in Twilio's onboarding guide. A campaign is registered together with a Messaging Service. The Messaging Service needs at least one Twilio phone number in its sender pool, and each Messaging Service can be linked to only one campaign at a time. A number in a different Messaging Service, or in none, is outside the campaign.

A working order for an agency is below. It starts with the checks that take a minute and ends with the ones that take days.

• Open the failed message and confirm the code is 30034 and the sender is a 10-digit US number
• Find the brand and campaign for that client and read their status
• If the campaign is approved, open its Messaging Service and look for the sending number in the sender pool
• If the number is missing, add it and send a test once it shows as registered
• If the brand is a sole proprietor, remove every number but one from the Messaging Service
• If the campaign is pending, stop sending from the number until it is approved
• If the campaign was rejected, read the rejection codes and correct the cause before resubmitting

This is the case that confuses people most. The dashboard shows an approved brand and an approved campaign, and messages still fail. Two of Twilio's four causes describe it: the number is not in the right sender pool, or the brand is a sole proprietor with more than one number.

It commonly follows a change. A client buys a second local number, an agency swaps a number that was flagged, or a number is moved between sub-accounts. The new number does not inherit the registration.

HighLevel, which runs on the same registration system, describes the same situation in its campaign guide under the heading of an approved campaign with failing texts. It says to confirm that the number shows the green A2P Verified label in the phone number settings, and if it does not, to link the number to the approved campaign. It adds that each new local number needs this check.

A further possibility is a short delay between adding a number and its registration taking effect. Twilio's error page does not give a figure for this, so we cannot say how long a newly added number takes to show as registered.

The error page for 30034 contains no billing information. The statement comes from a separate Twilio support article on the shutdown of unregistered 10DLC messaging. Our research notes record it as saying that unregistered messages to US numbers were fully blocked from 1 September 2023, that a blocked message returns error 30034, and that it is still billed.

We could not open that article directly for this post. The page refused automated access, and the notes mark the reading as taken from a search summary. Treat the billing statement as reported, and confirm it on a current invoice.

Twilio's overview of A2P 10DLC says separately that unregistered traffic from a Twilio 10DLC number incurs additional carrier fees. For toll-free numbers, Twilio's help article is explicit that blocked messages from unverified numbers are subject to messaging fees.

The practical reading for an agency is that a failing automation should be paused. A workflow that keeps firing texts from an unregistered number produces errors and, on the reported terms, charges.

If the campaign is approved and the number was simply missing from the Messaging Service, the fix is a configuration change. Twilio does not publish a time for a number's registration to take effect on the pages we read.

If registration is not finished, the stated review times apply. Twilio's onboarding guide says brand review typically takes a few minutes and can take seven business days or more when it goes to manual review. Its vetting FAQ says campaign review takes up to five business days for standard use cases, and asks customers to contact support if vetting is still in progress after ten days.

A new registration also costs money. Twilio lists a brand fee of 4.50 dollars for sole proprietor and low-volume standard brands and 46 dollars for a standard brand, a 15 dollar campaign vetting fee, and a monthly campaign fee of 1.50 to 10 dollars depending on the use case.

Twilio's error page says that a business that must send before registration is complete can use a sender type other than 10DLC, such as a toll-free number, a short code, or Twilio Verify for verification messages.

A toll-free number is not an instant substitute. Twilio says messages from unverified toll-free numbers have been blocked since 31 January 2024 and return error 30032. Its API guide says toll-free verification requests are reviewed within three business days, and its help article says to allow about three to five.

Switching the sender does not change the consent the business needs. The same people have to have agreed to the same messages, and toll-free verification asks for proof of the opt-in too.

Error 30032 is the toll-free version. It means a toll-free number sent a message before its verification was approved.

Error 30007 is filtering. Twilio's toll-free help article describes it as the code returned when a message is judged spam or unwanted on a verified number. A registered sender can receive it, and registration does not clear it.

Codes from 30880 upward, such as 30886 and 30925, are campaign rejection reasons. They appear on the campaign record after a failed review. Twilio's support article on rejected campaigns says to record every code and reason on the failed campaign, correct the business information, description, consent flow, linked pages and samples involved, and resubmit if the campaign is eligible.

The sequence matters. A campaign rejection leads to no approved campaign, which leads to 30034 on every message from that client's numbers. Fixing the 30034 then means fixing the rejection first.