Businesses sending routine text alerts, appointment reminders, and one-time passcodes are discovering that their messages never reach customers, even though their SMS provider’s dashboard shows “delivered.” A report from The Next Web on the mechanics of carrier-side filtering has pushed SMS deliverability back into the spotlight on October 18, 2026, as developers and marketing teams compare notes on why legitimate application-to-person (A2P) traffic keeps getting silently dropped by US carriers.
The short version: carriers are not blocking spam alone. They are running automated, risk-based filters across every text sent from a standard 10-digit phone number, and those filters catch plenty of legitimate businesses in the crossfire. For engineers building SMS notification systems, the fix lives mostly in a compliance and infrastructure layer most consumer apps never have to think about: A2P 10DLC registration through The Campaign Registry. Skip it, and even a perfectly worded, fully consented appointment reminder can vanish without a bounce, an error code, or any signal that something went wrong.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What’s Actually Happening: SMS Deliverability in October 2026
SMS deliverability describes whether a text message sent through an API actually reaches a subscriber’s handset, as opposed to being accepted by a messaging provider and then quietly filtered somewhere between the provider and the carrier network. That distinction matters more than most developers realize. According to reporting reviewed for this story, an SMS API can return a success response the moment a message is accepted for delivery, while the carrier filters or blocks it further downstream, long after the API call has already returned “200 OK.” The business sees no error. The customer never gets the text. Nobody finds out until support tickets pile up.
Carrier filtering in the United States is risk-based rather than content-based alone. Signals that trigger filtering include high sending volume, rising complaint rates, a mismatch between a message’s actual content and the use case a business declared during registration, suspicious links, spam-associated wording, and sudden spikes in sending patterns that look automated or bot-like rather than organic. AT&T, Verizon, and T-Mobile all apply this kind of filtering to application-to-person traffic sent from ordinary 10-digit long codes, the same type of number a small business might use for its main office line.
This is not a new rule that dropped overnight. US carriers have required A2P 10DLC registration for business texting since February 2025, when enforcement became fully active across the major networks. What’s driving renewed attention in October 2026 is the layered cost of staying compliant, the surcharge schedule set to shift again on November 1, 2026, and the fact that so many developers building SMS notification features still don’t know the registration step exists until their delivery rates collapse.
A2P 10DLC, Explained for Developers
A2P stands for application-to-person, the category covering any text sent by software to a human being rather than between two people texting each other. 10DLC means 10-Digit Long Code, the standard ten-digit phone number format businesses use to send that traffic. The registration layer that governs all of this is The Campaign Registry, commonly abbreviated TCR, which administers the brand and campaign vetting system that carriers rely on to decide whose traffic to trust.
Twilio, one of the largest communications platforms for developers, frames the registration requirement plainly: “10-digit long codes have traditionally been designed for Person-to-Person (P2P) traffic only, causing businesses to be constrained by limited throughput and heightened filtering.” That’s the root problem. A2P 10DLC exists precisely because ordinary phone numbers were never built to carry commercial messaging volume, and carriers needed a way to separate a business sending 50,000 appointment reminders a month from a person texting their group chat.
Registration works in two layers. First, a business registers its brand, essentially a verified identity tied to its legal entity. Second, it registers one or more campaigns, which describe the specific use case: two-factor authentication codes, appointment reminders, marketing promotions, customer care, and so on. Twilio describes the mechanism this way: “The major US carriers, acting through an entity called The Campaign Registry (TCR), have formalized regulations to make explicit throughput allowances, and to reduce filtering rates in exchange for pre-registration and compliance by customers.” In plain terms, carriers trade higher throughput and lower filtering risk for upfront transparency about who is texting and why.
Developers who skip this step are not automatically blocked at the API level. Twilio is explicit about the downstream consequence: “Carriers block any A2P messaging traffic to US recipients using unregistered Twilio 10DLC numbers.” The filtering happens at the carrier, not the provider, which is exactly why so many teams discover the problem only after a launch, a feature rollout, or a sudden spike in message volume triggers carrier scrutiny. A related Twilio post on individual and low-volume senders reinforces the same point: “They will be filtering or blocking A2P messages over 10DLC numbers that are not registered and verified.” Even small, low-volume test traffic is not exempt.
Why Messages Fail Silently
The hardest part of debugging SMS deliverability is that failure often produces no error at all. Some blocked messages fail silently, without an explicit failure status returned to the sender’s system. An API call can return success, a delivery receipt can arrive, and the message can still never reach the subscriber’s phone because a carrier-side filter intercepted it after the provider already logged it as sent. This is structurally different from, say, a failed HTTP request or a bounced email, where the sender typically gets some kind of signal.
Debugging deliverability properly means checking status at every layer: API acceptance, provider-reported message status, any carrier response or error code that does come through, delivery receipts where available, the recipient’s opt-out status, and complaint or spam signals tied to the sending number. Provider acceptance can occur before carrier filtering kicks in, which means a clean log on the sending side tells a developer almost nothing about whether the text actually landed. Teams that only monitor API response codes are flying blind on real-world delivery.
One related wrinkle developers often overlook: landline numbers generally cannot receive SMS in most markets. A notification system that doesn’t distinguish mobile numbers from landlines at signup will quietly accumulate a pile of messages that were never deliverable in the first place, inflating what looks like a filtering problem but is really a data-hygiene one. Getting SMS campaigns right starts well before carrier registration, at the point where a phone number is first collected and validated. The same discipline that governs email authentication, covered in detail in this site’s guide to SPF, DKIM, and DMARC setup, applies conceptually here: unauthenticated, unverified senders get treated with suspicion by default.
The Cost Structure Behind Compliance
Registration is not free, and the fee structure has several moving parts that catch developers off guard when they’re budgeting for an SMS feature. Reported figures put the one-time brand registration fee around $4 to $4.50. Optional vetting, which can speed up approval and unlock higher throughput, runs roughly $41.50 for standard vetting or $101.50 for enhanced vetting. Campaign registration fees are commonly reported in the range of $1.50 to $30 per month depending on the use case and volume tier. Standard campaign vetting is reported at $15 per attempt, with an optional expedited 48-hour review costing $50 in one current fee schedule.
On top of registration fees, carriers charge per-message surcharges that differ sharply based on registration status. Registered traffic is commonly billed around $0.003 to $0.005 per message segment, while unregistered traffic has been reported at $0.010 to $0.012 per segment, roughly double to triple the cost, on top of carrying a much higher risk of outright filtering. T-Mobile’s pass-through pricing reportedly increased in January 2026, and one estimate puts carrier surcharges alone for a business sending 10,000 messages a month at roughly $30 to $50. A further surcharge adjustment is scheduled for November 1, 2026, moving some outbound A2P 10DLC surcharges to $0.005 per message and adding United Wireless to the list of networks applying these fees.
Approval timelines vary depending on which source you check and which vetting tier a business chooses. One estimate puts most registrations at roughly 5 to 7 business days, while a broader range cited elsewhere spans 1 to 4 weeks depending on vetting requirements and campaign type. That gap matters operationally: a startup launching an SMS onboarding flow next week needs to start registration now, not after the feature ships, because carrier-side approval is not something an engineering team can route around with clever retry logic.
Table: A2P 10DLC Registration Costs, 2026
| Fee Type | Reported Cost | Frequency | Notes |
|---|---|---|---|
| Brand registration | $4–$4.50 | One-time | Per registered business brand |
| Standard vetting | ~$41.50 | One-time, optional | Improves trust score and throughput |
| Enhanced vetting | ~$101.50 | One-time, optional | Highest trust tier |
| Campaign registration | $1.50–$30/month | Monthly | Varies by use case and volume tier |
| Standard campaign vetting | $15 | Per attempt | Can be resubmitted if rejected |
| Expedited vetting | $50 | Per attempt, optional | 48-hour turnaround |
| Registered carrier surcharge | $0.003–$0.005 | Per message segment | Rising to $0.005 flat on Nov. 1, 2026 for several networks |
| Unregistered carrier surcharge | $0.010–$0.012 | Per message segment | Plus much higher filtering risk |
Throughput Limits: Why Volume Tier Matters
Beyond cost, registration tier directly determines how fast a business can send messages, which matters enormously for anything time-sensitive like one-time passcodes or appointment confirmations. Reported throughput ranges run from roughly 3 to 180 messages per second for lower tiers, up to 100-plus messages per second for higher-volume configurations. Daily segment limits follow a similar structure: sole proprietor registrations are commonly capped around 3,000 segments per day, while high-volume standard registration can reach 600,000 segments per day.
For a developer building a notification system, this means the registration tier chosen at setup time becomes a hard architectural constraint later. A SaaS product that registers as a sole proprietor and later scales to tens of thousands of users sending password-reset codes will hit a throughput wall long before it hits a database bottleneck. Planning the registration tier around realistic 12-month growth, not launch-day volume, avoids a painful re-registration cycle mid-scale.
Table: SMS Throughput and Volume Tiers
| Registration Tier | Typical Throughput | Daily Segment Limit | Best Fit |
|---|---|---|---|
| Sole Proprietor | Low (single number) | ~3,000 segments/day | Solo developers, small test campaigns |
| Low Volume Standard | 3–180 msgs/sec range | ~6,000 segments/day | Early-stage startups, limited user base |
| High Volume Standard | 100+ msgs/sec | ~600,000 segments/day | Scaling SaaS, consumer apps with OTP/alerts |
| Enhanced-vetted brands | Highest available | Carrier-dependent, generally highest | Large enterprises, high-trust use cases |
How Developers Debug Deliverability in Practice
Because filtering happens invisibly between provider acceptance and handset delivery, engineering teams need to instrument more than just the API call. A disciplined debugging approach checks status at each of these layers in order: did the API accept the request, what status does the provider report after acceptance, did a carrier-level response or error code come back, did a delivery receipt arrive, is the recipient opted out, and are there complaint or spam signals tied to the sending number or campaign. Treating “API returned success” as proof of delivery is the single most common mistake teams make when building SMS notification features.
This layered debugging model echoes patterns familiar from other developer tooling categories. Teams that already run a multi-provider LLM gateway to track model-level failures will recognize the same instinct applied here: never trust a single layer’s “success” signal as proof that the full pipeline worked. The same applies to API credential hygiene. Just as leaked secrets get caught by automated secret-scanning tools before they ship to production, SMS deliverability problems get caught earlier when teams build automated monitoring for carrier-side filtering signals rather than waiting for customer complaints.
Message content also plays a direct role in filtering risk. Carriers flag sudden volume spikes, irregular sending patterns, suspicious links (including shortened URLs), and spam-associated wording as possible triggers. A business that registers a “customer care” campaign and then starts sending promotional discount codes through the same number is exactly the kind of content-to-registration mismatch that carrier filters are built to catch. Keeping registered campaign descriptions honest and narrow, rather than registering broadly and sending whatever fits later, reduces filtering risk measurably.
Competitive Landscape: How SMS Providers Handle Deliverability
The major CPaaS providers, Twilio, Vonage, MessageBird, Sinch, and Plivo among them, all operate within the same carrier-imposed A2P 10DLC framework, since none of them control carrier-side filtering directly. What differentiates them for developers is how much registration friction, deliverability visibility, and automated compliance tooling each one bakes into its API and dashboard. Sinch’s own guidance on fixing SMS delivery failures frames the core problem the same way most of the industry does: deliverability failures stem from the gap between what a provider’s API confirms and what actually reaches a handset.
For teams evaluating providers, the practical questions worth asking are less about raw pricing and more about operational transparency: does the dashboard clearly separate “accepted by API” from “confirmed at carrier” status, does the provider proactively flag registration gaps before sending large volumes, and how quickly does support respond when filtering rates spike unexpectedly. These are the same categories of trust-and-transparency questions developers already ask when comparing AI coding tools or API providers, where clear setup documentation and credential management separate a smooth integration from a support-ticket nightmare.
Historical Context: From Unregulated Long Codes to Mandatory Registration
Business texting in the US spent years in a gray zone. Before A2P 10DLC existed as a formal category, businesses frequently sent commercial traffic through ordinary long codes designed for person-to-person conversation, exploiting a format never built for bulk commercial use. That workaround produced exactly the kind of abuse carriers eventually cracked down on: high-volume spam, phishing campaigns, and fraud riding on ordinary-looking phone numbers with no registration trail.
As one 2026 compliance breakdown of the registration system describes it, The Campaign Registry framework and A2P 10DLC emerged as the carrier industry’s answer, formalizing what had been an unregulated free-for-all into a structured, auditable registration system. Full enforcement across the major US carriers became active in February 2025, which is the inflection point most current reporting on registration fees and filtering mechanics points back to. What’s changed since then is not the underlying requirement but the sophistication of the filtering logic applied to unregistered and even registered-but-suspicious traffic, and the layered fee schedule that keeps shifting, with the next adjustment landing November 1, 2026.
Market Impact: Who Feels This Most
The businesses most exposed to deliverability problems are not large enterprises with dedicated compliance teams, they’re small and mid-sized companies and independent developers building their first SMS feature without realizing registration is a prerequisite, not an optional add-on. A solo founder wiring up SMS-based two-factor authentication for a new app, or a small clinic sending appointment reminders through a no-code automation platform, is exactly the profile most likely to register late, register incorrectly, or skip registration entirely until delivery rates collapse.
AI voice agent platforms represent a newer and faster-growing category running into this exact problem. A voice agent that calls a customer and then sends a text confirmation needs that follow-up SMS to be registered exactly like any other business text, and developers building these pipelines quickly learn that an AI-generated conversation means nothing if the confirmation text never arrives. The compliance burden doesn’t scale down for smaller or newer categories of software; if anything, less mature tooling categories hit registration gaps more often because the pattern isn’t yet baked into standard onboarding checklists.
Predictions: Where SMS Deliverability Goes From Here
- Carrier surcharge schedules will keep shifting through 2027 as networks pass through infrastructure costs, with the November 1, 2026 adjustment unlikely to be the last change this year.
- More CPaaS providers will build automated pre-flight checks that flag likely filtering risk before a campaign sends at scale, rather than after delivery rates drop.
- AI voice agent and automation platforms will drive a new wave of first-time registrants discovering A2P 10DLC requirements the hard way, pushing providers to simplify onboarding flows specifically for that segment.
- Expect growing demand for deliverability monitoring tools that track carrier-level signals separately from API-level success responses, closing the visibility gap that currently makes filtering so hard to debug.
- Registration vetting tiers will likely see further price segmentation as carriers try to balance throughput demand against fraud-prevention costs across a growing base of registered brands.
Practical Steps for Developers Building SMS Features
For engineering teams building or auditing an SMS notification pipeline today, the practical checklist starts well before writing integration code. Confirm the sending number category: 10DLC, toll-free, or short code, since each carries different registration paths and throughput ceilings. Register the brand and campaign through the chosen provider and The Campaign Registry before sending any meaningful volume, not after a feature ships. Keep campaign descriptions narrow and accurate, since a mismatch between registered use case and actual message content is a direct filtering trigger.
Instrument delivery monitoring at every layer described above, not just API response codes, and build alerting around unexpected drops in delivery receipts rather than relying on customer complaints as the first signal something broke, a point Plivo’s own guidance on maximizing SMS delivery makes as well. Validate phone numbers at signup to filter out landlines before they ever enter a sending queue. And budget registration and surcharge costs into the actual unit economics of the feature, since a $0.003 per-segment surcharge sounds trivial until it’s multiplied across hundreds of thousands of OTP codes a month.
None of this is exotic engineering. It’s closer to the kind of infrastructure discipline developers already apply to email authentication, where getting SPF, DKIM, and DMARC configured correctly determines whether a transactional email lands in an inbox or a spam folder. SMS carries the same lesson with a sharper edge: there’s often no spam folder to check, no bounce message to parse, just silence where a delivered text should have been.
Frequently Asked Questions
What does A2P 10DLC mean?
A2P 10DLC stands for Application-to-Person, 10-Digit Long Code. It describes the registration framework US carriers require for businesses sending text messages from standard ten-digit phone numbers through software rather than through a short code or toll-free number.
Why do carriers block legitimate business texts?
Carriers apply risk-based filtering to reduce spam, fraud, and non-compliant traffic. Signals like high sending volume, rising complaint rates, suspicious links, spam-associated wording, and a mismatch between declared campaign use case and actual message content can all trigger filtering, even for messages sent by a legitimate, consented business.
How long does A2P 10DLC registration take?
Reported approval times vary by source. One estimate puts most registrations at roughly 5 to 7 business days, while a broader range cited elsewhere spans 1 to 4 weeks depending on vetting tier and campaign type.
How much does A2P 10DLC registration cost?
Reported figures include a one-time brand fee around $4 to $4.50, optional vetting around $41.50 for standard or $101.50 for enhanced vetting, and campaign fees commonly ranging from $1.50 to $30 per month. Standard campaign vetting runs about $15 per attempt, with a $50 expedited option in some fee schedules.
What happens if a business doesn’t register for A2P 10DLC?
Unregistered traffic can be accepted by the SMS API and still be filtered or blocked by the carrier. Since February 2025, enforcement has been fully active across major US carriers, meaning unregistered business texts face a much higher risk of silent filtering, with no explicit failure status returned to the sender.
Can landline numbers receive SMS?
No. Landline numbers generally cannot receive SMS in most markets. Developers building SMS notification features should validate that collected phone numbers are mobile numbers before attempting delivery.
Which carriers enforce A2P 10DLC filtering?
AT&T, Verizon, and T-Mobile all require A2P 10DLC registration for business traffic sent from local ten-digit numbers and apply filtering or blocking to unregistered traffic.
Is A2P 10DLC registration a one-time process?
Brand registration is generally a one-time fee, but campaign registration carries ongoing monthly fees, and most campaigns require an initial multi-month commitment regardless of whether a business continues sending at that volume.
