Toll-Free Number Verification confirms the business and messaging use case associated with a toll-free phone number. Verification is required before an eligible toll-free number can send SMS or MMS to recipients in the United States or Canada. A complete submission includes accurate business details, a description of the intended messages, and evidence of how recipients provide consent. This guide explains how to submit verification, prepare opt-in evidence, monitor approval, and resolve common verification problems.
Important: Only toll-free numbers with a Verified (Approved) status can send SMS or MMS to recipients in the United States and Canada. Numbers marked Restricted (Unverified), Pending Verification, or Rejected remain blocked until approval. Toll-Free Verification applies to messaging and does not prevent voice calling.
Sending a message before approval may return Error 30032. Error 30007 indicates message filtering and may occur when content, consent, sender identification, or other messaging requirements are not met.
TABLE OF CONTENTS
- What Is Toll-Free Number Verification?
- Key Benefits of Toll-Free Verification
- What You Need Before You Begin
- How to Verify a Toll-Free Number
- Appendix A — A2P Opt-In Guide
- Monitor Verification Status
- Political Election Campaign Use Cases
- Troubleshooting and Rejection Prevention
- Frequently Asked Questions
- Related Articles
- Need Help?
What Is Toll-Free Number Verification?
Toll-Free Verification confirms the business sending messages from a toll-free number, the types of messages recipients will receive, and how recipients provide consent.
The review helps carriers distinguish legitimate application-to-person messaging from unwanted or abusive traffic.
Verification applies to toll-free SMS and MMS traffic sent to recipients in the United States and Canada. Each toll-free number must have an approved verification record before messaging is enabled.
Toll-Free Verification is different from A2P 10DLC registration. A2P 10DLC applies to eligible US local 10-digit numbers, while Toll-Free Verification applies to toll-free messaging. Both processes require accurate sender information, a clear messaging use case, and documented recipient consent.
Key Benefits of Toll-Free Verification
Verification allows carriers to evaluate a business's messaging program before messages are sent. Providing complete and consistent information helps reduce preventable verification delays and supports responsible messaging.
- Messaging Eligibility: Allows an approved toll-free number to send eligible SMS and MMS messages to recipients in the United States and Canada.
- Improved Deliverability: Reduces the risk of messages being blocked solely because the toll-free number has not been verified.
- Carrier Transparency: Connects the business identity, messaging use case, sample messages, and opt-in method to the sending number.
- Consent Accountability: Documents how recipients agree to receive the messages described in the verification submission.
- Faster Troubleshooting: Provides a verification status and submission record that can help identify messaging restrictions or rejection reasons.
- Sender Trust: Supports responsible messaging practices that help protect recipients and the sending number's reputation.
What You Need Before You Begin
Prepare the information used to identify your business and describe its messaging program before opening the verification form. Accurate, consistent details help reviewers evaluate the submission.
Have the business's legal name, public website or eligible public business profile, contact information, physical address, messaging use case, opt-in evidence, and representative sample messages ready.
Required policy links: Effective September 15, 2026, new toll-free verification submissions must include both a Privacy Policy URL and a Terms & Conditions URL. Each URL must be publicly accessible and relevant to the business being verified.
Existing approved toll-free verifications do not require an update solely because of this policy-URL requirement.
| Prepare | What Reviewers Need to Confirm |
|---|---|
| Toll-free phone number | The number is available in Manage Numbers and requires verification. |
| Legal entity or business name | The name accurately identifies the business sending messages and remains consistent throughout the submission. |
| Live website or public business profile | The public page represents the named business and supports its stated products, services, and messaging purpose. |
| Business contact and location | The responsible contact and physical business address are accurate and associated with the sender. |
| Estimated monthly volume and use-case categories | The selected categories and anticipated messaging volume accurately describe the intended traffic. |
| Opt-in method and public evidence URL | The evidence shows how recipients provide consent for the stated messages. |
| Privacy Policy URL | A publicly accessible page containing the business's Privacy Policy. |
| Terms & Conditions URL | A publicly accessible page containing the business's Terms & Conditions. |
| Detailed use-case description | The description identifies the intended recipients, message purpose, consent source, and sending process. |
| Representative sample messages | Examples match the use case and identify the business, message context, and applicable opt-out instructions. |
| Additional business-registration fields | If requested, provide the DBA, entity type, registration authority, registration number, or registration country. |
Important: Provide any additional identity or registration details requested by the verification form. Requirements may vary with the business information and verification process.
The legal entity should identify the business actually sending the messages. Its public website, contact information, messaging purpose, and opt-in evidence should consistently represent that business.
For consent requirements and examples, see Appendix A — A2P Opt-In Guide.
How to Verify a Toll-Free Number
The verification form collects business identity, physical location, messaging use case, and consent evidence. Complete the following steps using information that matches the business's public presence and actual messaging practices.
Step 1: Open the Toll-Free Verification Form
Start from the Phone System settings and locate the toll-free number that requires verification.
- Click Settings.
- Open Phone System.
- Select Manage Numbers.
- Locate the toll-free number.
- Click Verification Required beneath the number to open the verification form.

