Short answer: a dedicated short code is a 5- or 6-digit number leased exclusively to your business and provisioned for very high-volume, two-way SMS; 10DLC is a standard 10-digit long code whose daily throughput and deliverability are set by your registered brand and campaign through The Campaign Registry (TCR); a toll-free number is an 8XX number that is texting-enabled through a lighter verification process than short-code leasing. Pick the short code for national-scale programs where the number itself is a brand asset, pick 10DLC for most standard business messaging where TCR vetting is the price of deliverability, and pick toll-free when you want an 8XX caller-ID identity with two-way SMS attached and moderate volumes. The rest of this comparison is about which constraints are real and which are marketing.
The full definitions sit in the glossary: short code, A2P 10DLC. This post is about choosing between them.
What a short code actually is, and when it wins
In the US and Canada, a short code is a 5- or 6-digit number leased from the Common Short Code Administration (CSCA). It exists in two forms: dedicated, where one business holds the code exclusively, and shared, where multiple unrelated senders split a single code and replies route by keyword. For any serious program the dedicated form is the only sensible one — a shared code collapses your brand into someone else's on the handset, and the industry has been moving away from shared codes for years.
Where a dedicated short code genuinely wins:
- Very high-volume, two-way programs. Short codes are provisioned for throughput headroom well beyond what a registered 10DLC campaign or a toll-free number carries — tens of messages per second sustained. That includes heavily interactive traffic: OTP bursts, fraud alerts, two-factor authentication, and two-way customer threads where inbound replies matter as much as outbound.
- Brand trust and memorability. A 5- or 6-digit number is the sender identity itself — for a national loyalty program, a bank, or a retailer whose customers text a keyword, that memorability is a real asset, and it survives a carrier-level audit differently from a long code.
- Carrier vetting that is one-time and harder to inherit a bad reputation from. The vetting review covers the actual use case and message content before the code activates. It is slower than 10DLC registration, but once a dedicated code passes, its sender reputation is yours alone — not pooled with every other sender behind a shared SMS pool.
What that costs: a months-long provisioning lead, a per-month lease on the order of $500–$1,500 for a dedicated code depending on whether the digits are random or vanity, plus per-message rates comparable to other sender types, plus the carrier vetting process. For programs in the millions-of-messages-a-month range, that math often still wins on per-message economics.
Why buyers juggling 10DLC guides end up pivoting to short codes
Most US SMS guides assume 10DLC. It is the default sender type for standard business messaging, and properly registered it delivers well. But buyers who have read the 10DLC rejection breakdown — which says, correctly, that TCR throughput is capped per day per number and that the top tier requires a 75+ brand vetting score — sometimes conclude that 10DLC is a workaround rather than the right answer for their program.
The pivot to a short code usually happens at three inflection points: throughput planning shows the registered per-number cap will not hold the projected volume; the sender identity itself has to be memorable for a consumer program (text-to-join, text-to-donate, text-for-alerts); or the brand is large enough that the fixed short-code lease is noise against the risk of sharing sender reputation in a long-code pool. Toll-free sits between the two — branded 8XX identity, more manageable volume than a short code, and a lighter verification path than both — and it is often the right answer when the choice is not "short code or 10DLC" but "short code, 10DLC, or neither."
Cost and time-to-provision, side by side
| Dedicated short code | 10DLC (registered via TCR) | Toll-free (texting-enabled) | |
|---|---|---|---|
| Sender identity | 5- or 6-digit, memorable, exclusive | Standard 10-digit long code | 8XX number, recognizable |
| Throughput | Highest — tens of messages/second sustained | Capped per day per number by TCR tier (roughly 1,000 to 2,000,000 segments/day by vetting score and entity type) | Moderate — lower than a short code, above a long code's unregistered ceiling |
| Vetting / registration | Carrier review of the use case and sample messages, before activation | TCR brand + campaign registration; per-carrier approval tracked separately | Toll-free verification — lighter than both |
| Time to provision | Weeks to a few months | Typically 1–5 business days once the brand is clean | Days |
| Fixed cost | ~$500–$1,500/month lease | Registration fees only, no lease | ~$0–$5/month for the number |
| Two-way | Yes — dedicated, full keyword control | Yes | Yes |
| Best fit | High-volume two-way, enterprise brand programs | Standard business messaging — alerts, reminders, notifications | Branded 8XX caller-ID identity with texting attached |
Where Orbit's SMS API fits
The SMS API treats sender type as a per-message routing decision, not a product tier: register your 10DLC brand and campaign through the standard TCR flow, provision a dedicated short code where the program needs it, or enable a toll-free number, all against the same /v1/messages endpoint and the same delivery-receipt webhook stream. The sender-type comparison above is the buyer-level question; the platform-level answer is that it is one integration. Country-level SMS pricing is on the pricing pages, and the product surface is on the features/messaging page.
Frequently asked questions
Do I need a short code, or will 10DLC do?
Start with 10DLC unless you have a concrete reason it will not hold: a projected daily volume above your registered tier's per-number cap, a consumer program whose sender identity has to be a 5- or 6-digit number, or a hard requirement for exclusive sender reputation. For most standard business messaging — appointment reminders, delivery notifications, account alerts — registered 10DLC is the right default.
How long does it take to get a dedicated short code?
Weeks to a few months. The code is leased through the CSCA and then each carrier reviews the actual use case and sample messages before activation. That is a different, slower process from TCR registration, and it is the main reason to plan a short-code program ahead of a launch rather than react to a 10DLC cap mid-flight.
Is toll-free SMS just a cheaper short code?
Not exactly — it is a different sender identity with a different trust profile. A texting-enabled toll-free number carries moderate volume at a fraction of a short code's fixed cost and with a lighter verification path, but it does not carry the short code's top-end throughput, and the 8XX identity reads as a business line rather than a memorable program number. For branded customer-service traffic it is often the best fit; for national marketing programs it usually is not.
Can I run all three sender types from one SMS API account?
Yes, on Orbit. Registered 10DLC, a leased dedicated short code, and texting-enabled toll-free numbers all send through the same /v1/messages endpoint, with delivery receipts, inbound replies, and opt-out handling shared across sender types. The choice is about which sender identity fits the program, not which integration to build.
What does "shared short code" mean, and should I use one?
A shared short code is a single 5- or 6-digit number used by several unrelated businesses, each addressed by a distinct keyword. It exists on price, and it is a poor trade for a serious program: your sender identity is pooled with strangers, the carrier relationship is not exclusively yours, and the industry has been steadily retiring shared codes. A dedicated code, registered 10DLC, or a toll-free number are the three sender types worth choosing among.
Related reading
- The short-code glossary entry is the definitional version of this comparison — what a short code is, dedicated versus shared, and where the vetting process differs from 10DLC.
- The 10DLC registration debugging guide covers the rejection reasons that kill 10DLC campaigns at TCR — the registration path most buyers default to before reading the short-code math.
- The top SMS APIs compared buyer guide runs the four vendor-level checks — pricing model, network path, compliance and anti-fraud tooling, channel breadth — across ten providers, alphabetically.
- The SMS pumping fraud news explainer covers why sender-type choice and network path matter for fraud exposure, not just for throughput and cost.