Toll-Free Verification registers a toll-free number, the end business using it, and the business's messaging use case with participating carriers. Verification is required before an LC Phone toll-free number can send SMS or MMS to recipients in the United States or Canada.

A successful submission depends on consistent business information, a live public web presence, a specific use-case description, representative message samples, and verifiable proof of how recipients consent to receive messages.

This guide covers the complete in-app verification flow and includes an in-page A2P opt-in appendix so you can prepare compliant consent evidence without relying on a separate article.

Only toll-free numbers with a Verified (Approved) status can send SMS/MMS traffic to recipients in the United States and Canada. Restricted (Unverified), Pending Verification, and Rejected numbers remain blocked for messaging until approval.

An unverified toll-free send can return Error 30032. Error 30007 indicates carrier filtering and can also appear when message content, consent, sender identification, or other compliance elements do not meet carrier expectations. Applicable messaging charges can still apply to accepted delivery attempts.

Toll-Free Verification applies to messaging. It does not prevent the number from being used for voice calling.

What is Toll-Free Number Verification?

Toll-Free Verification confirms who is sending business messages from a toll-free number, what types of messages recipients will receive, and how those recipients provide consent. The review helps carriers distinguish legitimate application-to-person messaging from unwanted or abusive traffic.

The requirement applies to SMS and MMS sent from US or Canada toll-free numbers to recipients in the United States and Canada. Each toll-free number must have its own approved verification record before messaging is enabled.

Toll-Free Verification is not 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 identity, transparent messaging use cases, and documented recipient consent.

Key Benefits of Toll-Free Verification

Verification gives carriers the information needed to evaluate the sender and messaging program before traffic is allowed. A complete and accurate submission also reduces preventable review delays.

• Messaging Eligibility: Enables an approved toll-free number to send SMS/MMS to US and Canada recipients.
• Improved Deliverability: Reduces the risk of traffic being blocked solely because the toll-free number is unverified.
• Carrier Transparency: Connects the end business, use case, message samples, and opt-in method to the sending number.
• Consent Accountability: Documents how recipients agree to receive the specific messages described in the submission.
• Faster Troubleshooting: Provides a clear status and verification record when messaging is blocked or rejected.
• Brand Trust: Supports responsible messaging practices that protect recipients and the sender's number reputation.

What You Need Before You Begin

Preparing the information before opening the verification form prevents incomplete submissions and makes it easier to keep the business website, consent proof, use-case description, and sample messages aligned.

How to Verify a Toll-Free Number

The in-app flow collects business identity, location, messaging use case, opt-in proof, and sample content in three stages. Complete every field using information that is accurate, public, and consistent with the end business.

Step 1: Open the Toll-Free Verification Form

1. Open the sub-account that owns the toll-free number.
2. Go to Settings → Phone System.
3. Open Manage Numbers.
4. Click Verification Required beneath the applicable toll-free number.

Open Phone System from the sub-account Settings area, then select Manage Numbers.

Select Verification Required for the toll-free number you want to register.

Step 2: Enter Business and Contact Information

Use the identity of the end business that recipients recognize as the sender. The legal entity name, website, contact information, and any additional registration fields should agree with one another.

• Legal Entity Name: Enter the business name used on official records and represented on the public website.
• Website URL: Use the end business's live public website. A public social profile can be used when the business does not maintain a website.
• Contact: Enter the first name, last name, email, country code, and phone number for a responsible business contact.
• Additional fields: Complete DBA, legal entity type, registration authority, registration number, or registration country when the form displays them.

Avoid mismatched branding. A private, inactive, unrelated, or reseller-branded website can prevent reviewers from confirming the end business and may lead to rejection.

Enter the end business's legal identity, public website, and responsible contact information.

Step 3: Enter the Business Location

Enter the physical location of the end business the recipient is engaging with. Use a complete address that can be associated with the same business named in the previous step.

1. Select the Country.
2. Enter the State, province, or region.
3. Enter Address Line 1.
4. Enter the City.
5. Enter the Postal or ZIP code.
6. 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 use-case stage must explain what will be sent, who will receive it, how consent is collected, and what evidence proves that process. Every selection should describe the program that will actually run on the toll-free number.

1. Select the expected Estimated Monthly Volume.
2. Select the actual Opt-In Type: Mobile/QR Code, Paper Form, Verbal, Via Text, or Web Form.
3. Select every applicable Use Case Category. Include Marketing when promotional content will be sent.
4. Provide a public Opt-In Workflow Image URL that shows the full consent flow.
5. Write a specific Use Case Description that identifies the audience, message purpose, opt-in source, and sending workflow.
6. Enter representative Message Content that matches the selected categories and includes the recognizable business name and opt-out language when applicable.

