The Toll-Free Verification Guide for 2026

Last updated July 21, 2026

Toll-free verification is the messaging industry's identity check for 8XX numbers — the toll-free equivalent of 10DLC registration, run through the toll-free aggregator rather than The Campaign Registry. You submit your business identity, use case, and opt-in evidence for each toll-free number; once verified, your traffic is trusted at full throughput.

Unverified toll-free messaging has been blocked industry-wide since the 2023 cutover, and in 2026 the review process got noticeably stricter: business details are checked against public records, and vague use cases that would have passed two years ago now come back rejected.

For the plain-English version — what reviewers actually check, and why submissions get rejected — see Toll-Free Verification, Explained.

• Legal business name matching state/IRS records.
• EIN / business registration number and an accurate business address.
• Specific use case — "appointment reminders for existing customers," not "notifications."
• Sample messages that match the use case, including opt-out language — and the same point-of-consent disclosures 10DLC reviewers expect (brand name, frequency, "Message and data rates may apply", STOP/HELP; see the disclosure checklist).
• Opt-in evidence — a screenshot or URL showing exactly how recipients consent to receive texts.
• Expected monthly volume for the number.

Verification checks the language in your live messages and the consent flow behind them, not just the campaign details. Have all of the following in place before you submit.

Messages must carry the required disclosures — reviewers compare them against what you actually send:

• Welcome / confirmation message: "Welcome to {Business Name}. Msg freq. varies. Msg & Data rates may apply. Reply STOP to end or HELP for help."
• HELP reply: "{Business Name}: {Description}. Help at {Email} or {Phone}. Msg&Data rates may apply."
• Your program or brand name in every content message.
• No public URL shorteners (bit.ly and the like) — a common rejection reason.

Your privacy policy must explain what data you collect and how it's used, and state that mobile opt-in information is not shared with third parties or affiliates for marketing or promotional purposes.

Your terms & conditions, kept separate from the opt-in language, must include:

• Program or brand name and a description.
• A "Message and data rates may apply" disclosure.
• Message frequency or recurring-message disclosure.
• Customer support contact information.
• Opt-out instructions (HELP and STOP), in bold or capitals.
• A link to your privacy policy.
• A "Carriers are not liable for any delayed or undelivered messages" disclosure.

Your opt-in flow must:

• Match the use case described in your submission.
• Collect consent per campaign — voluntary, and not bundled with other agreements.
• Keep messaging consent separate from your general terms of service or other sign-up flows.
• Use opt-in controls (checkboxes, toggles) that are unchecked or off by default; pre-checked boxes and other pre-authorizations are rejected.
• Show evidence of consent — a link or screenshot with your business name or logo visible.

Standard processing typically completes within about a week for clean submissions. Rejected submissions restart the clock — a resubmission cycle commonly adds one to several weeks, and numbers stuck "in verification" for months almost always trace back to mismatched business data or unverifiable opt-in evidence. The fastest path is a complete, consistent submission the first time.

Common rejection reasons in 2026:

• Business name that doesn't match public records.
• Vague or overly broad use-case descriptions.
• Sample messages that don't match the stated purpose.
• Missing or unverifiable opt-in language.
• The same content reused across unrelated campaigns.

Many businesses run more than one: short codes for mass and keyword traffic, toll-free for national support, 10DLC for local engagement. Carrier pass-through fees apply to all three and moved repeatedly in 2026 — T-Mobile and UScellular (Jan 19), Verizon (May 1), and eighteen regional carriers (Jul 1).

Short codes skip TCR entirely — carriers vet each program directly under CTIA Short Code Monitoring standards. See Short Codes for how that channel works.