Toll-Free Verification Guide
How to submit a toll-free verification — the required fields, the new 2026 mandatory fields, and the rules that get submissions rejected.
Toll-Free Verification is a single submission — no separate Brand and Campaign like 10DLC. You assemble one packet of business details, message samples, and proof of opt-in, your provider files it with the Somos/carrier-backed verification system, and the carriers approve or reject it. While it is in review, the number sends at a reduced pending rate; once verified, it moves to the default toll-free throughput.
The fastest path is to get every field right on the first pass. Use the Toll-Free Verification Field Builder to assemble a complete packet, including the new 2026 fields, before you submit.
The verification flow
- Get a toll-free numberProvision an 8XX number through your provider (Twilio, Telnyx, Bandwidth, etc.). You will need its identifier (the toll-free number SID) for the submission. You can usually send at the reduced pending/unverified rate immediately while you prepare the packet.
- Assemble the business and contact detailsGather your legal business name (matching IRS records), DBA, website, full business address, and a contact (first/last name, email, E.164 phone) plus a notification email. From 2026 you also need the new mandatory fields below.
- Describe the use case and write samplesChoose a use-case category and write a short summary of who sends, who receives, and why. Provide production message sample(s) that reflect what you will actually send.
- Provide opt-in proofSupply opt-in image URL(s) and the opt-in type. This is where most submissions fail — the reviewer must be able to see exactly how consumers consented (the form, checkbox, or keyword flow). Host it publicly.
- Submit and wait for reviewYour provider files the packet. Approval commonly takes 3–5 business days (Twilio) but can run several weeks in a backlog. A rejection can be resubmitted within 7 days for priority re-review — fix the cited reason before resubmitting.
Required fields
| Field | Notes |
|---|---|
| Legal business name | Must match IRS records |
| DBA | If you trade under a different name |
| Business website | Functional, related to the business |
| Full business address | — |
| Contact | First/last name, email, E.164 phone |
| Notification email | Where status updates are sent |
| Use-case category + summary | Who sends, who receives, why |
| Production message sample(s) | What you will actually send |
| Opt-in image URL(s) + opt-in type | Public proof of consent — top rejection cause if missing |
| Estimated monthly volume | — |
| Toll-free number SID | The number being verified |
New mandatory fields from 2026
The three new fields:
- BRN (Business Registration Number) — the government business identifier. In the US, this is your EIN.
- Issuing Country — the country that issued the BRN.
- Entity Type — the legal entity classification.
Add these now even before your provider enforces them — supplying them early avoids a resubmission later.
Twilio: separate Privacy and Terms URLs from Sept 15, 2026
Avoiding rejection
The opt-in evidence is the single most common failure point. Make sure:
- The privacy policy is publicly accessible (not login-gated, not under construction).
- The opt-in image clearly shows how consent was captured, and matches your stated opt-in type.
- The business name matches IRS records and your website.
- Message samples reflect the real traffic and the chosen use case.
Next: see throughput & fees for what your number can send before and after verification.