Quick answer: US A2P messaging runs on three sender-number categories, and the choice is a capacity-and-identity decision, not a price decision. A toll-free number (TFN) — a texting-enabled 8XX — carries branded one-to-many traffic at moderate-to-high volume behind a lighter sender-verification flow. A 10DLC — a standard 10-digit local number — is the two-way business sender whose daily throughput is set by your Brand and Campaign registration at The Campaign Registry (TCR). A short code — a dedicated 5- or 6-digit number — is the burst-throughput sender for national programs, two-factor authentication floods, and emergency-notification spikes where per-second capacity and sender memorability are the constraint. Devotel Orbit provisions all three from one Numbers surface against the same /v1/messages endpoint, so the pick is about which sender identity the program needs, not which integration to build. This post is the chooser: one decision table, then the verification flow per type, then the tenant-owned controls that stay yours whichever type you send on.
The decision table — volume, deliverability class, vertical regulation
Start with the two numbers that decide almost everything: your projected peak throughput and whether the traffic is one-to-many (notifications, alerts, marketing) or two-way (conversational replies, support threads). The third axis is vertical regulation — healthcare, financial services, and political traffic each carry extra vetting regardless of sender type.
| Toll-free (TFN) | 10DLC | Dedicated short code | |
|---|---|---|---|
| Sender identity | 8XX number — recognizable, brand-forward | Local 10-digit number — familiar, regional | 5- or 6-digit — the program identity itself |
| Traffic profile | One-to-many A2P at moderate-to-high volume | Two-way local A2P — support, alerts, reminders | Burst A2P — OTP floods, emergency notification, national campaigns |
| Throughput | Higher than an unregistered long code, below a short code | Per-day, per-number cap set by TCR vetting tier (~1,000 to ~2,000,000 segments/day) | Highest — tens of messages per second sustained |
| Verification gate | Toll-free sender verification (lighter than TCR) | TCR Brand + Campaign registration, vetted per carrier | Carrier-network approval, use case and samples reviewed before activation |
| Time to provision | Days | Typically 1–5 business days once the Brand is clean | Weeks to a few months |
| Two-way | Yes | Yes — the two-way default | Yes — full keyword control |
| Best fit | Branded customer-service and notification traffic with an 8XX identity | Standard business messaging where local presence matters | Programs where throughput or sender memorability is the constraint |
Two rows worth reading slowly. First, throughput on 10DLC is per number, per day — the tier table in the TCR walkthrough is per-number, so the campaign ceiling is tier × assigned numbers, and a Standard-tier campaign that needs more headroom adds numbers rather than changing sender type. Second, toll-free and short code are not "registered 10DLC alternatives" — they are different sender identities with different trust profiles. A TFN reads as a business line; a short code reads as a program.
Verification flow per type — what actually gates each sender
Every US sender type has a verification gate; what differs is who vets it and how long it takes. Skipping the gate is not an option on any of the three — unverified traffic filters, throttles, or blocks. Here is what each flow actually asks for.
Toll-free verification. A texting-enabled TFN goes through a sender-verification submission: the sending entity's business identity, the use case, and how recipients opt in. It is a lighter review than 10DLC registration or short-code approval — no separate Campaign filing, no per-use-case sample-message vetting — and it typically clears in days once the business record is consistent. The gate exists; it is shorter, not absent.
10DLC through The Campaign Registry. 10DLC is two filings with TCR — the Brand (your legal entity, vetted against tax-record fields) and the Campaign (your use case, vetted against sample messages and a narrated opt-in/opt-out flow). The full field-by-field walkthrough is the 10DLC registration TCR walkthrough, and the debugging half — the rejection reasons that kill first submissions, from EIN mismatch to missing opt-out language to political-vertical token requirements — is the 10DLC campaign rejections and TCR vetting breakdown. Those two posts are the register-here-first and fix-it-when-it-rejects pair; this chooser just names which flow you are in.
Short code through carrier-network approval. A dedicated short code is leased through the Common Short Code Administration (CSCA) and then approved carrier by carrier: each network reviews the actual use case and sample messages before activation. It is the heaviest gate of the three — weeks to a few months — and it is also the strongest sender identity once approved, because the vetting is one-time and the sender reputation is exclusively yours rather than pooled.
Tenant-owned controls in Orbit — what stays yours on every sender type
Whichever number type you provision, the controls that determine whether verification sticks and whether traffic stays deliverable are tenant-owned. Orbit surfaces them in one place so the sender-type choice above does not change your operating model.
The number-type chooser lives at Channels → Numbers in the dashboard: buy a local number and it enters the 10DLC registration path; enable a toll-free number and it enters toll-free verification; order a dedicated short code and it enters the carrier-approval pipeline. All three resolve to numbers on the same account, send through the same /v1/messages endpoint, and report through the same delivery-receipt webhook stream — the chooser is a routing-surface decision, not an integration decision.
The tenant-owned controls that apply on every type:
- Brand and campaign metadata. The entity fields TCR vets, the use case and sample messages a campaign files, and the opt-in narrative a reviewer reads all come from your tenant's own registration record. Keep the legal name character-for-character against the tax document and the sample messages copied from real sends — both posts above trace most rejections to one of those two fields.
- Sender-key hygiene. The sender keys and credentials behind each channel are tenant-owned: they live under Settings → Channels per channel, they are never passed on a per-message request, and rotation is a tenant-side operation. A sender whose key management is sloppy is a sender whose verification gets re-litigated.
- Consent proofs. Every sender type's verification asks how recipients opt in and how they revoke. The consent record — grant, revocation, proof pointer — is the tenant-owned evidence that answers it, whatever the sender identity. The KYC documents CPaaS customers need post covers the document tier per sender category, and the number regulatory preview and CNAM post covers how a tenant previews the regulatory posture of a number before it goes live.
The carrier-of-record hub at /compare/carrier-of-record runs the ownership row per vendor — on Orbit, the numbers you register terminate on infrastructure the same company operates, so the verification record and the sending reputation live behind one accountable operator rather than a reseller's upstream.
The migration chord — moving between number types without re-architecting
Most migrations are 10DLC ↔ TFN: a program that started on local long codes moves a branded notification stream to a toll-free sender, or a toll-free-first program adds local numbers for two-way support. On Orbit that is a Numbers-surface change, not a code change — the sending code, the DLR webhook, and the opt-out handling are identical across sender types, so the migration is provisioning plus verification, not re-integration.
The regulatory preload is the real migration cost. Moving a traffic class between sender types means filing the new verification (TCR Campaign, toll-free verification, or carrier approval) against the same use-case narrative, and the narrative is only as clean as the consent and content records behind it. Programs that treat the 10DLC registration walkthrough as a one-time chore re-learn it during migration; programs that keep campaign drafts aligned with what was actually registered swap sender types by re-filing the same honest story against a new number. The KYC and sender-ID checklist is the preload document for that — the documents and consent evidence assemble once and re-use across sender categories.
Frequently asked questions
Which number type should a new US A2P program start on?
Start with the traffic profile, not the price. Two-way business messaging — appointment reminders, support replies, account notifications — defaults to registered 10DLC. One-to-many branded notification traffic where an 8XX identity helps defaults to toll-free. Only reach for a short code when the projection shows 10DLC's per-number daily cap or toll-free's envelope will not hold the peak, or when the sender identity itself must be a memorable 5- or 6-digit number.
Can one account run all three sender types at once?
Yes. On Devotel Orbit, registered 10DLC numbers, verified toll-free numbers, and a dedicated short code co-exist on one account and send through the same /v1/messages endpoint with shared delivery receipts, inbound replies, and opt-out handling. The sender-type choice is per-program; the integration is once.
How does vertical regulation change the choice?
Healthcare, financial-services, and political traffic add vetting on top of whichever sender type you pick: political campaigns on 10DLC need a Campaign Verify token, and regulated verticals face closer sample-message review on every flow. The sender-type decision still resolves to throughput and identity; the vertical overlays the verification flow, not the chooser.
What happens to deliverability if I skip verification?
Unverified traffic filters, throttles, or blocks at the carrier — this is true on all three sender types. Verification is the deliverability gate, and the TCR vetting and rejections post is the reference for reading a rejection rather than guessing at it.
Related reading
- The 10DLC registration TCR walkthrough — the field-by-field Brand and Campaign registration path, and the rejections companion at 10DLC campaign rejections and TCR vetting.
- The short codes vs 10DLC explainer — the deeper throughput-and-cost comparison this chooser's short-code row summarizes.
- The KYC documents CPaaS customers need — the document and consent-evidence tier that preloads a number-type migration.
- The number regulatory preview and CNAM — how to preview a number's regulatory posture before it carries traffic.