Toll-Free Verification for Business Texting Explained

Toll-free verification is the review a business must pass before it can send text messages from a toll-free number (800, 888, 877, 866, 855, 844 or 833). Since January 31, 2024, texts from unverified toll-free numbers, including those still pending review, are blocked from reaching US and Canadian recipients.

If you plan to text customers, the number type you choose decides which registration you go through: toll-free verification for toll-free numbers, or 10DLC registration for local numbers.

Why toll-free verification exists

Carriers want to know who is sending business text messages and whether recipients agreed to receive them. Local numbers got that system first with 10DLC. Toll-free numbers followed. Twilio's help center describes the shift: after US A2P 10DLC routes began in 2020, the industry announced in 2023 that toll-free numbers would also require registration and vetting, consistent with a broader move to require registration for all application-to-person messaging.

The timeline

According to Twilio:

Date	Change
November 8, 2023	All unverified ("Restricted") toll-free messaging blocked in the US
January 31, 2024	Messages from numbers with verification pending also blocked; only verified numbers can send
September 30, 2025	Business Registration Number (BRN) could be included in submissions
February 17, 2026	BRN mandatory for all new toll-free verification submissions

For US organizations, the BRN is the Employer Identification Number (EIN), and Twilio says the legal business name must match the IRS CP 575 EIN confirmation letter or an IRS 147C letter exactly.

What a verification submission includes

Providers collect similar information, which the carriers review:

• Business identity: legal business name, DBA if any, address, website and EIN
• Business contact: an authorized representative's name, title, email and phone, ideally with a business-domain email
• Use case: what you will send, such as appointment reminders, order updates or customer support
• Sample messages: real examples of what recipients will receive
• Opt-in process: how people agree to receive texts, with evidence such as a screenshot or live URL of the form
• Expected volume: estimated messages per month
• Policies: a live privacy policy and terms that match how you collect consent

Common rejection reasons

Twilio's list of rejection codes shows where submissions fail. The most common categories:

Problem	Example of what reviewers flag
Business can't be verified	Name, website and email domain don't match; contact email unrelated to the business
Business name mismatch	Name doesn't match official records; DBA not provided
Website issues	Site not active, password-protected, or missing business branding
BRN problems	EIN missing, wrong format, or legal name doesn't match IRS records
Consent problems	No opt-in evidence; consent bundled with another agreement; opt-in required to get a service
Disclosure gaps	Opt-in form missing business name, message frequency, rates, help or opt-out instructions
Too many numbers	More than five numbers for one business without justification
Shared number	One toll-free number used for several businesses
Prohibited content	Categories carriers do not allow; these cannot be fixed by resubmitting

Twilio notes a corrected submission can generally be resubmitted, but resubmission "does not authorize prohibited messaging." Changing the description of a prohibited use case does not make it allowed.

Toll-free verification vs 10DLC

	Toll-free verification	10DLC registration
Number type	800-type toll-free numbers	Standard local numbers
What is registered	Each toll-free number and its use case	A brand and one or more campaigns
Business ID	EIN required for new submissions (from Feb 17, 2026, per Twilio)	EIN used for brand registration
Unregistered sending	Blocked	Filtered or blocked by carriers
Local presence	No	Yes
Moving providers	Re-verify after porting (verification does not transfer, per Twilio)	Registration handled by the new provider

For details on the local-number side, see 10DLC brand registration, 10DLC campaign registration and 10DLC fees. If you are still choosing a number, read local vs toll-free numbers.

Should you text from a toll-free number at all?

Toll-free numbers make sense for national brands that want one number customers can call from anywhere, and for high-volume notification programs that providers offer on toll-free routes. For most small and local businesses, texting from the same local number customers already call is simpler: replies land in the same place, the number looks familiar, and there is one registration to manage instead of a separate toll-free verification for each number. If you already have a toll-free number for calls, you can keep it for voice and text from a local number, as long as the local number goes through 10DLC registration.

Porting a toll-free number

Twilio states that toll-free verifications cannot transfer between providers. If you port a toll-free number, submit a new verification after the port completes; Twilio warns that submitting before the port finishes can cause a rejection. Plan for a gap in texting if your new provider needs to re-verify.

Opt-in language that passes review

Your opt-in point, whether a web form, checkbox or keyword, should clearly show:

1. Your business name
2. What messages people will receive
3. How often (for example, "up to 4 messages per month")
4. "Message and data rates may apply"
5. How to get help (reply HELP) and stop (reply STOP)
6. Links to your privacy policy and terms

Consent to texts should be its own choice, not bundled with accepting your terms of service or required to get the service. See SMS opt-in language for examples.

After you are verified

Verification is not permanent permission to send anything. Carriers can still filter messages that do not match the approved use case, and a number that starts sending different content, such as marketing from a number verified for appointment reminders, risks filtering or suspension. If your use case changes, update the verification with your provider. Keep honoring STOP requests immediately, keep your opt-in records, and keep the website and privacy policy you submitted live, because reviewers may check them again.

Multiple numbers and multiple businesses

Twilio's rejection codes show two related limits. A single business asking to verify more than five toll-free numbers must justify why it needs them, and a single toll-free number cannot be shared across several businesses. Agencies and software vendors texting for clients need a separate number and a separate verification for each client.

Verification checklist

• Legal business name matches IRS EIN records exactly
• DBA listed if you text under a different name
• Website is live, public and shows your business name
• Contact uses a business-domain email
• Use case and sample messages match what you will actually send
• Opt-in evidence shows all required disclosures
• Privacy policy and terms are live and linked
• Separate number for each business you text for

Texting with Callata

Callata uses local business numbers, so texting goes through carrier 10DLC registration rather than toll-free verification. Callata handles the brand and campaign registration with your business details, including your EIN, for a one-time $49 fee, and team texting works from your business number once carriers approve it. The plan is $99 a month for up to five users with up to three local numbers; extra users are $20 a month each. Sign up.