Decorative title card illustration

For most U.S. marketing programs, 10DLC is the right starting point. Upgrade to a short code only when you need sustained high throughput, a nationally recognized sender identity, or a time-critical broadcast that cannot tolerate carrier-side queuing.

Here is the quick version of why that recommendation holds:

  • 10DLC costs less and registers faster. Brand and campaign registration through The Campaign Registry (TCR) typically takes days to a few weeks, and monthly number costs are a fraction of a short-code lease.
  • Short codes deliver higher throughput. A dedicated short code can handle hundreds of messages per second, far beyond what a single 10DLC number supports under carrier-set limits.
  • Both require registration to reach inboxes. Unregistered long codes are now filtered near-universally by U.S. carriers. CTIA’s Messaging Principles & Best Practices and TCR registration are the baseline for compliant A2P delivery.
  • The decision turns on volume, budget, and brand identity, not on which number type sounds more professional.

Key Takeaways

10DLC is the right default for most U.S. marketing programs; short codes are justified only when sustained high throughput or national brand identity is a genuine campaign requirement.

Point Details
Start with 10DLC Register through a CSP via TCR; it is faster, cheaper, and sufficient for most SMB programs.
Short code for extreme volume Use a dedicated short code when you need hundreds of messages per second or a nationally recognized 5-digit sender.
Registration is non-negotiable Unregistered long codes are filtered near-universally; TCR registration is required for consistent A2P delivery.
Follow CTIA consent rules Verifiable opt-in and easy opt-out are required for both number types under CTIA Messaging Principles.
Pulp AI Studio builds it for you Two-week scoped builds include number provisioning, consent flows, AI reply integration, and optional managed monitoring.

What is 10DLC, and how does it differ from a short code?

10DLC stands for 10-Digit Long Code. It is a standard 10-digit U.S. phone number registered specifically for Application-to-Person (A2P) messaging. Before 10DLC existed, businesses sent automated texts over ordinary long codes not designed for commercial traffic. Carriers responded by filtering that traffic aggressively. The industry’s answer was to create a sanctioned registration path: brands register with TCR, campaigns are tied to those brands, and carriers grant approved traffic better routing and deliverability.

US short codes are 5 or 6-digit numbers leased from the Common Short Code Administration (CSCA) and provisioned across all major U.S. carriers. Recipients see a short, memorable number rather than a 10-digit one. Short codes are built for volume: a single dedicated short code can process hundreds of messages per second, making them the standard choice for large-scale broadcast programs, national alerts, and high-frequency promotional sends.

Toll-free numbers occupy a middle position. They carry a national identity (an 800-series prefix), support moderate throughput above a single 10DLC number, and require their own verification process. They are worth considering for customer-service messaging or transactional notifications where a local-area-code appearance is less important than a recognizable national number.

A few quick distinctions worth keeping in mind:

  • 10DLC numbers show a local area code on the recipient’s screen, which can improve open rates for locally targeted campaigns.
  • Short codes appear as a 5 or 6-digit number, instantly recognizable as a business sender.
  • Toll-free numbers display an 800/888/877 prefix and support two-way messaging.
  • Only short codes and toll-free numbers support voice calls in addition to SMS; 10DLC numbers can also support voice, but their primary A2P registration is for messaging.

Short code vs 10DLC: a side-by-side comparison

Dimension 10DLC Short Code
Best for Local/regional campaigns, conversational flows, moderate volume, SMB marketing National broadcasts, high-volume alerts, brand-recognition campaigns, time-sensitive sends
Throughput Carrier-determined; typically low-to-moderate MPS per number, scalable with number pools Hundreds of messages per second on a dedicated code
Cost shape Low monthly number cost; one-time brand/campaign registration fee; per-message carrier surcharges High monthly lease; significant one-time provisioning cost; per-message fees
Registration & approval time Days to a few weeks via TCR and CSP Several weeks to months for carrier provisioning
Compliance/vetting Brand + Campaign registration through TCR; CSP submits on your behalf Carrier-by-carrier provisioning review; use-case and content vetting
Two-way messaging Supported; well-suited for conversational AI flows Supported but less common; typically used for one-way broadcasts
MMS/media support Supported on most carriers Supported; MMS throughput also higher
Sender appearance 10-digit local number (familiar, local feel) 5–6 digit code (recognized as business/brand)
Geographic/brand identity Local presence; area code signals regional relevance National identity; no geographic association

The practical effect of the throughput row is significant. AWS documentation confirms that 10DLC throughput limits are carrier-determined and that organizations needing the very highest throughput and cross-carrier consistency should consider a short code. For most SMB campaigns, the 10DLC throughput ceiling is not a constraint. For a retailer sending a flash-sale alert to 500,000 subscribers in under five minutes, it is.

How do you choose between 10DLC and a short code?

