10DLC vs toll-free vs short code: which should your business text from?
13 min readProvider docs read 2026-10-22
For the owner or ops lead picking a number to text customers from: how a local 10DLC number, a toll-free number and a short code each get approved, how long it takes, how fast they send, who handles STOP, and which one fits a small business. Every time and limit is a provider's own published figure from Twilio, Bandwidth, Telnyx or CTIA, read on 2026-10-22.
The short answer
A business can text US customers from software over three kinds of number. Each one has its own approval path, and none of them skips approval. For most small senders the real choice is between a local 10DLC number and a toll-free one; a short code is for programs that need volume above everything else.
The three routes side by side
Twilio keeps one table of the three US texting routes, and it is the clearest place to start. The rows below follow it, with Bandwidth's and Telnyx's published figures added where they differ. Every time and speed is the provider's own statement, read 2026-10-22, not a promise.
| Point | 10DLC (local number) | Toll-free | Short code |
|---|---|---|---|
| The number | 10 digits with a local area code | 10 digits starting 800, 888, 877, 866, 855, 844 or 833 | 5 or 6 digits, leased |
| Approval | A brand and a campaign with The Campaign Registry, filed by your provider | Toll-free verification, one form per number, filed with your provider | A short code application and campaign brief, reviewed by each carrier |
| How long, per the provider | Brand: minutes to over seven days (Twilio). Campaign: immediately (Bandwidth) to several weeks (Twilio) | About 3–5 business days (Twilio), up to 5 (Bandwidth), 1–2 weeks (Telnyx) | 6–8 weeks of carrier review for a new code, after the brief (Bandwidth) |
| Throughput | Set per carrier by brand type and vetting score | 3 segments a second by default at Twilio, can be raised | 100 messages a second by default at Twilio, can be raised |
| STOP handling | Your provider's job (Twilio does it by default; Bandwidth leaves it to you) | Enforced by the network as well as the provider | Your provider's job; Twilio does not do it by default |
| Voice calls | Yes | Yes | No |
| Delivery receipts | From the carrier | From the handset | From the handset |
| Long texts split into | 153 characters a part (67 in Unicode, say with an emoji) | 152 a part (66) to the US and Canada | 153 a part (67) |
“Toll-Free numbers and short code numbers aren't part of the A2P 10DLC system and can also be used for messaging end-users in the United States.”
That sentence is why the routes are not interchangeable paperwork. A toll-free number never touches The Campaign Registry, and a short code goes through CTIA's Short Code Registry and the carriers instead. The 10DLC process itself, with its brand types and use cases, is laid out in what is 10DLC.
Registration: a brand and campaign, or one verification form
The two common routes ask for much the same evidence in a different shape. 10DLC splits it in two: the brand says who you are, the campaign says what you send. Toll-free verification asks for both on one form per number. In both cases your provider files it; Twilio's toll-free numbers “can't send SMS messages to the United States and Canada” until it approves.
| Part | 10DLC (brand + campaign) | Toll-free verification |
|---|---|---|
| Who you are | Legal name and EIN exactly as on the IRS letter, address, website, a support contact | Business name, website, entity type, address and a business registration number (the EIN in the US); a contact whose email matches the company |
| What you send | A campaign use case and a description | One or more use case categories and a use case summary |
| Sample texts | Sample messages that match the use case | Production message samples (Bandwidth asks for one to three) |
| Proof of opt-in | How people opt in, the opt-out and HELP replies | The opt-in type (web form, paper form, keyword, QR code, verbal, import) and a public link to an image of it |
| Volume | Set by brand type and vetting, not declared | An estimated monthly message volume |
| Policies | Privacy policy and terms links | Privacy policy and terms links; Bandwidth lists what each must say |
| Extra checks | Authentication+ for public for-profit brands; optional third-party vetting | The registration number is checked against official records automatically (Bandwidth: in seconds) |
Toll-free reviewers read the opt-in hardest. Bandwidth's handbook calls insufficient opt-in information “a common cause for rejection” and wants the image to show the form itself, or for a verbal opt-in a script of the exchange. Marketing needs its own opt-in even when the number also sends receipts. Telnyx's list of rejection reasons reads the same way: a business name that does not match public records, samples that do not match the use case, samples without opt-out wording, an opt-in nobody can follow. The SMS opt-in language builder writes the disclosure, and the SMS privacy policy generator the page reviewers open.
Short codes: a brief, then the carriers
A short code is leased, not registered. CTIA's Short Code Registry describes three steps: pick a five- or six-digit code, lease it and find a partner, then “develop your campaign and submit with your partner. Once approved, launch it.” Bandwidth's brief asks for a program summary, the call to action, the message flows (opt-in, confirmation, opt-out, HELP) and a terms link, and its integration must answer HELP and STOP before carrier testing starts.
How long approval takes, provider by provider
There is no industry clock. Each provider publishes its own figure, and they differ by a week or more for the same route. These are their words, side by side.
| Provider | 10DLC | Toll-free verification |
|---|---|---|
| Twilio | Brand: most within minutes, a few over seven days. Standard campaign vetting: up to several weeks | Help centre: about 3–5 business days. API docs: within three business days |
| Bandwidth | Brand: verified or unverified within an hour. Standard use cases: immediately; special ones up to a few weeks | Reviewed by hand, up to 5 business days |
| Telnyx | Vetting: 1–7 business days | Typically 1–2 weeks |
A short code is a different order of wait. Bandwidth's handbook puts carrier review of a new code at 6–8 weeks, after up to three weeks on the brief, and says plainly that “there's no expedite process.” A business that needs to text next month does not start here.
“As of January 31, 2024, messages sent from any unverified (Restricted or Pending) Toll-Free phone numbers (TFPN) are blocked. Only fully verified Toll-Free phone numbers are eligible to send messages.”
Throughput, filtering and delivery receipts
The routes meter speed in different units, which is why a straight comparison is hard. 10DLC caps a brand per carrier: T-Mobile by messages a day, AT&T by messages a minute per campaign, both set by the vetting score. Toll-free and short codes are metered per second.
On toll-free, Twilio sends 3 segments a second by default once a number is verified and sells a high-throughput option above that. Telnyx says verification unlocks “full sending capabilities (up to 20 MPS)”. Bandwidth goes further: there are “no CTIA or industry restrictions” on high-volume use of a toll-free number, which “isn't throttled on a per-phone-number-outbound basis”, only by the account limit in your contract. A short code starts at 100 messages a second at Twilio. The 10DLC tier tables are in what is 10DLC.
For a business sending a few hundred reminders a day, any route is fast enough. Speed starts to matter for a flash sale to a large list, where three segments a second comes to 10,800 an hour, and a small business's AT&T class on 10DLC allows 75 a minute.
“Verification is not whitelisting, but it helps expedite the resolution of blocking issues when traffic aligns with the verification application.”
Trust works the same way on every route: approval lowers filtering, it does not switch it off. Bandwidth calls a verified toll-free number one with “minimal traffic filtering”, and Twilio says verified numbers keep a reduced risk of filtering “as long as you adhere to your stated use case”. One difference is in the reporting. Twilio's table lists delivery receipts from the handset on toll-free and short codes, but only from the carrier on 10DLC, so a toll-free sender learns whether the phone itself received the text.
STOP works differently on toll-free
On a US toll-free number, the opt-out is enforced before your software sees it. Vonage puts it in one line, and Twilio and Bandwidth say the same.
“for Toll-free numbers (TFN) in the USA, STOP messages and opt-out functionality are managed automatically at a network level, enforced by the US operators. There is no need to enable this service, and it cannot be disabled.”
| Route | Who blocks after STOP | What the providers say |
|---|---|---|
| 10DLC | Your provider, if it offers it | Twilio blocks after STOP and its other default keywords on long codes; Bandwidth does not handle opt-outs on long codes at all |
| Toll-free | The network, and your provider | A STOP reply always unsubscribes (Twilio); it cannot be switched off (Vonage); Bandwidth's network layer also reads STOP in French (ARRET) |
| Short code | Your own program | Twilio does not keep the opt-out list by default; Bandwidth requires the program to answer HELP and STOP itself |
Two consequences follow. A custom opt-out reply is not reliable on toll-free: Twilio says its Advanced Opt-Out message “will not display” after STOP there, and that START or UNSTOP opts the person back in, so tell toll-free audiences those words. And the list is still yours: Bandwidth says “the onus of honoring these commands and maintaining opt-in and opt-out lists lies with the customer.” The full keyword set is in SMS opt-out keywords.
What you pay for on each route
The parts differ more than the totals. 10DLC adds The Campaign Registry's fees on top of the number; toll-free has no registry fees; a short code is a lease. Every route pays a per-segment price and a carrier fee on top: Twilio's price page lists carrier fees for toll-free traffic as well as for local numbers.
| When you pay | 10DLC | Toll-free | Short code |
|---|---|---|---|
| Before the first text | Brand registration, optional vetting, a campaign vetting fee | Verification itself: free at Bandwidth, no fee named by Twilio | The lease's setup fee |
| Every month | Number rent and a fee per campaign | Number rent, higher than a local number's at Twilio | The lease, billed quarterly at Twilio |
| Per segment | Provider rate plus a carrier fee | Provider rate plus a carrier fee | Provider rate plus a carrier fee |
The figures change by provider and by quarter, so they live in one place on this site: the 10DLC registration cost calculator for the registry and carrier fees across five providers, and Twilio SMS pricing for one provider's full bill, including the toll-free number rent and the short code lease.
Long texts cost slightly more on toll-free. Twilio bills per segment, and while a long text on a local number splits into parts of 153 characters (67 once a single character forces Unicode), toll-free multi-part texts to the US and Canada carry 152 and 66. A text written to fill exactly two parts on 10DLC can need three on toll-free; the SMS segment counter counts both.
Calls, local presence and what the number can carry
The number is also your business's face on the customer's phone. Twilio's own price list sums up the three: a long code is “a 10-digit number for SMS and voice calls with localized identity”, a toll-free number is for “high-throughput SMS and voice calls”, and a short code is for “high-throughput two-way SMS messaging”, with no calls.
So a plumber, a clinic or a salon whose customers call back the number that texted them wants a local number or a toll-free one, never a short code. A local area code reads as a neighbour; a toll-free prefix reads as a national company. A toll-free number already used for calls can usually start texting: Bandwidth says it can text-enable an existing toll-free number held elsewhere with a letter of authorization from the number's RespOrg, and it still goes through verification. A short code also stops at the border: Twilio says sending in both the US and Canada takes two codes, one in each country.
How many numbers you may use differs too. Bandwidth wants each sender on “only one primary sending number” on toll-free, one per location for a franchise, and calls spreading the same texts across many numbers “snowshoeing”, a spam technique that gets messages blocked. On 10DLC, T-Mobile caps a campaign at 49 numbers unless a number pool is approved.
What toll-free will not carry
Toll-free verification turns some businesses away outright. Bandwidth's handbook lists use cases “not eligible for Toll-Free Verification”, among them payday, auto, mortgage and student loans, debt collection and consolidation, credit repair, gambling, sweepstakes, cannabis, alcohol, tobacco and vaping, and firearms. A mortgage broker or a liquor store that reaches for a toll-free number will be refused at verification; check how your provider treats that content on 10DLC before building on it. Some content is closed everywhere: Twilio forbids cannabis and third-party lead generation on every US route.
Switching providers: what follows the number
A port moves the number. Whether the approval moves with it depends on the route, and for toll-free on which provider you ask.
“currently there is no way to transfer toll-free verifications between providers. In order to minimize any downtime, we highly recommend submitting your verification request as soon as the porting process completes for your number.”
Twilio adds that the number's traffic “should remain treated as Verified” until the new submission is reviewed, and that a request filed before the port completes may be rejected (error 30447). Bandwidth reads it the other way round: verified toll-free numbers “retain their status after porting”, but it strongly encourages a fresh verification so it has the campaign on file, and says that filing will not put the number into Pending. Either way, plan a new verification for the day the port lands.
Short codes are stricter. Bandwidth says each migration “is subject to a re-approval process” with the carriers, quotes 4–6 weeks, and warns the carriers do not approve in step, so run both providers in parallel until all of them have. The rest of a provider move, including 10DLC campaigns and opt-out lists, is in Twilio alternatives.
Which route fits your business
Six answers settle most cases. Each one marks a route Fits, With limits or Does not fit, from the rules quoted on this page; the best match is the route with no “does not fit” and the most points.
Score the three routes against your business
10DLC fits your answers best.
| Your answer | 10DLC (best match) | Toll-free | Short code |
|---|---|---|---|
| Volume | FitsA Low-Volume Standard brand covers up to 2,000 segments a day to T-Mobile (Twilio). | FitsWell inside 3 segments a second, Twilio's default. | With limitsWorks, but you pay for speed you will not use. |
| Calls on the same number | FitsLocal numbers take calls and texts (Twilio). | FitsToll-free numbers take calls and texts (Twilio). | Does not fitShort codes cannot take voice calls (Twilio). |
| Local area code | FitsA 10-digit number with your local area code. | Does not fitAlways an 8NN prefix such as 800 or 855, never a local code. | Does not fitFive or six digits, no area code at all. |
| Start date | FitsTime enough for a brand, vetting and a campaign. | FitsTime enough, even after a rejection and a fix. | With limitsTight: up to 3 weeks on the brief, then 6 to 8 weeks with the carriers (Bandwidth). |
| What you send | FitsAccount notifications, customer care, delivery and 2FA are standard use cases. | FitsReminders, alerts, 2FA and status updates are on Bandwidth's toll-free list. | FitsBandwidth names 2FA among common short code campaigns. |
| Tax ID | FitsA Standard or Low-Volume Standard brand. | FitsThe EIN goes in the registration number field. | FitsCompany details on the application. |
| Score | 12 of 12 | Ruled out | Ruled out |
Two points a fit, one a limit; any “does not fit” rules a route out. Read 2026-10-22 from Twilio, Bandwidth and Telnyx pages.
Whichever wins, the registration form will ask how people opted in, and the answer has to be true. Marketing texts need prior express written consent on every route, and the rest of the texting law is in TCPA rules for text messages. To pick the provider that files the route for you, compare SMS API providers or, for a ready-made app, SMS marketing software, several of which send from toll-free numbers by default. This page compares sending routes from the providers' published rules; it is not legal advice.
Questions owners ask
Is toll-free easier than 10DLC for a small business?
It is one filing instead of two. Toll-free verification is a single form per number, sent through your provider: business details, use case, sample messages and proof of how people opt in. 10DLC asks for a brand and then a campaign through The Campaign Registry. Approval times are close: Twilio quotes 3 to 5 business days for toll-free, Bandwidth up to 5, Telnyx 1 to 2 weeks, while 10DLC runs from minutes for a brand at Twilio to several weeks for some campaigns. Toll-free gives up the local area code, and some content is not accepted at all.
Does a toll-free number avoid the 10DLC fees?
It avoids The Campaign Registry's fees, because toll-free numbers sit outside the 10DLC system. Bandwidth calls toll-free verification a free process, and Twilio's verification article names no fee. You still pay the number's monthly rent and the per-segment prices, and Twilio's price page lists per-message carrier fees for toll-free traffic too. The 10DLC registration cost calculator and the Twilio SMS pricing guide on this site carry the figures.
Can I text from the toll-free number we already use for calls?
Usually, once it is verified for messaging. Bandwidth says it can text-enable an existing toll-free number held elsewhere with a letter of authorization from the number's RespOrg, and Twilio's comparison table lists both local and toll-free numbers as able to take voice calls. A short code cannot take calls.
Do I need a short code for marketing texts?
No. Marketing is a use case on all three routes: a 10DLC Marketing campaign, a toll-free verification with the marketing category, or a short code program. Each one still needs prior express written consent for marketing texts. A short code makes sense for volume and speed, not for permission.
If customers reply STOP to a toll-free number, am I covered?
Only for the keyword. On a US toll-free number the network blocks further texts after STOP, and START or UNSTOP lets the person back in. A reply in other words, such as "please stop texting me", is not caught by the network, yet the FCC rule counts any reasonable method and gives you 10 business days to honour it. Keep your own opt-out list and update it from every reply.
Does toll-free verification move with the number when I switch providers?
The providers answer differently. Twilio says verifications cannot transfer between providers, so you submit again once the port completes, and that the number's traffic should stay treated as verified until the new submission is reviewed. Bandwidth says verified numbers keep their status after porting but asks for a new verification so it has the campaign on file. Ask both sides before you set a port date.
Sources
- Twilio Help Center: Differences between long codes (A2P 10DLC), short codes and toll-free numbersfetched 2026-10-22
- Twilio Help Center: Toll-free message verification for US/Canadafetched 2026-10-22
- Twilio Docs: Toll-free verification console onboarding guidefetched 2026-10-22
- Twilio Docs: Toll-free verification using the API (fields, review time)fetched 2026-10-22
- Twilio Docs: Programmable Messaging and A2P 10DLCfetched 2026-10-22
- Twilio Docs: Advanced Opt-Out (toll-free behaviour)fetched 2026-10-22
- Twilio Docs: What is the SMS character limit?fetched 2026-10-22
- Twilio: SMS pricing in the United States (number types, carrier fees)fetched 2026-10-22
- Bandwidth: Toll-free verification handbookfetched 2026-10-22
- Bandwidth: Toll-free verification guide (page dated 2026-09-15)fetched 2026-10-22
- Bandwidth: Toll-free verification business registration number requirementsfetched 2026-10-22
- Bandwidth: Per-number rate limits on toll-freefetched 2026-10-22
- Bandwidth: Text-enabling an existing toll-free voice number (page dated 2026-05-26)fetched 2026-10-22
- Bandwidth: Why use a single toll-free numberfetched 2026-10-22
- Bandwidth: Does Bandwidth handle opt-in and opt-out keywords?fetched 2026-10-22
- Bandwidth: Short code handbook (page dated 2026-02-09)fetched 2026-10-22
- Bandwidth: 10DLC FAQfetched 2026-10-22
- Telnyx: Toll-free verification with business registration fieldsfetched 2026-10-22
- Telnyx: Toll-free verification troubleshootingfetched 2026-10-22
- Telnyx: 10DLC quickstartfetched 2026-10-22
- Vonage: Enabling Opt-Out Assist (toll-free note)fetched 2026-10-22
- CTIA: Short Code Registryfetched 2026-10-22
- 47 CFR § 64.1200, Delivery restrictions (eCFR, current as of 2026-10-20)fetched 2026-10-22