Open Phone System from Settings and select Manage Numbers.

Select Verification Required for the toll-free number you want to register.
Step 2: Enter Business and Contact Information
Enter the identity and contact information of the business whose messages recipients will receive. This information should match the business's public presence.
- Legal Entity Name: Enter the business's legal name as required by the form.
- Website URL: Enter the business's live public website. If the business has no formal website, use an eligible public business profile where supported.
- Contact: Enter the responsible person's first name, last name, email, country code, and phone number.
- Complete any additional identity or registration fields displayed by the form.
Important: The website or public profile must be accessible and clearly associated with the named business. An inactive, unrelated, or inaccessible site can prevent reviewers from confirming the business identity.

Enter the business's legal identity, public website, and responsible contact information.
Step 3: Enter the Business Location
Provide the physical location of the business associated with the messaging program. Use a complete, accurate address that corresponds to the business information entered previously.
- Select the Country.
- Enter the State, province, or region.
- Enter Address Line 1.
- Enter the City.
- Enter the Postal or ZIP code.
- Click Continue to Messaging Use Case.

Complete the physical business location before continuing to the messaging use case.
Step 4: Describe the Messaging Use Case and Opt-In
The messaging use-case stage explains what messages will be sent, who will receive them, and how consent is collected. The evidence and examples must match the messaging program the business actually uses.
On Step 3/3 — Messaging use case, the Privacy Policy URL and Terms & Conditions URL fields appear below the opt-in evidence fields and above the use-case description and message-content fields.
- Select the expected Estimated Monthly Volume.
- Select the actual Opt-In Type: Mobile/QR Code, Paper Form, Verbal, Via Text, or Web Form.
- Select each applicable Use Case Category. Include Marketing when the program will send promotional messages.
- Provide a publicly accessible Opt-In Workflow Image URL that shows the consent process.
- Enter the publicly accessible business Privacy Policy page in Privacy Policy URL.
- Enter the publicly accessible business Terms & Conditions page in Terms & Conditions URL.
- Write a specific Use Case Description identifying the recipients, message purpose, consent source, and sending process.
- Enter representative Message Content that matches the selected categories and identifies the business. Include applicable opt-out instructions.
Provide both publicly accessible policy URLs in the Messaging use case step.
Strong Use-Case Example
This toll-free number sends appointment confirmations, rescheduling notices, and service follow-ups to customers of [Business Name] who explicitly opt in through our public appointment form. Messages are sent after booking or service events. Recipients can reply HELP for assistance or STOP to opt out.
Strong Sample Message
[Business Name]: Your appointment is confirmed for [date/time]. Reply C to confirm or call [support number] for help. Reply STOP to opt out.
Note: These examples illustrate use-case clarity and sample-message structure. Review all current carrier-required disclosures before adopting wording for a live messaging program.
Step 5: Review and Submit
Review the completed submission to make sure the business identity, messaging details, consent evidence, and legal-policy links are accurate and consistent.
- Review the business name, website, contact information, location, selected categories, opt-in proof, policy URLs, use-case description, and sample messages.
- Open the opt-in evidence URL, Privacy Policy URL, and Terms & Conditions URL in a private browser window. Confirm that each loads without requiring a login.
- Select I agree to the Terms of Service.
- Click Send Information for Verification.
- Complete any additional identity verification requested by the application.