Select the opt-in type that matches the evidence and consent process described in the submission.

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 from HighLevel after a booking or service event. 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.”

Step 5: Review and Submit

1. Confirm that the business identity, website, location, categories, consent proof, description, and sample messages all match.
2. Open the public opt-in evidence URL in a private or incognito browser window to confirm that no login is required.
3. Select I agree to the Terms of Service.
4. Click Send Information for Verification.
5. Complete KYC or identity verification if HighLevel prompts the authorized user to do so.

Review the completed use case, accept the Terms of Service, and send the information for verification.

Appendix A — A2P Opt-In Guide

Business messaging sent through an application is application-to-person, or A2P, traffic. Toll-Free Verification reviews the same foundational questions: who is sending, what recipients will receive, and how the business can prove that each recipient knowingly agreed to those messages.

Core Consent Rules

• Consent must belong to the end 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 messaging.
• Consent must be optional. A person must be able to submit a form or complete a purchase without being forced to accept promotional messages.
• Checkboxes cannot be pre-selected. The recipient must select the desired consent option.
• Marketing and non-marketing consent must be separate. Use distinct choices when both message categories are offered.
• The disclosure must be complete. Identify the business, describe the message type, disclose frequency, state that message and data rates may apply, and provide HELP and STOP instructions when applicable.
• The submitted method must match reality. The selected opt-in type, evidence URL, use-case description, website, and actual workflow must tell the same story.
• Opt-outs must be honored. Stop messaging a recipient after a valid opt-out unless the recipient later completes a valid resubscription process.

Web Form Opt-In

A web form should show the SMS consent choice next to the phone-number collection experience, with visible links to the business's Privacy Policy and Terms and Conditions. The phone-number field can be required, but SMS consent must remain optional.

• Keep marketing and non-marketing consent in separate unchecked boxes.
• Make each consent box optional rather than a condition of submitting the form.
• Place visible Privacy Policy and Terms and Conditions links near the form or in its footer.
• Make sure the Privacy Policy explains the use of mobile information and does not permit sharing text-message opt-in data or consent with third parties for their marketing.
• Use the same business name and message categories in the form, verification submission, website, and sample messages.

Example of separate, optional SMS consent choices with visible legal-policy links.

Verbal Opt-In

Before asking for agreement, the representative or IVR should identify the business, explain the message types and expected frequency, disclose message and data rates, provide HELP and STOP instructions, and direct the recipient to the Terms and Privacy Policy.

Record the phone number, date and time, representative or IVR flow, disclosure version, recipient response, and any call recording or system log used as evidence.

Paper Form Opt-In

The paper form should display the same required disclosures and provide a clear place for the recipient to affirm consent. Retain a dated copy or scan and provide a publicly accessible redacted sample as verification evidence.

Via Text and Mobile/QR Code Opt-In

Campaign collateral should explain the keyword or QR-code action, identify the business, describe the message program, disclose frequency and rates, include HELP and STOP instructions, and point to the Terms and Privacy Policy.

• A QR code that opens a web form must lead to a form that follows the web-form rules above.
• A QR code that opens the phone's messaging app should prefill only the intended keyword or opt-in message.
• Provide a public image of the printed sign, advertisement, landing page, or other collateral that contains the complete opt-in instructions.

Opt-In Evidence and Recordkeeping

The verification URL must be accessible to a reviewer without signing in. Show the full context of the opt-in, not only a cropped checkbox or phone-number field.

• Store the full consent text shown to the recipient.
• Store the recipient phone number and the date and time of consent.
• Store the opt-in method and source page, form, campaign, call, paper record, keyword, or QR code.
• Store the IP address, form submission ID, call recording, or comparable evidence when available.
• Keep a link or reference to the consent record on the contact record when your process supports it.
• Retain opt-out and resubscription events so the current consent status can be demonstrated.

Use Media Storage to upload opt-in evidence and obtain a public link for the verification submission.

Monitor Verification Status

The status beneath the toll-free number determines whether US and Canada messaging is available. Review can take up to four to six weeks, although some submissions finish sooner; approval timing is not guaranteed.

Political Election Campaign Use Cases

Political Election Campaign messaging has an additional identity-verification requirement. The extra credential connects the toll-free messaging program to a verified political organization.

Beginning February 17, 2026, new political toll-free verifications—and existing approved toll-free numbers used for political election messaging—require a valid Campaign Verify Auth Token. HighLevel does not issue this token; it must be obtained through Campaign Verify and entered when the Political Election Campaign category is selected.

Learn about Campaign Verify requirements for political toll-free messaging →

Troubleshooting and Rejection Prevention

Most verification problems come from inconsistent business identity, inaccessible websites or proof URLs, incomplete consent disclosures, mismatched use cases, or sample messages that do not represent the actual program.

Frequently Asked Questions

Related Articles