Setting Up Toll-Free Verification for AI Calling

Toll-free numbers (800, 888, 877, 866, 855, 844, 833) carry a compliance requirement that catches many voice AI deployments off-guard: before you can reliably send SMS or initiate high-volume outbound voice traffic from a toll-free number, you need carrier verification. Skip this and your messages get silently filtered, your outbound calls get flagged as spam, and your integration appears to be working in dev but failing mysteriously in production. Setting up verification is a straightforward process — if you know what's required and plan for the 2–4 week approval cycle.

TL;DR

• Toll-free verification is required for reliable SMS delivery and high-volume voice on 800-series numbers.
• The process: submit business info, sample content, opt-in evidence, and use case.
• Timeline: 2–4 weeks for approval; first submissions often bounce back.
• Different process than A2P 10DLC (for standard 10-digit numbers).
• Once verified, deliverability and trust ratings materially improve.

What verification is

Toll-free carriers (the networks that deliver your calls and SMS to end users) run a verification program to reduce spam and fraud. Unverified toll-free numbers get:

• SMS: heavily filtered or blocked.
• Voice: flagged as spam / scam-likely on caller ID.
• Caller ID issues: may not display business name.

Verification tells carriers: "This is a legitimate business, we follow consent rules, our traffic is expected."

Who needs it

You need toll-free verification if:

• You send SMS from a toll-free number.
• You make high-volume outbound voice calls from a toll-free number.
• You want branded caller ID display.

You may be fine without it if:

• Very low volume inbound-only.
• Using local 10-digit numbers (those use A2P 10DLC instead).

See A2P 10DLC explained for voice agent builders.

The verification process

Typical flow via Twilio (similar for other carriers):

1. Gather business info.

   • Legal business name.
   • Address.
   • EIN (tax ID).
   • Website URL.
   • Estimated volume.
   • Use case category (marketing, notifications, 2FA, customer care, etc.).

2. Prepare opt-in evidence.

   • Screenshot of signup form showing SMS consent.
   • Copy of privacy policy referencing SMS.
   • Description of how users opt in.
   • Must match what you describe in the verification.

3. Prepare sample messages.

   • 2–5 sample SMS messages you'll send.
   • Must match your use case category.
   • Must include STOP opt-out language.

4. Submit. Via your carrier provider's portal.

5. Wait. Approval: 2–4 weeks typically. First-submission rejection rate: ~30–40%.

6. Fix and resubmit. Address rejection reasons, resubmit.

Common rejection reasons

• Missing STOP language in sample messages.
• Opt-in flow unclear. "Users opt in on our website" isn't enough — show the exact form.
• Privacy policy doesn't mention SMS. Update it.
• Use case mismatch. You said "notifications" but samples look like marketing.
• Business verification fails. EIN doesn't match registered name.

Each rejection explains what's wrong. Fix, resubmit.

Throughput tiers

After verification, your number gets a throughput tier:

• Standard. ~10 messages/second per number.
• Higher tiers for verified campaigns. Up to hundreds/second.

For most voice agent SMS use cases, standard is sufficient.

Toll-free vs 10DLC

	Toll-free	10DLC
Number format	1-8xx	1-xxx (area code)
Setup time	2–4 weeks	2–8 weeks (brand + campaign)
Cost	Free-ish (per message)	Registration fees + per message
Throughput	Moderate	Brand-score-dependent
Best for	Consumer-facing brands	Most business SMS
Content filtering	Strict	Moderate

Many deployments use both — toll-free for voice and consumer SMS, 10DLC for local-flavored business messaging.

Maintenance

Verification isn't forever:

• Renewals every 12 months typically.
• Content / campaign changes may require re-verification.
• Volume changes may require tier re-evaluation.

Calendar the renewals. Don't let verifications lapse.

Sample submission

Here's what a good submission looks like:

Business: Westside Dental LLC
EIN: XX-XXXXXXX
Website: westsidedental.com
Use case: Customer Care (appointment reminders, confirmations)
Estimated volume: 5,000 SMS/month
Opt-in: Patients provide phone at signup; SMS consent checkbox on intake form. Phone+consent stored in EHR.
Opt-out: Any patient can reply STOP to opt out. Confirmed via return SMS.
Sample messages:

1. "Westside Dental: Reminder — appointment tomorrow 4/18 at 10 AM. Reply C to confirm or R to reschedule. STOP to opt out."
2. "Westside Dental: Your cleaning is confirmed for 4/18 at 10 AM with hygienist Sarah. STOP to opt out."
3. "Westside Dental: Your lab results are in. Please call 555-1234 to discuss. STOP to opt out."

Clean, clear, compliant.

Voice verification (caller ID)

Separate from SMS verification, voice calls benefit from SHAKEN/STIR attestation:

• A-level attestation — signed by originating carrier, high trust.
• B-level — partial attestation.
• C-level — lower trust.

Your carrier signs calls based on your verification. Over time, call completion and trust scores improve.

See caller ID and trust: why numbers get marked as spam.

Pilot strategy

While verification is in progress:

• Use local 10DLC numbers (faster to provision) for early testing.
• Pilot with small user group.
• Migrate to toll-free once verified.

Common pitfalls

Submitting too fast. Rushing the prep → rejection. Take time on opt-in evidence and sample messages.

Vague opt-in descriptions. Carriers want specifics.

Forgetting STOP language. Federal law requires it. Sample must show it.

Mismatched business info. EIN, address, legal name must all align across submission.

Renewal lapses. Verification expires; deliverability drops without warning. Calendar renewals.

Working with your provider

Your provider (Twilio, Bandwidth, Telnyx) handles the mechanics:

• They submit on your behalf.
• They communicate carrier responses.
• They handle re-submissions.

Your job: provide clean, complete information. Their job: navigate the carrier process.

Related reading

• Twilio + Voice Agents: A Complete Guide
• Sending Voice Agent Transcripts to Slack
• Connecting Voice Agents to Snowflake or BigQuery
• How to Port a Phone Number to Your Voice Agent
• Bring Your Own Twilio: Pros, Cons, and Setup

FAQ

What if our provider doesn't handle verification? Time to switch providers. Modern carriers all support this.

Can we deploy without verification? You can, but deliverability and trust suffer. Not recommended for production.

Does verification transfer between providers? Not directly — each provider submits verifications. Porting numbers may reset some work.

What about international toll-free? Different rules per country. Each country has its own registration.

How do we maintain good standing? Respect opt-outs, match your stated use case, keep volume in line with estimates.