A2P SMS OTP in USA 2026: 10DLC, Toll-Free, and Short Code Compared

Every US business that sends OTP SMS uses one of three application-to-person (A2P) SMS routes: 10DLC long codes, toll-free SMS, or short codes. Each route has different throughput limits, cost structures, time to launch, and compliance requirements. The wrong choice can either over-spend on capacity you do not need or under-deliver during peak OTP loads.

This guide explains how A2P SMS works in the USA in 2026, compares the three routes head to head, and shows when each makes sense for your OTP volume and use case. For broader US OTP context, see our SMS OTP Service USA hub. For pricing detail, see our SMS OTP Pricing USA guide.

What is A2P SMS?

A2P SMS, or Application-to-Person SMS, is automated text messaging from a business application to an individual mobile phone. It differs from P2P (person-to-person) SMS in that the sender is a software system rather than a human, and the message is generated programmatically.

For OTP traffic, A2P is the only viable model. OTP delivery from a regular consumer SMS account would not scale, would not survive carrier filtering, and would violate carrier terms of service.

In the USA, A2P SMS runs on three carrier-approved route types:

• 10DLC long codes: Registered 10-digit phone numbers, vetted through The Campaign Registry and approved by each carrier.
• Toll-free SMS: +1 8XX numbers verified through the Toll-Free Verification (TFV) process operated by Somos.
• Short codes: 5-digit or 6-digit numbers leased through CSCA / iconectiv and vetted by CTIA.

Any A2P SMS sent outside these registered routes is filtered or blocked by carriers within hours.

Side-by-side comparison

Businesses in the USA typically choose between 10DLC long codes, toll-free SMS numbers, and short codes depending on message volume, launch speed, throughput requirements, and OTP delivery performance. 10DLC numbers use standard 10-digit phone numbers and are registered through The Campaign Registry (TCR), making them a popular option for businesses sending between 5,000 and 5 million OTP messages per month. They generally take between two to six weeks to launch unless using pre-approved campaigns, and support throughput rates around 75 messages per second by default, scaling up to 150 MPS with higher trust scores and vetting.

Toll-free SMS uses +1 8XX numbers registered through Somos via TFV and can typically be launched within one to three days, making them attractive for faster onboarding and lower-volume authentication workflows under 100,000 messages per month. Throughput is lower at around 30 messages per second, while per-message pricing is generally higher than 10DLC.

Short codes, which use dedicated 5- or 6-digit numbers registered through iconectiv and CTIA, are designed for enterprise-scale OTP delivery and very high messaging throughput. Although setup can take eight to twelve weeks and monthly leasing costs are significantly higher, short codes support 200+ messages per second with industry-leading OTP delivery rates exceeding 99.5 percent. For businesses operating large-scale authentication workflows in the USA, short codes remain the highest-performance option for OTP verification infrastructure.

10DLC: the default choice

10DLC is the modern standard for US A2P SMS, including OTP. It exists in roughly the form it does today because of three regulatory drivers: (1) carriers needed to clean up unregistered long-code abuse, (2) businesses needed an affordable A2P route between toll-free and short code, and (3) the wider industry needed a verified-identity model akin to STIR/SHAKEN for voice.

Strengths:

• Cheapest per-message cost for sub-5M monthly volume.
• Standard 10-digit phone number familiar to users.
• Highest throughput per-dollar at mid volume.
• Pre-approved shared routes available (uniquely from Message Central VerifyNow USA) for under 5 minute launch.

Trade-offs:

• 2 to 6 week registration timeline (unless using pre-approved routes).
• Throughput capped per campaign by Trust Score and carrier-tier.
• Carrier pass-through fees apply per message.

For the full 10DLC framework, see our 10DLC OTP SMS USA guide.

Toll-Free SMS: the quick-launch alternative

Toll-free SMS uses +1 8XX numbers that businesses already own for voice traffic. Toll-Free Verification (TFV), operated by Somos, vets businesses and use cases similar to 10DLC's TCR but with a simpler, faster process.

Strengths:

• 1 to 3 day approval timeline, much faster than 10DLC.
• Useful for businesses with existing toll-free voice numbers.
• Strong delivery on carriers; less filtering risk than unregistered long codes.

Trade-offs:

• Per-message cost is roughly 1.5x to 2x 10DLC for OTP.
• Throughput capped at 30 MPS, limiting peak OTP volume.
• Number format (+1 8XX) is less user-friendly than 10-digit local numbers.
• Toll-free A2P share is lower; some power-user customers expect 10DLC for OTP.

Toll-free SMS works well as a fast launch path or as a fallback when 10DLC throughput is constrained. It is also commonly used in financial services where the legacy toll-free brand is part of the user experience.

Short codes: the high-volume option

Short codes are 5 or 6 digit numbers leased from CSCA / iconectiv, vetted by CTIA, and approved by carriers. Common consumer brands use short codes for both marketing and authentication (e.g. "Reply YES to confirm").

Strengths:

• Highest throughput per number: 200 MPS by default, 1,000 MPS plus with enhanced vetting.
• Per-message cost is lowest at scale ($0.005 to $0.008 plus lease).
• Strong brand recognition: users learn to trust the short-code number associated with your brand.
• Highest delivery rates (99.5 percent plus typical) due to direct carrier approval.

Trade-offs:

• $500 to $1,500 monthly lease per code, unrelated to volume.
• 8 to 12 week provisioning timeline.
• CTIA vetting requirement is more stringent than TCR.
• Vanity short codes (memorable numbers) cost more and have longer waitlists.

