Many businesses already own a toll-free number. It sits on the website, the invoices and the side of the van, so texting from it seems like the obvious choice. Then they find out that sending texts from a toll-free number takes a verification process, that unverified traffic gets blocked, and that "forward my texts" doesn't work the way call forwarding does.
This post covers how toll-free verification works, what reviewers reject, how text forwarding actually behaves, and when a 10DLC local number is the better choice. Ready's self-serve registration is built around 10DLC, so we'll say where that fits and where it doesn't.
What toll-free verification is and why it exists
US carriers treat business texting from toll-free numbers (800, 833, 844, 855, 866, 877, 888) as application-to-person traffic. That means they want to know who is sending and why. Toll-free verification answers that question. It plays the same role for toll-free numbers that brand and campaign registration plays for 10DLC local numbers.
Unverified toll-free traffic is blocked across the industry. A number that sends without verification isn't just slowed down. Its messages don't arrive. If you text-enable a toll-free number and start sending before verification clears, expect failures. For background on the sender type itself, see our explainer on what toll-free SMS is.
What a verification submission asks for
The exact form depends on your messaging provider, but submissions generally include:
- Business details: legal name, address, website, and a point of contact. Providers are increasingly asking for a business registration number such as an EIN, so have it ready.
- Use case: what you send. Examples are appointment reminders, order updates, two-way support or marketing.
- Sample messages: two or three real examples, including your business name and opt-out language.
- Opt-in workflow: how people agree to receive texts. Provide a URL or screenshot of the form, the checkbox or the keyword flow.
- Estimated monthly volume: a realistic number, not an aspirational one.
Why submissions get rejected
The same mistakes show up again and again:
- The opt-in proof doesn't match the use case. For example, you submit a checkout page for a marketing use case, and the checkbox only mentions order updates.
- The website doesn't support the business. A parked domain, a page with no privacy policy, or a site for a different business name.
- Sample messages are vague. "Hi, check out our deals!" doesn't say who is sending or how to stop.
- The content is restricted. Lending, debt, cannabis and similar categories get extra scrutiny or are refused outright.
- The volume is unrealistic. Very high volume from a business with no visible footprint gets flagged.
Most of these also apply to 10DLC. Our 10DLC opt-in examples work as a template for toll-free submissions too.
How long toll-free verification takes
There's no single published service level. Toll-free reviews commonly take anywhere from a few business days to a few weeks. Timing depends on the provider, the review queue and whether the first submission is clean. A rejection and resubmission can add as much time as the first review.
Plan for this before you need it. If you're launching a reminder program on a fixed date, submit early. Don't market the number for texting until verification clears.
For comparison, 10DLC registration on Ready is self-serve inside the app, and most approvals take 2 to 7 days. While your own registration is in review, an account that has already bought its number can send on Ready's shared registration at the same per-text rate. That shortens the gap between signing up and sending real messages.
Forwarding texts: why it isn't call forwarding
This is where most toll-free texting plans run into trouble.
Voice and text can live in different places
A phone number's voice routing and its messaging routing are separate. Your toll-free number might ring through a phone system (a cloud PBX, a call center tool), while texting is enabled through a different messaging provider. In general, a number can be text-enabled with one messaging provider at a time. Enabling texting somewhere new usually means moving the messaging side away from wherever it lives now.
So "forward my texts to my cell" isn't a setting the carrier flips. Texts go to whichever provider has the number text-enabled. That provider decides what happens next.
What forwarding looks like in practice
Once texting is enabled, inbound messages can usually be:
- Shown in an inbox. This is the provider's app or a shared team inbox.
- Pushed to your systems by webhook. Your server receives each inbound message and can route it to a CRM, a ticketing tool or an email.
- Relayed to email or a personal phone. This depends on the provider. It's often fragile for two-way conversations, because replies from your personal phone come from your personal number, not the business line.
On Ready, inbound replies land in the Inbox, and in GoHighLevel for connected accounts, where two-way sync is mapped per GHL location. Webhooks are built in for teams that want inbound messages in their own stack. The webhooks docs cover setup. Replies keep the conversation on the business number, which is usually what "forwarding" was meant to achieve.
One billing detail: on Ready, inbound replies are billed like sent texts, at the per-segment rate plus the carrier fee.
Toll-free vs 10DLC: a side-by-side
Neither sender type is universally better. Here's how they compare in practice:
| Toll-free | 10DLC (local number) | |
|---|---|---|
| Approval step | Toll-free verification per number | Brand + campaign registration |
| Typical approval time | Varies by provider; days to weeks | Most approvals take 2 to 7 days on Ready |
| Looks like | A national 8XX number | A local area code |
| Throughput | Set by provider and carrier; ask about the default | About 1 to 4 segments/sec for a fresh standard campaign; tens for higher tiers |
| Daily caps | Set by provider | T-Mobile caps by brand trust score (~2,000 up to ~200,000/day) |
| Best fit | An existing national brand number customers already know | Local businesses, platforms texting for many customers, conversational texting |
For a broader breakdown that includes short codes and RCS, see 10DLC vs toll-free vs long code vs RCS.
When toll-free makes sense
- Customers already recognize the number and you want texts and calls to share one identity.
- You're a national brand with no reason to look local.
- Your phone system already has the number text-enabled and verified, and it works. If that's your situation, keep it. Migrating a working setup for its own sake is wasted effort.
When 10DLC is the better pick
- You text on behalf of many businesses. 10DLC gives each sub-account its own brand, campaign and numbers.
- You want conversations to feel local. With Local presence on, Ready sends from the account number closest to the contact's area code. Every number still sits on your registered 10DLC campaign.
- You need a predictable approval path inside one app instead of a ticket with a phone vendor.
One more point: some recipients' phones filter or hide texts from non-local senders. Our guide on why toll-free and short code texts get blocked explains what recipients see.
What 10DLC costs on Ready, worked out
Ready's self-serve path is 10DLC. Here's the math so you can compare it with your toll-free quote.
Registration. There's no setup fee. At submit you pay the first month, $25. After that, the monthly cost is $25/mo for registration + $2/mo per number. One brand, one campaign and two numbers come to $29/mo.
Messages. The Standard rate is $0.0075 per segment plus a $0.0045 carrier fee per segment. That flat rate doesn't change with volume.
Example assumptions: 2,000 appointment reminders a month, each under 160 plain characters with no emoji, so 1 segment each.
- Rate: 2,000 × $0.0075 = $15
- Carrier: 2,000 × $0.0045
- Replies: each reply is billed the same way, so add them if you expect two-way traffic
That all-in figure excludes the compliance surcharge. TCPA/DNC scrubbing and landline validation are each $0.003 extra per segment when switched on, and both are off by default. Add an emoji to that reminder and a 140-character text becomes 3 segments, tripling the message line. The full fee breakdown is in 10DLC cost: every fee explained.
To be clear about price: raw CPaaS APIs like Twilio (around $0.0083/segment) and GoHighLevel's LeadConnector (around $0.0083/message) charge less per message. What you get with Ready is self-serve registration, STOP handling that propagates across campaigns, quiet-hours holds and the inbox in one place. Some teams care more about those than about the per-segment price.
If you need to start before approval
There are three options while you wait:
- Send under the pre-registration allowance. A Ready account can send up to 500 texts a month before registering, at its normal per-text rate. The first 20 texts are free one-to-one sends. Use them before you pay for registration, because the free texts end when a registration is paid. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it.
- Use the shared registration while yours is in review, as described above.
- Add a blue line. A blue line sends iMessage to iPhones with your business name and photo, and needs no 10DLC registration. It costs $99/mo per line plus 6 cents per segment, with up to 50 new conversations a day per line. Android contacts get texts from your regular number. It suits conversational outreach, not campaigns. Campaigns send from regular numbers.
The practical takeaway
If your toll-free number is already verified and texting well, keep using it. If you're starting from scratch, the decision usually depends on two questions. Does your audience need to see a familiar national number, or a local one? And do you want to wait on a toll-free review, or register 10DLC in-app with most approvals taking 2 to 7 days?
Whichever path you choose, the submission is the same work: a real website, clear opt-in proof, honest samples and realistic volume. Compliance stays the sender's responsibility. Tools reduce risk, but they don't remove it.
If 10DLC fits your use case, you can create an account, send your first one-to-one texts, and start registration from the app. If you specifically need a toll-free sender on Ready, email support@tryready.com first to confirm what's available before you build plans around it.