Work through these questions in order before you commit to provisioning:

  1. What is your monthly send volume? If you are sending tens of thousands of messages per month to segmented lists, 10DLC handles it. If you are pushing millions of messages in tight broadcast windows, a short code is worth the cost.
  2. Do you need national brand recognition? A 5-digit sender code is immediately understood as a business. A local area code can feel more personal but may not reinforce a national brand identity.
  3. How conversational is your program? Two-way flows, AI-driven replies, and appointment confirmations work well on 10DLC. Pure one-way broadcast programs are where short codes shine.
  4. What is your provisioning budget and timeline? Short-code provisioning can take several weeks to months. If you need to launch in two to four weeks, 10DLC is the only realistic path.
  5. Do you need MMS or rich media? Both support MMS, but confirm with your Campaign Service Provider (CSP) that your specific carrier mix supports the media type you plan to send.
  6. What are your compliance obligations? Both require opt-in consent and opt-out handling per CTIA guidelines. Short codes undergo additional carrier content review during provisioning.

When the answer to question 1 or 2 is clearly “extreme volume” or “national identity,” plan for a short code and budget the provisioning timeline into your campaign calendar. For everything else, start with 10DLC.

Pro Tip: Start your program on 10DLC, monitor your delivery rates and carrier trust scores for 60–90 days, and only initiate short-code procurement if you consistently hit throughput ceilings or your campaign strategy demands a national sender identity. Migrating later is straightforward; over-provisioning early is expensive.

Registration, fees, and approval timelines explained

10DLC registration through TCR

The Campaign Registry’s CSP user manual describes a three-layer model: your messaging vendor (the CSP) registers your Brand, then registers each Campaign under that Brand. Your Brand receives an alphanumeric Brand ID. Carriers use that ID to route your traffic with sanctioned status.

You do not register directly with TCR. SMBs and marketing teams register through their CSP or messaging platform. Attempting direct registration creates administrative friction and is not the supported workflow.

Common 10DLC fee components:

  • One-time brand registration fee (paid to TCR via your CSP)
  • Per-campaign registration fee
  • Monthly number lease (typically low per number)
  • Per-message carrier surcharges (vary by MNO)
  • CSP platform fees

Each carrier sets its own commercial terms. TCR provides a Carrier Terms Preview so you can review per-MNO rates before completing registration. That step is worth taking, because surcharge structures differ across AT&T, T-Mobile, and Verizon.

Short-code provisioning

Short-code provisioning runs through the CSCA and requires individual carrier approval from each major MNO. The process involves submitting a use-case description, sample messages, and opt-in/opt-out language. Carriers review and approve (or request revisions) independently, which is why provisioning timelines stretch to several weeks or months.

Fee components for short codes:

  • One-time setup/provisioning fee (higher than 10DLC)
  • Monthly lease fee (significantly higher than a 10DLC number)
  • Per-message fees
  • Potential carrier-specific surcharges

Incomplete documentation is the most common cause of provisioning delays. Submit your opt-in flow description, sample messages, and call-to-action copy in the first submission to avoid back-and-forth that adds weeks to your timeline.

Deliverability, carrier filtering, and CTIA compliance

Carrier filtering is the single biggest operational risk in A2P messaging, and the number type you choose directly affects your exposure to it.

The FCC has documented that carriers and aggregators identify messages by their originating identifier and apply blocking rules to traffic that appears fraudulent. Short codes and 10DLC numbers carry different blocking profiles. Registered 10DLC traffic receives sanctioned routing; unregistered long codes are filtered near-universally by U.S. carriers. That filtering reality makes TCR registration a practical requirement, not a formality.

Industry context: Americans exchange roughly 2.2 trillion text messages annually, and text messages carry a very high open rate. That reach is only accessible when your messages actually arrive.

CTIA’s consent-first model is the compliance foundation for both number types. The key requirements:

  • Obtain verifiable opt-in consent before sending any marketing message.
  • Include clear opt-out language (typically “Reply STOP to unsubscribe”) in every message or at program enrollment.
  • Honor opt-out requests immediately.
  • Encourage subscribers to report spam to 7726 (SPAM) if they receive unwanted messages.

Beyond the legal baseline, practical deliverability best practices include:

  • Review your sample messages before submission; carriers flag promotional language that looks like spam.
  • Avoid sudden traffic spikes; gradual ramp-up protects your trust score.
  • Monitor delivery receipts and complaint rates weekly, not monthly.
  • Keep message content consistent with the use case you registered.

For a detailed opt-in management checklist tailored to retail campaigns, the Pulp AI Studio blog covers the consent flow step by step.

Where do toll-free numbers and other long-code options fit?

Toll-free numbers are the most practical alternative when you want a national sender identity without the provisioning cost or timeline of a short code. They support moderate throughput, two-way messaging, and MMS, and they go through their own verification process that is generally faster than short-code provisioning.

Plain, unregistered long codes are no longer a viable option for A2P messaging in the U.S. Carrier filtering has made unregistered automated traffic effectively undeliverable. 10DLC replaced them as the sanctioned standard, and that shift is now complete.

A hybrid approach often makes the most sense for larger programs:

  • Toll-free for national customer-service and transactional messaging where a local area code is not relevant.
  • 10DLC for locally targeted marketing, conversational flows, and automated follow-up programs.
  • Short code reserved for peak broadcast events, emergency alerts, or campaigns where brand recognition from a 5-digit sender is a strategic requirement.