Short codes only break even on cost above approximately 5 to 10 million OTPs per month, where the per-message savings exceed the monthly lease. For most mid-market US OTP senders, 10DLC is more economical.

Choosing the right A2P route for your OTP volume

Three volume tiers determine the obvious choice:

Under 100,000 OTP per month

10DLC with pre-approved routes is the default. Toll-free SMS works as a fast-launch alternative. Short codes are uneconomical at this scale.

100,000 to 5 million OTP per month

10DLC is almost always the right choice. Throughput at default Trust Score handles 100k to about 2M per month per campaign; enhanced vetting unlocks higher tiers up to about 5M per campaign. For volumes near 5M, consider dual 10DLC campaigns or short code as alternatives.

Above 5 million OTP per month

Short codes start to pay back. The $500 to $1,500 monthly lease becomes a small fraction of total spend, and the higher throughput ceiling avoids campaign-level fragmentation. Many large US brands use short codes for OTP at this scale.

For the full pricing math by tier, see our SMS OTP Pricing USA guide.

Throughput planning for OTP

OTP traffic is bursty by nature. A login peak at 9pm on a weekday, a marketing-campaign-driven signup spike at lunch, a payment-system kickoff in the morning. Your A2P throughput must absorb peaks 5 to 10x the average rate.

For a service averaging 100,000 OTPs per month (about 3,300 per day, 140 per hour, 2.3 per second average), peak might be 23 OTPs per second. Within 10DLC standard throughput of 75 MPS on T-Mobile, this is comfortably absorbed. For services averaging 1 million OTPs per month (about 33,000 per day, 1,400 per hour, 23 per second average), peak might be 230 OTPs per second. This exceeds standard 10DLC throughput and requires enhanced vetting, number pools, or short codes.

Compliance differences across routes

All three A2P routes require carrier-approved registration and TCPA-compliant operation. Specific differences:

Compliance area10DLCToll-freeShort codeBrand verificationTCR + Trust ScoreSomos TFVCTIA vettingCampaign / use case approvalPer campaignPer numberPer short code programSTOP / HELP keyword supportRequired for marketing, recommended for OTPRequiredRequiredTCPA consentRequiredRequiredRequiredAudit loggingStandardStandardStandard

For full TCPA detail, see our TCPA-Compliant SMS OTP API guide.

Mixing routes: hybrid deployments

Some large US OTP senders run hybrid deployments:

• 10DLC primary, toll-free fallback: When 10DLC throughput is hit, traffic spills to toll-free at higher cost rather than queueing. Good for peak handling without committing to short code lease.
• Short code for high-value flows, 10DLC for routine: Authentication for high-stakes transactions uses the short code (best delivery, best brand trust); signup OTP uses 10DLC for cost efficiency.
• 10DLC for US, toll-free for international US-fronted senders: Toll-free numbers route more reliably across borders than 10DLC long codes.

Message Central VerifyNow supports hybrid orchestration through a single API: declare preference order, and the platform routes per-OTP optimally.

Common A2P SMS mistakes for OTP

• Trying to scale on toll-free. Toll-free throughput tops out at 30 MPS. Past 100k OTP per month, migrate to 10DLC or accept significant queueing during peaks.
• Buying a short code too early. $500 to $1,500 monthly lease pays for a lot of 10DLC traffic. Only short-code if your math is solid.
• Mixing OTP with marketing on the same A2P route. 10DLC marketing campaigns can throttle OTP if shared. Isolate authentication traffic.
• Skipping number-pool sizing. A single 10DLC long code carrying 100,000+ OTP per day can hit per-number per-day caps. Use a number pool of 3 to 10 numbers.
• Not monitoring carrier-specific delivery. Issues often appear on one carrier first (typically AT&T or US Cellular). Per-carrier delivery dashboards catch problems early.

Frequently asked questions

Can I send A2P SMS in the USA without registering?

Technically you can attempt to, but carriers will filter the traffic aggressively. Delivery failure rates of 20 to 60 percent are typical for unregistered A2P. For OTP traffic, this is unworkable. Always register.

Can one business use 10DLC, toll-free, and short codes simultaneously?

Yes. Many large brands do. Each route requires its own registration and is operated independently. A2P providers like Message Central handle multi-route orchestration through a single API.

Do P2P SMS rules apply to A2P SMS?

No. P2P (person-to-person) and A2P (application-to-person) are separate regulatory categories. P2P does not require TCR registration. However, if you attempt to send A2P-like volume from a P2P number, carriers will reclassify and filter the traffic. The classification is enforced by behavior, not just by your declaration.

What is RCS and does it replace A2P SMS for OTP?

RCS (Rich Communication Services) is a richer messaging protocol that complements but does not replace SMS for OTP. RCS adoption in the USA has been slower than SMS; SMS remains the universal fallback. RCS is more relevant for marketing and conversational use cases where rich media matters.

Does Message Central VerifyNow support all three routes?

Yes. VerifyNow operates 10DLC (pre-approved routes for instant launch and dedicated campaigns for high volume), toll-free SMS, and short codes. Customers can choose per-flow or per-OTP. Hybrid orchestration is built in.

Start with pre-approved 10DLC today

Message Central VerifyNow USA ships with pre-approved 10DLC routes for under 5 minute launch, bundled carrier surcharges, SMS pumping protection, and multi-channel fallback. Toll-free SMS and short codes available for higher volumes.

For more context, see our SMS OTP Service USA hub, the 10DLC OTP SMS guide, the SMS Sender ID USA guide, and the SMS OTP Pricing guide. Free test credits, no credit card required.