Toll-free SMS means texting from an 8XX number (800, 833, 844, 855, 866, 877, 888) instead of a local 10-digit number or a 5-to-6-digit short code. These are the same numbers businesses have used for support lines for decades, enabled for text. They work for national brands, help desks and platforms that don't want a local area code on every message. They also come with a verification process of their own, separate from 10DLC, and carriers filter unverified toll-free traffic.
This guide covers what toll-free texting is, how verification works, what limits apply, and when a toll-free number is a better choice than a 10DLC local number or a short code. Some of the answer depends on your use case, so we also cover when toll-free is the wrong pick.
How toll-free SMS works
A toll-free number sends and receives SMS and MMS like any other number. The difference is in how carriers treat the traffic:
- No area code identity. The recipient sees an 8XX number. That reads as "national company" rather than "someone local." For a support line, that fits. For a local plumber following up on a quote, a local number usually reads better.
- Its own verification system. Toll-free numbers don't use the 10DLC brand-and-campaign registry. They go through toll-free verification, where you describe your business, your use case, how people opt in, and what you'll send.
- One number, one sender identity. A verified toll-free number is tied to the business and use case you submitted. You can't quietly repurpose a number verified for appointment reminders into a promo line.
Two-way texting works the same as any other number. People reply, text STOP, and get a conversation thread. Recipients' phones handle toll-free and short code senders a bit differently, though: some phones and carrier filters treat them as "unknown business" senders. We cover what recipients can do about that in why toll-free and short code texts are blocked and how recipients allow them.
Toll-free verification: what gets reviewed
Carriers filter unverified toll-free traffic. Unverified numbers are blocked or heavily restricted. Verification is the price of entry, and reviewers look at the same things a 10DLC campaign reviewer looks at:
- Business identity. Legal name, address, website and a business contact. The website should match the business you name and should describe what you actually do.
- Use case. Appointment reminders, order updates, customer support, account alerts, marketing. Be specific. "Notifications" alone is vague and invites questions.
- Opt-in flow. Where and how a person agrees to receive texts. Reviewers want to see it: a screenshot of the web form checkbox, the keyword ("Text JOIN to..."), or the point-of-sale wording. The consent language should name your business, say what kind of messages they'll get, mention that message and data rates may apply, and explain how to opt out.
- Sample messages. Two or three real examples that match the use case. Include your business name and STOP language in at least one.
- Expected volume. A monthly estimate. Keep it honest. An inflated number doesn't speed anything up, and a wildly wrong one can raise questions.
The common rejections mirror 10DLC rejections: an opt-in that can't be verified, sample messages that don't match the stated use case, a website that's down or generic, or content in a restricted category. If your samples were written by marketing and read like ad copy for a "notifications" use case, rewrite them. Our 10DLC rejection rewrite guide walks through sample-message fixes, and the same edits apply to toll-free submissions.
Review times for toll-free verification vary and aren't something any provider controls. Plan for days, not hours, and don't schedule a launch campaign the morning after you submit.
Throughput and limits
Toll-free numbers are often described as "higher throughput than local numbers." That was more true before 10DLC registration existed. Today, here is the practical picture:
- Per-second rate. A verified toll-free number starts at a modest per-second rate, a few messages per second, and higher rates are available on request for senders who justify them. For most businesses sending reminders or support replies, the default is plenty.
- Unverified traffic. Unverified toll-free numbers are effectively unusable for business sending. Don't count on it.
- Content filtering still applies. Verification doesn't exempt you from spam filters. Link shorteners, a URL in a first message to a cold number, and aggressive promo wording all get filtered on toll-free just as they do on 10DLC. Our post on why a link in your first text gets filtered applies here too.
For comparison, 10DLC throughput is tied to your brand's trust score. A fresh standard campaign typically runs about 1 to 4 segments per second. T-Mobile also applies a daily brand cap that starts around 2,000 messages a day at the lowest trust score and goes up to around 200,000 at the highest. Those are round approximations, since carriers publish no official rate card. Optional brand vetting ($79 Standard / $179 Enhanced, one-time) can raise the trust score. It only moves the daily cap if it crosses a tier.
Toll-free vs 10DLC vs short codes
| Toll-free (8XX) | 10DLC (local number) | Short code | |
|---|---|---|---|
| What the recipient sees | 800/833/844/etc. number | Local 10-digit number | 5 to 6 digit number |
| Approval process | Toll-free verification | Brand + campaign registration | Carrier short code application |
| Typical setup timeline | Days | Most approvals take 2 to 7 days | Weeks to months |
| Local feel | No | Yes, and local presence can match area codes | No |
| Throughput | Moderate, can be raised | Tied to trust score and use case | Highest |
| Ongoing cost | Number rental | Registration fees + number rental | Expensive lease |
| Best for | Support lines, national brands, one sender identity | Most businesses and platforms texting customers | Very high-volume national programs |
Short codes are the heavy-duty option. They are built for very high-volume national campaigns and OTP traffic at scale, but the lease and the provisioning timeline rule them out for most businesses. If you're not sure you need a short code, you almost certainly don't. For a broader breakdown that includes RCS, see 10DLC vs toll-free vs long code vs RCS.
When toll-free is the right choice
Toll-free fits well when:
- You're a national brand with a central support team. A single 8XX number on the website, in receipts and on the support page is easy to recognize. Customers texting "where's my order" don't care about the area code.
- You already publish a toll-free voice number. Text-enabling the number customers already know keeps one identity across call and text.
- Your use case is transactional or support-driven. Order updates, account alerts, ticket follow-ups and similar messages.
- You want one sender identity rather than many local numbers.
It's a weaker fit when:
- Local trust matters. A dentist, a contractor, a real estate agent, or anyone whose customers expect a local number. A local 10DLC number feels like a person. An 8XX number feels like a call center.
- You're a platform texting on behalf of many customers. Each of your customers needs its own sender identity and registration. That's what 10DLC sub-accounts are built for, with one brand and campaign per customer.
- You want to spread sends across local area codes. That's a 10DLC pattern.
How this maps to Ready
Ready's self-serve path is built around 10DLC. Each account or sub-account gets its own numbers and its own carrier registration, handled in-app. There's no setup fee. The charge at submit is the first month, $25. After that, the monthly cost is $25/mo for registration and $2 per number. Most approvals take 2 to 7 days. While you wait, an account can send up to 500 texts a month before registering, at its normal per-text rate. Our 10DLC explainer covers the registry in more detail.
If your use case points to toll-free, such as a national support line or an existing 8XX number you want to text-enable, email support@tryready.com with the use case and expected volume. We'll tell you plainly whether toll-free or 10DLC is the better route for you.
Ready also has a local presence feature that picks the registered number closest to the contact's area code. Its listed price is $0.0015 for each segment of a delivered text. Every number still sits on your registered 10DLC campaign, so local presence chooses among registered numbers and doesn't bypass registration. There's also the blue line (iMessage for business), which needs no 10DLC registration. It costs $99 a month per line plus 6 cents a segment, with up to 50 new conversations a day per line. Docs: blue line guide.
Worked example: cost of a reminder program
Assumptions: a clinic sends 2,000 one-segment appointment reminders a month (under 160 plain characters, no emoji) and gets about 600 one-segment replies.
- Segments: 2,000 sent + 600 received = 2,600. Replies bill like sent texts.
- Ready rate: 2,600 × $0.0075 = $20.
- Carrier fee: 2,600 × $0.0045 = $11.70, itemized.
- Registration with one number: $25 for registration + $2 = $27 a month.
- Total: $58.20 a month.
That all-in figure excludes the optional compliance surcharge. TCPA/DNC scrubbing and landline validation are each $0.003 extra per segment when switched on, and both are off by default.
On price per segment alone, raw CPaaS APIs like Twilio (about $0.0083/segment) and GoHighLevel's LeadConnector come in lower. What you get with Ready instead is registration handled in-app, STOP handling, quiet-hours holds, two-way inbox and the API under one account. Our Twilio alternatives comparison lays out the full tradeoff.
Compliance applies to every sender type
Neither toll-free verification nor 10DLC registration makes a send compliant on its own. Your obligations stay the same:
- Text only people who opted in, and keep your own record of when and how they did.
- Honor STOP immediately and everywhere.
- Respect quiet hours in the recipient's time zone.
- Keep cold outreach to phone and mail. SMS is for consented or replied leads.
Ready helps with the mechanics. Opt-outs propagate across campaigns, sends outside permitted local hours are held, and litigator/DNC scrubbing is available. The responsibility is still yours as the sender.
The practical takeaway
Toll-free SMS works well for national, support-style texting from one recognizable number, as long as you complete verification before you send. For most local businesses and for platforms texting on behalf of many customers, 10DLC is the more natural fit, and short codes are only for very high volume.
To start on the 10DLC side, your first 20 one-to-one texts are free. Use them before you register, since they end once a registration is paid for. Sign up and the registration flow is in the app. If you think toll-free fits better, email us your use case first.