For a practical look at how short code vs 10DLC decisions play out in queue and customer-facing systems, the ezSeat team has documented real-world trade-offs worth reviewing.

How number type affects automated SMS and AI systems

When you are building an automated reply system rather than a one-way broadcast, the number-type decision has direct consequences for system architecture.

  1. Throughput and queuing. If your AI system sends acknowledgment messages within 30 seconds of a trigger (a missed call, a form submission, an after-hours inquiry), 10DLC throughput is almost always sufficient. The constraint is not the number type; it is the concurrency your webhook handler can sustain. Design your system to send a synchronous acknowledgment immediately and defer any heavy processing to an async queue.
  2. Delivery receipts and retry logic. Register webhook endpoints for delivery status callbacks with your CSP. If a message fails, your retry logic needs to distinguish a carrier filter event (do not retry the same content) from a temporary network failure (retry with backoff).
  3. Rate limiting. Even on a registered 10DLC number, sending bursts above your carrier-approved throughput triggers filtering. Build rate-limiting middleware that respects per-second limits and queues overflow rather than dropping it.
  4. Escalation rules. Conversational AI flows need a clean handoff path to a human agent when the AI cannot resolve a query. That handoff must preserve message history and not re-send an automated reply after the human takes over.

Pro Tip: Use a synchronous acknowledgment pattern: send a brief “Got your message, we’ll be right with you” reply the moment the trigger fires, then process the AI response asynchronously. This keeps the conversation warm even if the AI takes a few seconds to generate a substantive reply, and it protects your delivery reputation by keeping message volume predictable.

Pulp AI Studio builds these systems as scoped, two-week projects. The missed-call text-back system is the flagship build: a call goes unanswered, the caller receives an SMS within 30 seconds, the AI handles the conversation, and the owner gets an instant alert. The client owns the system outright. For healthcare practices, the automated medical answering workflow follows the same architecture with compliance-aware opt-in flows built in.

The case for starting local and scaling deliberately

The conventional advice is to pick the number type that matches your peak volume. That advice gets teams into trouble. Short-code provisioning timelines are long, costs are high, and a program that launches on a short code and then underperforms its volume projections has paid a significant premium for capacity it never used.

A more defensible approach: launch on 10DLC, treat the first 60–90 days as a trust-building period, and let your actual delivery metrics drive the upgrade decision. If you hit carrier throughput ceilings consistently, or if your campaign strategy genuinely requires a nationally recognized 5-digit sender, the short-code investment is justified. If you do not, you have saved the provisioning cost and the timeline risk.

The other thing practitioners underestimate is CSP responsiveness. During provisioning, especially for short codes, your CSP’s ability to respond quickly to carrier revision requests can mean the difference between a four-week launch and a twelve-week one. Ask your CSP directly: how many revision cycles have your recent short-code submissions required, and what is your average provisioning time? That answer tells you more than any spec sheet.

Pulp AI Studio builds compliant, automated SMS systems for small businesses

Most small businesses do not need a short code. They need a reliable, registered 10DLC number, a consent-aware opt-in flow, and an AI that handles the conversation when no one is available to answer. That is exactly what Pulp AI Studio delivers.

Every build includes number provisioning guidance, consent flow setup, webhook integration, and delivery monitoring, all scoped and live in two weeks. You own the rig outright. An optional managed plan covers ongoing tuning and reputation monitoring so your delivery rates stay healthy as your list grows.

If you are a clinic, dealership, contractor, or retailer who wants leads to stop going to voicemail, the after-hours AI answering system is the fastest path from missed call to booked appointment. Get in touch to scope your build.

Sources

FAQ

What is the difference between a long code and a 10DLC?

A standard long code is an ordinary 10-digit phone number not registered for commercial A2P traffic; carriers filter it aggressively when used for automated messaging. 10DLC is a registered long code, sanctioned through The Campaign Registry, that carriers route with approved status and better deliverability.

What is a US short code?

A US short code is a 5 or 6-digit number leased from the Common Short Code Administration and provisioned across all major carriers. Short codes are designed for high-volume broadcasts and can handle hundreds of messages per second, far above what a single 10DLC number supports.

Is 10DLC the same as a toll-free number?

No. 10DLC numbers display a local 10-digit area code; toll-free numbers display an 800-series prefix. They use separate registration and verification processes, carry different throughput profiles, and serve different use cases. Toll-free is a middle option between 10DLC and short codes for national-brand messaging.

Do I need to register my 10DLC number with TCR myself?

Small businesses and marketing teams should not register directly with TCR. Registration is handled by your messaging vendor or Campaign Service Provider, which submits your Brand and Campaign records on your behalf. Attempting direct registration creates unnecessary friction and is not the supported workflow.

Can I use an unregistered long code for business texting in 2026?

Not effectively. U.S. carriers now filter unregistered long-code A2P traffic near-universally. TCR registration through a CSP is a practical requirement for any automated business messaging program that needs consistent delivery.