Review the completed use case, accept the Terms of Service, and submit the verification request.
Appendix A — A2P Opt-In Guide
Application-to-person, or A2P, messaging requires clear evidence of who is sending messages, what recipients will receive, and how they agreed to receive them. Use this appendix to prepare consent information that is consistent with the toll-free verification submission.
Core Consent Rules
Consent evidence should clearly demonstrate that recipients knowingly agreed to the specific messaging program. The following principles help prevent incomplete or mismatched submissions.
- Consent must belong to the sending business: Do not use purchased, rented, shared, or transferred contact lists as proof of opt-in.
- Consent must be affirmative: A recipient must take a clear action to agree to receive the relevant messages.
- Consent must be optional: Promotional messaging consent must not be required to submit an unrelated form or complete a purchase.
- Checkboxes must not be preselected: The recipient must select the applicable consent option.
- Marketing and non-marketing consent must be distinct: Use separate choices when the messaging program includes both categories.
- Disclosures must be complete: Identify the business, describe the message purpose, explain frequency, provide applicable HELP and STOP instructions, and include all other required carrier disclosures.
- The submitted method must match the actual process: The selected opt-in type, evidence URL, public website, use-case description, and sending process must be consistent.
- Opt-outs must be honored: Stop sending messages after a valid opt-out unless the recipient later completes an appropriate resubscription process.
Important: Consent examples in this article are illustrative. The exact disclosures required for a particular messaging program must be reviewed against current carrier requirements and applicable law.
Web Form Opt-In
A web form should display the SMS consent choice near the phone-number collection field. Include visible links to the business's Privacy Policy and Terms & Conditions. Consent to receive marketing messages should remain optional.
| Consent Type | Illustrative Wording |
|---|---|
| Marketing | I consent to receive marketing text messages about special offers, discounts, and service updates from [Business Name] at the phone number provided. Message frequency may vary. Text HELP for assistance or reply STOP to opt out. |
| Non-Marketing | I consent to receive non-marketing text messages from [Business Name] about [specific use case, such as appointment reminders or order updates]. Message frequency may vary. Text HELP for assistance or reply STOP to opt out. |
Important: These samples are not complete, ready-to-publish consent disclosures. Add every disclosure required for the actual messaging program and applicable carrier policies before using them.
- Keep marketing and non-marketing consent in separate, unchecked boxes when both categories are offered.
- Make the relevant SMS consent choice optional rather than a requirement for submitting an unrelated form.
- Place visible Privacy Policy and Terms & Conditions links near the consent form.
- Ensure that the Privacy Policy explains the use of mobile information and does not authorize sharing messaging opt-in data or consent for unrelated third-party marketing.
- Use the same business name and messaging categories in the form, website, verification submission, and message samples.

Example of separate, optional SMS consent choices with visible legal-policy links.
Verbal Opt-In
Before requesting verbal consent, identify the business, explain the messages recipients will receive, describe their frequency, provide applicable HELP and STOP instructions, and direct recipients to the Privacy Policy and Terms & Conditions.
Illustrative example:
[Business Name] can send you appointment reminders and service updates by text. Message frequency varies. Reply HELP for assistance or STOP to opt out. Our terms are available at [Terms URL] and our privacy policy is available at [Privacy URL]. Do you agree to receive these messages?
Record the phone number, consent date and time, representative or IVR process, disclosure version, recipient response, and any associated call recording or system log used as evidence.
Use verbal opt-in only when the method is permitted for the applicable messaging program and meets current consent requirements.
Paper Form Opt-In
A paper form should identify the business, explain the messaging program, include the applicable consent disclosures, and provide a clear way for the recipient to affirm consent.
Retain a dated copy or scan. Provide a publicly accessible, appropriately redacted example when verification reviewers require evidence.
Via Text and Mobile/QR Code Opt-In
Text-message keywords, printed materials, and QR codes must clearly describe how the recipient joins the messaging program. The evidence should identify the business, the program, the requested action, and applicable consent disclosures.
- A QR code that opens a web form must lead to a form with the appropriate web-form consent elements.
- A QR code that opens a messaging app should prefill only the intended keyword or opt-in message.
- Provide a public image of the sign, advertisement, landing page, or other material that contains the opt-in instructions.
Opt-In Evidence and Recordkeeping
The opt-in evidence URL must be accessible to a reviewer without signing in. Provide the full consent context rather than a cropped checkbox or isolated phone-number field.
- Store the complete consent wording shown to the recipient.
- Record the recipient's phone number and the date and time of consent.
- Record the opt-in method and source, such as a form, website, campaign, call, paper record, keyword, or QR code.
- Retain an IP address, submission ID, call recording, or comparable evidence when available.
- Keep an accessible reference to the consent record where your contact-management process supports it.
- Record opt-outs and later resubscription events so the recipient's current consent status can be demonstrated.
Upload Opt-In Evidence to Media Storage
If your live opt-in page cannot be viewed publicly, you can provide a public link to an image or document showing the complete process. The available Media Storage tools can help you create that link.
- Open Media Storage.
- Upload the screenshot or supporting document using the upload control.
- Open the uploaded asset's menu.
- Select Get Link.
- Copy the link and test it in a private browser window before adding it to the verification submission.

