Carrier approval messaging is the process by which AT&T, T-Mobile, and Verizon independently assess whether a registered SMS campaign meets their specific standards before enabling delivery to their subscribers. TCR registration is not the same as carrier approval—TCR is the reputation authority that coordinates the process, but each carrier maintains its own adjudication criteria and operates its own review queue. Understanding how carrier approval messaging works explains why campaigns can be Active in TCR while still pending with individual carriers, and why campaigns that satisfy TCR automated validation can still be filtered at the carrier level. The TCR 101 guide establishes the registration framework; this article maps the carrier-specific layer that sits between TCR approval and actual message delivery.
As of July 2023, all three major U.S. carriers enforce mandatory A2P registration for traffic sent over 10-digit local numbers. Unregistered traffic is blocked automatically—not filtered with reduced deliverability, but blocked entirely. For campaigns that have completed TCR registration, carrier approval governs the provisioning of your registered numbers onto each carrier’s network. Until provisioning is complete, messages to that carrier’s subscribers do not deliver.
How Does Carrier Approval Messaging Work: The Architecture
The carrier approval messaging process flows through a defined architecture: TCR receives your campaign registration, validates structure and content at the TCR layer, routes the campaign to Direct Connect Aggregators (DCAs), and DCAs provision approved campaigns to their connected carrier networks. The three major carriers—AT&T, T-Mobile, and Verizon—participate in this ecosystem with different DCA relationships and review criteria.
AT&T and T-Mobile require pre-approval before provisioning begins. For standard use cases with clean submissions, both carriers provision through automated DCA workflows. For special use cases—political messaging, sweepstakes, financial services, healthcare—both carriers require manual review by their compliance teams. Campaigns requiring AT&T or T-Mobile manual review display a REVIEW status in the TCR portal’s carrier status table for each carrier pending review.
Verizon participates in the 10DLC ecosystem but historically processes standard use case campaigns through a more streamlined review relative to AT&T and T-Mobile. Verizon’s SHAFT policy (Sex, Hate, Alcohol, Firearms, Tobacco) defines absolute content restrictions that trigger immediate blocking regardless of registration status.
Why Do Carriers Block Unregistered SMS Messages
Carriers block unregistered A2P traffic because unregistered numbers have no accountability layer. Prior to 10DLC enforcement, bad actors could send high-volume spam and phishing messages from local 10-digit numbers with no traceable registration. Registration creates a chain of accountability: the brand, the CSP, and the DCA are all identifiable and can be held responsible for policy violations. Carriers block unregistered traffic not through content filtering but through a whitelist model—only registered, provisioned numbers are allowed to deliver A2P traffic.
The distinction between blocking and filtering matters operationally. Carrier message filtering 10dlc refers to post-registration content evaluation where a provisioned campaign’s individual messages are assessed against carrier filter algorithms. Filtering can reduce deliverability without fully blocking traffic—messages may be delivered intermittently or with delay. Blocking applies to unregistered numbers and means no delivery to that carrier’s subscribers regardless of message content.
AT&T Carrier Approval SMS Campaign Requirements
AT&T’s carrier approval requirements for SMS campaigns place elevated scrutiny on financial services messaging, healthcare content with HIPAA implications, and lead generation programs. AT&T’s DCA2 (secondary DCA layer) review applies enhanced content analysis to campaigns in these categories, adding 5-14 business days to standard provisioning timelines.
AT&T’s content standards prohibit: messages that misrepresent the sender identity, messages soliciting financial commitment before providing required disclosures, messages that use deceptive subject line equivalents or misleading call-to-action language, and messages that circumvent opt-out mechanisms. Campaigns that pass TCR validation but trigger AT&T’s content filters post-provisioning can have their campaign status reverted to a flagged state requiring remediation.
For AT&T carrier approval messaging, the opt-in documentation quality carries the highest weight in review decisions. AT&T’s review teams look for evidence that the opt-in flow on your website matches the description in your campaign registration. A campaign registration describing “website opt-in form at [URL]” where the URL displays a different opt-in flow than described creates an inconsistency that AT&T review will flag.
T-Mobile Verizon AT&T SMS Compliance Differences
T-Mobile’s carrier approval messaging criteria differ from AT&T’s in several operationally significant ways. T-Mobile uses a DUNS Number (Dun & Bradstreet) verification signal as a trust factor in brand assessment. Brands with DUNS registrations that match their TCR brand data receive favorable treatment in T-Mobile’s vetting pass. T-Mobile also applies more aggressive content filtering for campaigns in the financial services and debt/loan adjacent categories than AT&T, generating higher rejection rates for campaigns with certain financial terminology in sample messages.
Verizon’s approach to carrier approval messaging after tcr registration focuses primarily on the SHAFT content policy and throughput limit enforcement. Verizon provisions most standard use case campaigns without manual review, but monitors post-provisioning content for policy violations. Verizon’s post-provisioning monitoring is more active than AT&T’s for high-volume programs, meaning a provisioned campaign that begins sending content inconsistent with its registered use case may be suspended mid-campaign rather than only at the registration review stage.
All three carriers update their approval criteria in response to spam events, regulatory guidance, and FCC enforcement actions. The A2P 10DLC Carrier Policy Updates resource tracks these changes; the Carrier Policies & Updates page documents historical policy changes and their compliance implications.
Carrier Approval Messaging Timeline: What to Expect After TCR Registration
The carrier approval messaging timeline after completing TCR registration depends on use case category and per-carrier review requirements. Standard use cases under normal DCA conditions: 24-72 hours for automated provisioning after TCR approval. Special use cases requiring MNO manual review: 1-4 weeks per carrier, with no guaranteed SLA.
Carrier provisioning is independent per carrier. A campaign can be Active and provisioned with T-Mobile while still pending AT&T manual review. Messages to T-Mobile subscribers deliver; messages to AT&T subscribers do not deliver until AT&T provisioning completes. The per-carrier status breakdown in your TCR portal’s carrier status table shows each MNO’s current status independently.
After provisioning completes, a 24-48 hour network activation period applies before your registered numbers are fully active for A2P delivery on that carrier’s network. Sending immediately after the portal shows an Active carrier status may produce delivery failures during this activation window.
Trust Score Impact on Carrier Approval Messaging
Your TCR trust score directly influences how carriers provision your campaign and what throughput limits they assign. Brands with scores above 75 receive higher message-per-second allocations; brands below 50 receive restricted allocations. Carriers use trust score as a risk signal—higher-scored brands receive more favorable treatment in manual review queues when required, and their provisioned campaigns receive higher baseline throughput allocations.
The TCR Trust Score Preflight Simulator projects your brand’s likely score before registration, enabling pre-registration improvements to the addressable factors that influence carrier provisioning outcomes.
Carrier approval messaging is not a one-time event. Carriers continuously monitor provisioned campaigns for content policy violations, complaint rate thresholds, and opt-out rate signals. Campaigns that exceed carrier-defined complaint or opt-out rate limits can have throughput reduced or be suspended post-provisioning independent of their TCR registration status. Staying within carrier policy on an ongoing basis requires the same attention to content, consent, and opt-out processing that drove initial approval.
Access the Carrier Policy Quick Reference for a consolidated view of AT&T, T-Mobile, and Verizon current approval criteria, prohibited content categories, and enforcement mechanisms—organized by carrier for rapid compliance verification at each stage of your SMS program.
