Executive Summary
US carriers and major messaging platforms treat application-to-person (A2P) traffic on local 10-digit long codes as a registered pathway. If your Brand or Campaign is incomplete, or your sending number is not attached to an approved Campaign, outbound US SMS/MMS from that long code is typically blocked—not merely throttled. On Twilio, that failure mode is documented as error 30034, and since September 1, 2023 Twilio has fully blocked unregistered US A2P 10DLC traffic. Twilio's changelog also states that messaging rates may still apply to blocked attempts, so noncompliance can cost money even when customers never receive the text. Separately, Telephone Consumer Protection Act (TCPA) consent failures create legal exposure that registration alone cannot cure. This guide separates carrier/CSP registration risk from consent risk, maps day-to-day failure symptoms, and gives a remediation operating procedure you can run with your provider.
Short answer: If you send US-bound SMS/MMS from an unregistered +1 10DLC number on a platform that enforces A2P rules, messages are blocked—on Twilio that surfaces as error 30034. Since September 1, 2023, Twilio has fully blocked unregistered US A2P 10DLC traffic, and blocked messages may still incur Twilio messaging rates. Separately, failing to obtain proper consent under TCPA rules creates legal risk that registration alone does not erase.
Who This Is For / Who It Is Not For
Who this is for
- Operations, marketing ops, and compliance leads whose US SMS suddenly fails with "unregistered," "not associated with a campaign," or Twilio 30034-class errors
- Product and engineering teams shipping OTP, appointment, or marketing SMS on local long codes
- Agencies and SaaS platforms registering Brands/Campaigns on behalf of customers and debugging partial delivery
- Finance and leadership stakeholders who need a clear distinction between blocked traffic fees and TCPA liability
Who this is not for
- Teams sending only via already-verified toll-free or short code paths (different registration systems—see related comparison content)
- Pure person-to-person handset texting with no application or CRM automation
- Non-US domestic messaging programs that do not route to US handsets on +1 10DLC
- Anyone seeking a substitute for counsel on TCPA class-action exposure or statutory damages calculations
Definitions
| Term | Plain-English meaning |
|---|---|
| 10DLC | A US 10-digit local long code used for A2P business messaging after Brand + Campaign registration |
| A2P | Application-to-person messaging—traffic originating from software, CRMs, or platforms rather than a handset-only conversation |
| Brand | The legal business identity registered through a Campaign Service Provider (CSP) into The Campaign Registry (TCR) ecosystem |
| Campaign | The declared use case, sample messages, opt-in/opt-out/HELP flows, and related attributes tied to a Brand |
| CSP | Campaign Service Provider / messaging provider that submits Brand and Campaign data and routes traffic (e.g., Twilio, Bandwidth, Telnyx) |
| Unregistered traffic | SMS/MMS from a +1 10DLC number not linked to an approved A2P Campaign for US-bound sends |
| Error 30034 | Twilio's documented error for US A2P 10DLC messages from an unregistered / unassociated number |
| TCPA | Telephone Consumer Protection Act; US federal framework implemented in part at 47 CFR § 64.1200 governing autodialed/marketing calls and texts |
| Snowshoeing | Spreading similar traffic across many numbers to evade filters—often treated as an evasion technique by carriers |
Two Different Problems People Call "Noncompliance"
"Not complying with 10DLC" usually mixes two different problems. Treat them separately so you remediate the right one.
- Carrier / CSP registration noncompliance — Brand/Campaign not approved, number not attached to an approved Campaign, or traffic sent outside the registered program.
- Consent / TCPA noncompliance — Sending marketing or autodialed texts without the required prior express written consent (or mishandling STOP), regardless of registration status.
You can fail one, the other, or both at once. An approved Campaign with weak consent still creates legal risk. Perfect consent paperwork does not unblock an unregistered long code.
What "Must Register" Means in Practice
Per Twilio's A2P 10DLC overview, anyone sending SMS/MMS over a 10DLC number from an application to the US must register. Carriers treat messaging-platform traffic as A2P. Toll-free and short codes are separate paths and are not part of the A2P 10DLC Brand + Campaign system.
Registration has two core pieces:
- Brand — business identity (legal name, tax ID where required, website, contacts, entity type).
- Campaign — use case, opt-in/out/HELP, sample messages, privacy/terms URLs, and related details.
If you skip this and keep sending on a local long code, you are operating outside the verified route US carriers and major CSPs expect. Related reading: How to register with TCR and draft companion pages on registration requirements.
Twilio Error 30034: Unregistered Number Blocked
Twilio error 30034 is titled "US A2P 10DLC - Message from an Unregistered Number." Twilio blocks messages to US numbers when you send from a +1 10DLC number that is not associated with an approved A2P 10DLC Campaign.
Common Causes (from Twilio's docs)
- Sending to a US number from a +1 10DLC number not linked to an approved Campaign.
- Brand or Campaign registration incomplete, so the number remains unregistered for US-bound 10DLC traffic.
- The phone number is not in the Sender Pool of the Messaging Service linked to your approved Campaign.
- Multiple +1 10DLC numbers added to a Sole Proprietor Campaign (only one 10DLC number can be registered for that Campaign; extras stay unregistered).
Documented Remediation Directions
- Complete A2P 10DLC Brand and Campaign registration before sending US traffic from +1 10DLC.
- Add the number to the Messaging Service Sender Pool associated with the approved Campaign.
- Verify the number's A2P registration status and fix Messaging Service / Campaign association.
- For Sole Proprietor Campaigns, keep only the single intended +1 10DLC number in that Messaging Service.
- If you must send before 10DLC registration is complete, Twilio notes alternative sender types outside A2P 10DLC—such as toll-free, short code, or Twilio Verify for verification use cases—subject to those products' own rules.
Other CSPs may use different error codes or filtering behavior. Check with your CSP if you are not on Twilio. See also MyTCRPlus troubleshooting: 10DLC unregistered traffic blocked.
September 1, 2023: Full Blocking of Unregistered Traffic
Twilio's September 1, 2023 changelog states that all SMS and MMS messages sent to US phone numbers using +1 10DLC numbers must go via an approved A2P Campaign. Messages from unregistered +1 10DLC numbers are blocked and return error 30034.
Critical billing note from that changelog: Twilio messaging rates still apply, even for blocked messages.
That means noncompliance is not only "texts don't arrive." You can pay for attempts that never reach the handset. Confirm current billing behavior in your CSP's pricing and error docs—carriers and CSPs mark up and change fees.
Provider documentation from other CSPs (for example Telnyx fee pages) has historically described elevated per-message charges for unregistered traffic in earlier enforcement phases. Treat every fee figure as provider- and date-specific; do not assume a universal industry surcharge.
Risk Matrix: Carrier Blocks vs Filtering vs TCPA
| Risk type | What goes wrong | Typical consequence | Fixed by registration alone? |
|---|---|---|---|
| Unregistered 10DLC | Number/Campaign not approved or not linked | Message blocked (e.g., 30034); possible fees on attempts; lost customer communications | Registration + correct number association |
| Filtered registered traffic | Content, frequency, or consent practices trip filters | Delivery failure or silent filtering despite registration | Fix content, cadence, consent evidence; work with CSP |
| Campaign / Brand rejection | Incomplete packaging, mismatched samples, policy URL failures | Cannot send on that Campaign until resubmitted and approved | Fix TCR packaging; see rejection guides |
| Evasion / Code of Conduct issues | Snowshoeing, unauthorized number replacement, prohibited content | Carrier pass-through fees (provider-documented categories), suspension | Stop evasion; remediate content; work with CSP/carrier process |
| TCPA / consent failure | Marketing/autodialed texts without required consent; ignored STOP | Consumer complaints, litigation exposure, platform AUP enforcement | Proper consent and records—not Brand approval alone |
Under 47 CFR § 64.1200, marketing and autodialed texts generally require prior express written consent under FCC TCPA rules. Statutory damages frameworks can apply under federal law depending on facts—do not invent per-text dollar amounts from secondary blogs. Link the CFR, document your practices, and consult qualified counsel for liability questions.
Registration does not equal consent. An approved Campaign can still send unlawfully if you text people who never agreed to that program. Conversely, perfect consent paperwork does not unblock an unregistered 10DLC number.
Provider-Documented Carrier Non-Compliance Categories (Examples)
Bandwidth's T-Mobile 10DLC documentation describes pass-through fee categories for certain Code of Conduct violations (text enablement before ownership verification, program evasion techniques such as snowshoeing/dynamic routing/unauthorized number replacement, repeated content violations, and other commercial messaging violations). Telnyx publishes related T-Mobile non-compliance fine categories on its 10DLC fees page. Exact dollar amounts and applicability change; always read your CSP's current pass-through schedule rather than treating any blog table as universal law.
Practical takeaway for operators:
- Do not text-enable and blast from numbers before ownership/LOA verification is complete.
- Do not rotate unregistered numbers to "get around" blocks.
- Do not treat SHAFT-prohibited or phishing-like content as a packaging problem you can hide with a new Campaign ID.
- Keep Brand identity, website disclosures, and live message content aligned.
What Noncompliance Looks Like Day to Day
- Appointment reminders, OTPs, or marketing blasts suddenly failing with CSP error codes.
- Partial delivery when only some numbers are attached to an approved Campaign.
- Sole Proprietor setups where a second local number silently fails.
- Finance surprises: attempts billed even when blocked (Twilio's documented behavior for 30034-era full blocking).
- Escalations to Trust & Safety or account review if traffic patterns look like spam or snowshoeing.
- Customer support tickets ("I never got my confirmation text") while dashboards show "sent" or "failed" inconsistently depending on provider status mapping.
If you are debugging rejections rather than blocks, see TCR rejection code troubleshooting and why TCR registration keeps getting rejected.
Decision Framework: Diagnose Before You Resubmit
Use this numbered operating procedure when US long-code SMS fails.
- Capture the exact error — Code, message body, timestamp, From number, Messaging Service / Campaign ID, destination carrier if available.
- Classify the failure — Unregistered/unassociated (block) vs Campaign rejected vs carrier filtered after approval vs consent/complaint event.
- Check number association — Is the From number in the Sender Pool tied to an approved Campaign? Sole Proprietor: is more than one long code present?
- Check Brand / Campaign status — Unverified Brand, failed Campaign, pending number registration with MNOs, or approved-but-not-propagated state.
- Check program hygiene — Opt-in language live and matching samples? Privacy policy SMS section present? STOP/HELP working?
- Choose the remediation path — Register/associate; fix packaging and resubmit; pause marketing and repair consent; or temporary alternate sender (verified TFN/short code) only if that path is already valid for you.
- Re-test at low volume — Controlled sends, monitor error rates, then scale.
- Document — Keep a change log for audits and future CSP tickets.
Quick triage table
| Symptom | Likely class | First action |
|---|---|---|
| Twilio 30034 / "unregistered number" | Registration / association | Complete Brand+Campaign; attach number to approved Campaign Messaging Service |
| Campaign status FAILED / rejected | Packaging / review | Fix samples, opt-in URL, privacy policy; resubmit |
| Some numbers deliver, others fail | Partial association | Audit Sender Pool; Sole Prop one-number rule |
| Approved Campaign but high complaint rate | Consent / content | Pause marketing; verify opt-in evidence; honor STOP |
| Sudden multi-number spray after blocks | Evasion risk | Stop; consolidate onto approved Campaign; engage CSP |
Practical Remediation Steps
1. Confirm the failure mode
- Read the CSP error code and message logs.
- Distinguish unregistered / not associated from Campaign rejected from carrier filtered after approval.
2. If unregistered or not linked
- Finish Brand registration (correct legal name, tax ID where required, website, contacts).
- Finish Campaign registration (use case, samples, opt-in description, policy URLs).
- Attach each sending number to the Messaging Service / Campaign correctly.
- For Sole Proprietor, ensure only one 10DLC number is used on that Campaign.
Follow a structured registration path: How to register with TCR.
3. If you must communicate during remediation
- Use a sender type that is valid for your use case outside incomplete 10DLC registration (for example, verified toll-free or short code)—only if that path is approved for you.
- Do not "blast harder" from additional unregistered long codes; that worsens filtering and evasion risk.
- Prefer transactional, consented, low-volume recovery messages over marketing blasts while the long-code path is down.
4. Fix consent and program hygiene in parallel
- Pause marketing sends until consent records are clear.
- Honor STOP immediately; support HELP.
- Align website disclosures (frequency, rates, non-sharing) with Campaign samples. See msg & data rates disclosure guidance and 10DLC privacy policy template.
- Prefer prior express written consent for marketing texts; electronic consent can qualify when it meets applicable standards—confirm with counsel.
5. Re-test carefully
- Send small controlled tests after Campaign approval and number association.
- Monitor error rates and carrier delivery receipts your CSP provides.
- Expand volume only after stable delivery.
Diagnostic helpers on MyTCRPlus tools (including trust-score preflight and related validators) can help you catch packaging issues before resubmission. They do not replace CSP support or legal advice, and they do not guarantee approval.
Implementation Checklist (Owner + Artifact)
| Step | Owner | Artifact / evidence |
|---|---|---|
| Inventory all US +1 10DLC senders in production | Eng / Messaging ops | Number list + Messaging Service map |
| Confirm Brand status (verified / unverified / vetted) | Compliance / ops | CSP console screenshot or API export |
| Confirm each Campaign approved and use-case accurate | Compliance | Campaign SID/ID + use-case description |
| Attach every production From number to correct Campaign | Eng | Sender Pool audit report |
| Sole Prop: enforce single long code | Eng | Pool diff before/after |
| Verify live opt-in page + privacy SMS section | Legal / marketing | URLs + dated PDF/HTML capture |
| Confirm STOP/HELP keywords functional | Eng | Test thread logs |
| Pause unregistered sends; enable alternate verified path if needed | Ops lead | Change ticket |
| Low-volume soak test post-fix | Eng | Delivery success metrics |
| Document consent source of truth | Legal-ops | Consent ledger schema + sample records |
Risks and Failure Modes (With Mitigations)
| Failure mode | Why it hurts | Mitigation |
|---|---|---|
| Paying for blocked attempts | Twilio documents messaging rates on blocked unregistered sends | Stop unregistered traffic; monitor error 30034 volume daily |
| Partial number registration | Customers on "orphan" numbers never get texts | Automate Sender Pool checks in CI/release |
| Sole Prop multi-number mistake | Extra numbers remain unregistered | Architecture gate: one number per Sole Prop Campaign |
| Resubmitting without fixing root cause | Repeat rejections burn calendar time | Use rejection-code playbooks before resubmit |
| Snowshoeing after blocks | Carrier evasion fees / suspension risk | Consolidate; never rotate to evade |
| "We're registered" masking TCPA gaps | Lawsuit / complaint risk despite delivery | Separate consent audit from TCR status |
| Stale website vs Campaign samples | Rejections (e.g., privacy policy codes) and filter risk | Keep disclosures and samples in sync |
| Agency Brand mismatch | Campaigns rejected when sender ≠ registered Brand | Register the actual sending brand; use reseller rules your CSP requires |
What About Fees and "Fines"?
- CSP / carrier messaging and registration fees: Documented on provider pricing pages; CSPs and carriers mark up and change fees. Twilio's changelog is clear that blocked unregistered messages may still incur messaging rates.
- Additional carrier fees for unregistered traffic: Twilio's overview historically noted additional fees for unregistered traffic in earlier phases; full blocking is now the primary Twilio enforcement for US-bound unregistered 10DLC. Confirm current fee schedules with your CSP.
- T-Mobile / carrier Code of Conduct pass-throughs: Provider docs (Bandwidth, Telnyx, and others) list categories such as text enablement, evasion, and content violations. Treat amounts as provider-published pass-through examples, not a single universal fine schedule.
- TCPA statutory damages: Can apply under federal rules depending on facts. Do not invent per-text dollar amounts. Read 47 CFR § 64.1200 and speak with counsel.
Internal Links and Related Guides
- How to register with TCR — step-by-step
- Unregistered traffic blocked troubleshooting
- A2P SMS blocked troubleshooting
- Why TCR registration keeps getting rejected
- Fix TCR rejection code 9108 (privacy policy)
- Video: unregistered traffic blocking
- Related draft slugs for cluster coverage:
/10dlc-vs-toll-free/,/tcr-campaign-rejection/,/tcr-registration-requirements/,/tcpa-text-message-rules/
FAQ
Will my texts send if I never register for 10DLC?
On Twilio, US-bound SMS/MMS from unregistered +1 10DLC numbers are blocked (error 30034) under the September 1, 2023 full-blocking policy. Other CSPs enforce similarly—confirm with yours. Do not assume a "grace period" without written confirmation from your provider.
Do I still get charged for blocked messages?
Twilio's September 1, 2023 changelog states messaging rates still apply even for blocked messages. Verify on your invoice and CSP billing docs.
Is getting Campaign approval enough to avoid lawsuits?
No. Approval addresses the registered messaging pathway. TCPA consent and state privacy rules are separate. Marketing/autodialed texts generally require prior express written consent under FCC TCPA rules.
What is the difference between error 30034 and a TCR rejection?
30034 is a send-time block for unregistered / unassociated numbers. TCR rejection happens during Brand or Campaign review before (or instead of) approval. Different fixes apply.
Can I keep sending on toll-free instead?
Toll-free is a separate verification path, not a loophole. You still need toll-free verification (where required) and lawful consent. Twilio notes that toll-free/short code are outside A2P 10DLC—but each has its own compliance gate.
How fast can I remediate?
Brand and Campaign timelines vary by CSP queue and completeness. Incomplete websites, privacy policies, or mismatched samples commonly add rounds of rejection. Fix packaging first; see privacy policy 9108.
Why do some of my numbers work and others fail?
Often only some numbers are in the Sender Pool of the Messaging Service tied to an approved Campaign. Sole Proprietor Campaigns allow only one registered 10DLC number—extras stay unregistered and can fail with 30034-class errors.
Does registration replace CTIA / carrier content rules?
No. Registration identifies the sender and use case. Content, frequency, consent, and prohibited-category rules still apply after approval.
What if my Brand is "Unverified"?
Unverified Brands generally cannot register standard 10DLC Campaigns until identity is fixed (update/resubmit, appeal, or vetting paths depending on CSP/TCR process). Resolve Brand status before expecting Campaign approval.
Are carrier "fines" the same as TCPA damages?
No. Carrier pass-through fees (when applicable) are commercial enforcement through your CSP. TCPA exposure is a separate legal regime. Do not conflate them in risk reporting to leadership.
Key Takeaways
- Unregistered US A2P 10DLC traffic is broadly blocked on major platforms; Twilio documents this as error 30034 with full blocking since September 1, 2023.
- Twilio states messaging rates may still apply to blocked unregistered attempts—stop the traffic, do not "retry harder."
- Fix Brand + Campaign + number association; Sole Proprietor Campaigns support only one 10DLC number.
- Registration risk and TCPA consent risk are different problems requiring different controls.
- Treat provider fee and fine tables as CSP-specific, not universal; never invent statutory damage amounts.
- Diagnose with logs first; remediate packaging and association; soak-test before full volume.
- Use alternate verified senders only when that path is already valid—do not snowshoe across unregistered long codes.
- Keep opt-in pages, privacy disclosures, samples, and live traffic aligned to reduce rejection and filter risk.
Disclaimer
This article is for informational purposes only and is not legal advice. Blocking behavior, billing on failed messages, fees, pass-through penalties, and TCPA exposure depend on your CSP, carriers, and facts. Confirm current rules with your provider and qualified counsel before sending commercial SMS/MMS. MyTCRPlus does not guarantee Campaign approval, delivery rates, or legal outcomes.