Use Media Storage to upload opt-in evidence and obtain a public link for the verification submission.
Monitor Verification Status
The verification status displayed for the toll-free number determines whether messaging to recipients in the United States or Canada is available. Review times vary, and approval is not guaranteed within a particular period.
| Verification Status | US/Canada Messaging | What It Means |
|---|---|---|
| Restricted (Unverified) | Blocked | The number has not been submitted or does not have an approved verification. |
| Pending Verification | Blocked | The request is under review. Wait for approval before sending SMS or MMS. |
| Verified (Approved) | Allowed | The number is approved for eligible messaging, subject to applicable carrier, consent, and content requirements. |
| Rejected | Blocked | Review the rejection reason, correct the submission, and resubmit or request assistance when appropriate. |
Important: Do not attempt production messaging while the number is Restricted, Pending, or Rejected. Resolve the verification requirement and send a controlled test after the number shows Verified (Approved).
Political Election Campaign Use Cases
Political Election Campaign messaging has additional identity-verification requirements. The verification process uses a Campaign Verify credential to associate the toll-free messaging program with a verified political organization.
As of February 17, 2026, new toll-free verification submissions for Political Election Campaign messaging require a valid Campaign Verify Auth Token. The requirement also applies to existing approved toll-free numbers used for political election messaging.
Campaign Verify issues the token after completing the applicable political organization verification process. Obtain a token suitable for toll-free messaging before submitting the political use case.
When completing the toll-free verification form, select Political Election Campaign as the use-case category and enter the valid Campaign Verify Auth Token in the required field.
Troubleshooting and Rejection Prevention
Verification requests may be rejected because of inconsistent business information, inaccessible websites or evidence URLs, incomplete consent disclosures, mismatched messaging use cases, or sample messages that do not represent the actual program.
| Problem | What to Check | Recommended Action |
|---|---|---|
| Verification Required is not visible | The number is toll-free, appears in Manage Numbers, and is eligible for the verification process. | Confirm the number type and refresh Manage Numbers. Contact support if the expected option remains unavailable. |
| Website cannot be verified | The page is live, public, associated with the business, and not password-protected. | Publish or correct the website. Use an eligible public business profile when appropriate. |
| Opt-in evidence URL is rejected | The link is public, opens directly, includes the full consent process, and matches the selected opt-in type. | Provide a complete image or document through a publicly accessible link and test the URL in a private browser window. |
| Consent flow is incomplete | Optional unchecked consent boxes, sender identification, message purpose, frequency, applicable disclosures, HELP and STOP instructions, and policy links. | Correct the live opt-in process and update the supporting evidence before resubmitting. |
| Use case and samples do not align | Use-case categories, description, opt-in wording, website, and sample messages describe the same program. | Replace vague descriptions and correct samples that omit the sender, messaging context, or required instructions. |
| Error 30032 | The sending toll-free number has not reached Verified (Approved) status. | Complete or correct Toll-Free Verification and wait for approval before retrying. |
| Error 30007 | A message was filtered because of content, consent, sender information, or other policy signals. | Review the message content, links, opt-in evidence, sender identification, and applicable messaging policies. |
| Rejected and resubmission is unavailable | The rejection reason, business details, affected number, opt-in proof, and submitted use case. | Contact support and request guidance on available correction or appeal options. |
Information to Include When Contacting Support
Providing complete verification details helps support investigate a rejected submission or missing verification option.
- Location ID, when relevant to identifying the affected number.
- Affected toll-free number in E.164 format.
- Current verification status and rejection reason.
- Business legal name and public website URL.
- Public opt-in evidence URL.
- Screenshot or screen recording of the issue.
- Example failed messages and error codes, when applicable.
Frequently Asked Questions
Q: Can I send SMS or MMS while verification is pending?
No. Numbers marked Pending Verification remain blocked from sending SMS and MMS to recipients in the United States and Canada until they are approved.
Q: Does Toll-Free Verification affect voice calling?
No. The verification requirement described here applies to SMS and MMS. Voice calls are not blocked solely because toll-free messaging verification is incomplete.
Q: Can I verify multiple toll-free numbers in one submission?
Each toll-free number is submitted individually through the verification process described in this guide.
Q: Is verification required for sole proprietors and small businesses?
Yes. Toll-Free Verification requirements apply to eligible toll-free messaging regardless of business size. Provide the business identification and registration details requested by the form.
Q: Must the business be located in the United States?
No. A business address from another country may be used when it accurately represents the business and the information can be verified.
Q: Can I use a social media page instead of a website?
An eligible public business social profile may be used when the business does not maintain a formal website. The profile must be publicly accessible and clearly represent the business named in the submission.
Q: What should I do if my opt-in page is behind a login or is not live yet?
Provide a publicly accessible image or document showing the complete opt-in process. The evidence should show the consent wording, relevant disclosures, and the action the recipient takes to agree.
Q: What should I do if verification is rejected?
Review the rejection reason and correct the business information, website, messaging use case, consent evidence, legal-policy links, or sample messages as needed. Resubmit when the option is available. If resubmission is unavailable, contact support.
Q: How do I know the toll-free number is ready to send messages?
The number is ready for eligible SMS and MMS traffic to US and Canada recipients when Manage Numbers displays Verified (Approved). Continue following applicable consent, sender-identification, content, and opt-out requirements after approval.
Need Help?
If you have questions or need assistance with a feature, contact support for further guidance. To help resolve your issue efficiently, include a brief description of what you're trying to accomplish, the steps you've already taken, and any relevant screenshots or error messages.