Before your business can send messages from a toll-free number in the US or Canada, you’ll need to complete SMS toll-free verification.
This process ensures that your messages comply with carrier requirements — confirming that customers have given explicit consent to receive SMS from your business.
Toll-free verification protects your business from message filtering and improves delivery reliability.
A verified number shows carriers that you’re a legitimate sender, not a source of unwanted or unsolicited messages.
In this guide, we’ll help you complete your verification successfully by walking you through:
- Choosing the right use case — decide what type of messages your number will send.
- Selecting your opt-in type — choose how customers will give consent.
- Preparing your opt-in proof — upload the correct screenshot, form, or URL that demonstrates consent.
- Avoiding rejections and delays — understand common issues and how to fix them quickly.
- Reviewing FAQs — get answers to common verification questions.
💡 Tip:
Each toll-free number can only be verified for one use case at a time.
If your business sends both marketing and transactional messages, you’ll need to submit separate verifications for each purpose.
Toll-free verification checklist
Before you start your SMS toll-free verification, prepare the following:
- Define your use case
- Decide what this phone number will be used for — e.g. marketing, customer care, delivery updates, or 2FA.
- Each number can only be verified for one use case.
- Estimate your monthly message volume
- Carriers review your estimated monthly volume to ensure it matches your business size and use case.
- Setting it unrealistically high (for example, a small business claiming 1M messages per month) can delay approval.
- Provide a reasonable estimate — you can update it later as your traffic grows.
- Prepare compliant consent
- Make sure your opt-in process clearly states:
- Your business name
- The purpose of messages
- Informs customers that their mobile carrier may charge for receiving texts: “Msg & data rates may apply”
- Tells customers how to opt out of future messages at any time: “Reply STOP to unsubscribe”
- Make sure your opt-in process clearly states:
- Gather proof of consent
- Depending on how customers opted in, prepare:
- A public URL or screenshot of your web/QR form
- A screenshot of your SMS keyword prompt
- A scanned form or CRM note for paper or verbal consent
- Depending on how customers opted in, prepare:
- Example of compliant consent
- “By signing up, I agree to receive [type of messages] from [Your business name]. Msg & data rates may apply. Reply STOP to unsubscribe.”
Ready-to-use templates for your submission
To help you complete your toll-free verification faster, we’ve prepared ready-to-copy templates for the most common use cases.
Each template includes all the fields you’ll see in the verification form — from use case description to message content and opt-in proof.
Simply copy the content from the table that matches your use case, replace the bracketed text (e.g. [Your business name]), and paste it directly into your form.
The following templates cover the five most common business purposes:
💡 Tip: Always make sure your opt-in proof (screenshot or URL) clearly matches the consent wording in your submission to avoid delays or rejection
Marketing
Form field |
Example content to copy |
Estimated monthly messaging volume |
Select your estimated monthly volume |
Opt-in type |
|
Opt-in policy image URLs |
💡 Make sure the link is publicly accessible (“Anyone with the link”) and clearly shows:
|
Use case categories |
|
Use case description |
We use this toll-free number to send promotional and marketing messages such as product offers, discounts, and campaign updates to customers who have opted in through our website form or SMS keyword. Messages are only sent to contacts who have given express written consent. |
Message content |
Example 1: “Hi
Example 2: “FLASH SALE! Get 15% off all items this weekend only. Visit |
Additional information |
Our SMS program follows carrier and TCPA compliance requirements. All recipients opt in via [choose one: a web form / QR code / SMS keyword] that includes our brand name,consent statement, Msg & data rates may apply,” and “Reply STOP to unsubscribe.” Messages are only sent to customers who have provided express written consent.
|
Customer care/support
Form field |
Example content to copy |
Estimated monthly messaging volume |
Select your estimated monthly volume (e.g. |
Opt-in type |
Web form / Paper form / Verbal |
Opt-in policy image URLs |
💡 Make sure the link is publicly accessible (“Anyone with the link”) and clearly shows:
|
Use case categories |
|
Use case description |
We use this toll-free number to send service-related messages such as appointment reminders, support updates, and follow-ups to customers who have requested assistance or submitted a service form. Messages are only sent to customers who have given consent through a web form, paper form, or verbal agreement. |
Message content |
Example 1: “Hi
Example 2: “Reminder: Your |
Additional information |
We only send messages to customers who have initiated a service request or provided consent via |
Account notification
Form field |
Example content to copy |
Estimated monthly messaging volume |
Select your estimated monthly volume (e.g. |
Opt-in type |
|
Opt-in policy image URLs |
💡 Make sure the link is publicly accessible (“Anyone with the link”) and clearly shows:
|
Use case categories |
|
Use case description |
We use this toll-free number to send account-related messages such as billing reminders, renewal alerts, password resets, and security notifications to customers who have opted in through our account signup or service forms. These are transactional messages only and do not include any marketing content. |
Message content |
Example 1:“[
Example 2:“ |
Additional information |
All recipients opt in via |
Delivery notification
Form field |
Example content to copy |
Estimated monthly messaging volume |
Select your estimated monthly volume (e.g. |
Opt-in type |
|
Opt-in policy image URLs |
https://[insert-public-URL-or-Google-Drive-link-showing-your-checkout-or-order-form] 💡 Make sure the link is publicly accessible (“Anyone with the link”) and clearly shows:
|
Use case categories |
|
Use case description |
We use this toll-free number to send order and delivery updates, including confirmations, shipment tracking, and pickup reminders. These messages are transactional and only sent to customers who have opted in during checkout or confirmed their phone number for delivery updates. |
Message content |
Example 1:“
Example 2:“ |
Additional information |
All recipients opt in via |
Event
Form field |
Example content to copy |
Estimated monthly messaging volume |
Select your estimated monthly volume (e.g. |
Opt-in type |
|
Opt-in policy image URLs |
💡 Make sure the link is publicly accessible (“Anyone with the link”) and clearly shows:
|
Use case categories |
|
Use case description |
We use this toll-free number to send event-related messages such as confirmations, reminders, schedule updates, and location changes to participants who have registered for our events. These messages are informational and do not contain marketing or promotional content. |
Message content |
Example 1:“
Example 2:“ |
Additional information |
All recipients opt in via |
Choosing the right use case for your phone number
Every toll-free number must be verified under one primary use case, which defines the purpose of your SMS messages.
Your use case determines what kind of consent you need from customers, and what type of messages are allowed under that consent.
Choosing the correct use case is the first and most important step in your verification process.
Submitting the wrong use case — or sending messages outside the approved purpose — is a common reason for rejection.
💡 Tip:
Think about the intent of your messages, not your industry.
For example, a university sending marketing campaigns should select Marketing, while a university sending enrollment reminders should select Higher education.
Available use cases
When completing the verification form, you can select one of the following use case categories:
Use case |
What is it for |
|
Promotional and sales messages.
|
|
Service updates or assistance follow-ups |
|
Account activity or renewal alerts. |
|
One-time verification or login codes. |
|
Order, shipping, or pickup updates. |
|
Event confirmations and reminders. |
|
Donation or volunteer updates. |
|
Security or suspicious activity alerts |
|
University or college communications. |
|
School or parent notifications. |
|
|
Surveys and research participation.
|
|
|
Voter outreach or election reminders.
|
|
Emergency or community alerts. |
⚠️ Note:
Each toll-free number can only be verified for one use case.
If your business sends both marketing and transactional messages, submit separate verifications for each purpose.
Marketing
The Marketing use case applies when your business sends promotional or sales-related messages to customers. This includes product offers, discounts, loyalty programs, and campaign updates.
You can use this category if your SMS messages promote products or services, announce new launches, or share exclusive deals with customers who have explicitly opted in to receive marketing content.
Category |
Details |
Accepted opt-in types |
Marketing messages can only be sent to customers who opt in through: ✅ Web form (e.g. newsletter signup, checkout page) ✅ Paper form (e.g. in-store registration or event form) ✅ Mobile / QR code (e.g. promotional poster scan) ✅ Via text (SMS keyword) (e.g. “Text JOIN to 12345 to receive offers”) — allowed for this use case, provided the keyword prompt includes your brand name, purpose of messages, and “Reply STOP to unsubscribe.” ❌ Verbal consent cannot be used for marketing messages. |
Compliance requirements |
Express written consent must include:
|
Examples of compliant consent wording |
Web form: “By checking this box, I agree to receive marketing text messages (e.g. offers, discounts) from
SMS keyword: “Text JOIN to 12345 to receive promotional text messages from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Customer care/support
Customer care messages are service-related communications sent to help customers with ongoing requests or updates.
Use this category if your SMS messages provide support information, appointment reminders, service updates, or follow-ups after a customer interaction.
These messages are transactional in nature — they must not contain any marketing or promotional content.
Category |
Details |
Accepted opt-in types |
Customer care messages can be sent to customers who have provided consent through: ✅ Web form (e.g. contact or booking form) ✅ Paper form (e.g. in-person service request) ✅ Mobile / QR code ✅ Verbal consent (during customer service calls) ❌ Via text (SMS keyword) is not allowed for this use case because customer care messages are service-triggered, not customer-initiated.
|
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
|
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Account notifications
Account notification messages are transactional communications that keep customers informed about their account activity.
Use this category if your SMS messages provide updates on account changes, billing, renewals, password resets, or login alerts.
These messages must not include marketing or promotional content and should only be sent to customers who have opted in or agreed to receive account-related notifications.
Category |
Details |
Accepted opt-in types |
Account notifications can be sent to customers who opt in through: ✅ Web form (e.g. during signup or profile update) ✅ Paper form (e.g. account registration form) ✅ Mobile / QR code ✅ Verbal consent (e.g. given during onboarding or support calls) ❌ Via text (SMS keyword) is not allowed for this use case, since account updates are automatically generated and not initiated by the customer.
|
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
|
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
2FA (Verification)
2FA (Two-Factor Authentication) messages are security-related, one-time communications sent to verify a customer’s identity during login, signup, or sensitive account actions.
Use this category if your SMS messages send one-time passcodes (OTPs) or authentication links.
These messages are transactional and time-sensitive — they must not contain any marketing content or additional information beyond the verification purpose.
Category |
Details |
Accepted opt-in types |
2FA messages can be sent to customers who have consented through: ✅ Web form (e.g. during account signup or login) ✅ Paper form (e.g. account setup form in regulated environments) ✅ Mobile / QR code (e.g. secure registration page) ✅ Verbal consent (e.g. agent confirmation during onboarding) ❌ Via text (SMS keyword) is not allowed for this use case, since authentication messages must be triggered by a verified action (e.g. login attempt).
|
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By signing up, I agree to receive one-time verification codes from Verbal: “To complete your registration, we’ll send a one-time verification code by text from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Delivery notifications
Delivery notification messages are transactional communications that keep customers informed about the status of their orders or deliveries.
Use this category if your SMS messages provide order confirmations, shipment tracking updates, or pickup reminders.
These messages should only contain delivery-related information and must not include promotional or upsell content.
Category |
Details |
Accepted opt-in types |
Delivery notifications can be sent to customers who opt in through: ✅ Web form (e.g. at checkout or in customer portal) ✅ Paper form (e.g. in-store order form) ✅ Mobile / QR code (e.g. tracking subscription link) ✅ Verbal consent (e.g. confirmed during customer service or pickup call) ❌ Via text (SMS keyword) is not allowed for this use case because delivery updates are transactional and system-generated.
|
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By providing my phone number, I agree to receive order and delivery updates from Verbal: “Can we send you text updates about your delivery from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Event
Event messages are informational or reminder communications related to upcoming or ongoing events.
Use this category if your SMS messages provide event confirmations, schedule updates, attendance reminders, or cancellations.
These messages are considered transactional when they help participants stay informed — but promotional messages about buying tickets or joining new events fall under Marketing instead.
Category |
Details |
Accepted opt-in types |
Event messages can be sent to customers who opt in through: ✅ Web form (e.g. event registration page) ✅ Paper form (e.g. in-person sign-up sheet ✅ Mobile / QR code (e.g. registration link or poster scan) ✅ Via text (SMS keyword) (e.g. “Text RSVP to 12345 to get event reminders”) ✅ Verbal consent (e.g. confirmed over phone during registration) |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By registering, I agree to receive event reminders and updates from Verbal: “Can we text you event reminders and updates from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Charity/Non-profit
Charity and non-profit messages are informational or community-focused communications sent by registered non-profit or charitable organizations.
Use this category if your SMS messages provide donation appeals, volunteer updates, campaign results, or event reminders related to charitable or non-profit work.
Messages must remain non-commercial — they can promote giving or participation, but not products or paid services.
Category |
Details |
Accepted opt-in types |
Charity and non-profit messages can be sent to subscribers who opt in through: ✅ Web form (e.g. donation page or volunteer sign-up form) ✅ Paper form (e.g. physical donation form or in-person event form) ✅ Mobile / QR code (e.g. campaign poster scan) ✅ Via text (SMS keyword) (e.g. “Text DONATE to 12345 to support our campaign”) ✅ Verbal consent (e.g. confirmed during phone donation pledge) |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By signing up, I agree to receive donation and volunteer updates from Verbal: “Can we text you updates about our charity programs or volunteer events at |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Fraud alert messaging
Fraud alert messages are security or account protection communications that warn customers about potential suspicious activity.
Use this category if your SMS messages include fraud alerts, security breach notifications, or unusual account activity warnings.
These are time-sensitive, transactional messages that must only contain essential security information — not promotions, marketing content, or unrelated updates.
Category |
Details |
Accepted opt-in types |
Fraud alert messages can be sent to customers who opt in through: ✅ Web form (e.g. during account creation or security setup) ✅ Paper form (e.g. account or service registration form) ✅ Mobile / QR code (e.g. digital onboarding form) ✅ Verbal consent (e.g. confirmed during a support or verification call) ❌ Via text (SMS keyword) is not allowed, since fraud alerts are automated and not customer-initiated. |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By registering, I agree to receive security alerts and fraud notifications from Verbal: “Can we send you text alerts from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Higher education
Higher education messages are informational or administrative communications sent by colleges, universities, or post-secondary institutions.
Use this category if your SMS messages share admissions updates, enrollment notices, course reminders, or campus alerts.
These messages must only contain academic or institutional information — not promotional material for unrelated programs or third parties.
Category |
Details |
Accepted opt-in types |
Higher education messages can be sent to students, applicants, or staff who opt in through: ✅ Web form (e.g. admissions application or student portal) ✅ Paper form (e.g. course registration form) ✅ Mobile / QR code (e.g. campus event or admissions form) ✅ Verbal consent (e.g. confirmed during enrollment calls) ❌ Via text (SMS keyword) is not allowed for this use case, as academic notifications are administrative, not opt-in marketing. |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By submitting this form, I agree to receive admissions, enrollment, or academic updates from Verbal: “Can we send you admissions or enrollment updates from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
K12 education
K12 education messages are school-related communications sent by primary or secondary schools to parents, guardians, or students.
Use this category if your SMS messages share attendance notifications, school announcements, event reminders, or emergency alerts.
These messages must only contain school or administrative updates — not marketing for third-party services or fundraising promotions.
Category |
Details |
Accepted opt-in types |
K12 education messages can be sent to parents, guardians, or students who opt in through: ✅ Web form (e.g. school enrollment or parent portal) ✅ Paper form (e.g. school registration or consent form) ✅ Mobile / QR code (e.g. PTA or school event link) ✅ Verbal consent (e.g. provided during parent-teacher or administrative calls) ❌ Via text (SMS keyword) is not allowed, since school messages are administrative and not promotional subscriptions. |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By submitting this form, I agree to receive school updates and announcements from [Your school name]. Msg & data rates may apply. Reply STOP to unsubscribe. ”Paper form: “By signing below, I agree to receive SMS notifications from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Polling/Non-political voting
Polling and non-political voting messages are survey or feedback-related communications used to collect opinions or responses from customers, members, or communities.
Use this category if your SMS messages include satisfaction surveys, experience feedback, or participation in research or internal polls.
Messages must remain non-commercial and cannot include promotional content, incentives, or references to political topics.
Category |
Details |
Accepted opt-in types |
Polling and non-political voting messages can be sent to participants who opt in through: ✅ Web form (e.g. signup or feedback form) ✅ Paper form (e.g. event feedback sheet) ✅ Mobile / QR code (e.g. survey or research participation link) ✅ Verbal consent (e.g. during customer service or research calls) ✅ Via text (SMS keyword) (e.g. “Text VOTE to 12345 to participate in our survey”)
|
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By submitting this form, I agree to receive survey or feedback-related messages from Verbal: “Can we text you a short survey from [Your organization name] after your visit? Msg & data rates may apply. You can reply STOP anytime.” |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Political / Election campaign
Political and election campaign messages are politically related communications sent by registered political parties, candidates, or campaign organizations.
Use this category if your SMS messages include voter outreach, election reminders, fundraising appeals, or candidate updates.
These messages are highly regulated — they require express written consent from each recipient and must clearly identify the sender.
Only political entities or authorized representatives are permitted to use this use case.
Category |
Details |
Accepted opt-in types |
Political or election campaign messages can be sent to supporters who opt in through: ✅ Web form (e.g. campaign website sign-up) ✅ Paper form (e.g. in-person event or donation form) ✅ Mobile / QR code (e.g. campaign poster or event link) ✅ SMS keyword (e.g. “Text VOTE to 12345 to join [Candidate Name]’s campaign updates”) ❌ Verbal consent cannot be used for political messaging. |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By signing up, I agree to receive political campaign messages from ”SMS keyword: “Text SUPPORT to 12345 to receive election updates from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Public service announcement
Public service announcement (PSA) messages are non-commercial, informational communications sent by public agencies, government bodies, or community organizations.
Use this category if your SMS messages provide emergency alerts, safety updates, health advisories, or community service notifications.
These messages are strictly for public awareness and cannot include promotional or political content.
Category |
Details |
Accepted opt-in types |
Public service announcements can be sent to recipients who opt in through: ✅ Web form (e.g. city portal, safety registration form) ✅ Paper form (e.g. event or program sign-up sheet) ✅ Mobile / QR code (e.g. public awareness campaign poster) ✅ Via text (SMS keyword) (e.g. “Text ALERT to 12345 to receive emergency notifications”) ✅ Verbal consent (e.g. registration over the phone for local alerts) |
Compliance requirements |
Consent must include:
|
Examples of compliant consent wording |
Web form: “By subscribing, I agree to receive community updates and safety alerts from Verbal: “Would you like to receive public safety or emergency alerts from |
Sample message content |
✅ Compliant examples:
❌ Non-compliant examples:
|
Choosing the right opt-in type
Each use case requires a specific opt-in type and matching proof format to show how your customers gave consent to receive SMS messages.
Carriers verify these three elements together — if the proof doesn’t match the selected opt-in type or declared use case, your submission may be rejected.
Decision helper: choose the right opt-in type and proof format
Use case |
Recommended opt-in type |
Proof format |
Web form / QR code / SMS keyword |
Public URL of the webpage showing consent text, or screenshot of the form with visible opt-in statement (“By subscribing, I agree to receive marketing messages…”) |
|
Verbal / Paper form / Web form |
Screenshot or public URL of service form showing consent, or CRM note / signed document confirming verbal consent |
|
Web form / Paper form / Verbal |
Public URL or screenshot of account registration page with opt-in statement |
|
Web form |
Screenshot or public URL of login/verification page showing consent message (“By continuing, I agree to receive verification codes…”) |
|
Web form / Verbal |
Screenshot or public URL of checkout/order confirmation page showing consent to receive delivery updates |
|
Web form / QR code / SMS keyword |
Public URL or screenshot of registration form, RSVP page, or event poster showing consent message |
|
Web form / QR code / SMS keyword |
Public URL of donation or campaign page, or screenshot showing opt-in statement |
|
Web form / Paper form / Verbal |
Screenshot, document, or URL of account registration page showing security consent clause |
|
Web form / Paper form / Verbal |
Public URL or screenshot of enrollment or admissions form showing opt-in |
|
Paper form / Web form / Verbal |
Signed parent consent form, or screenshot/URL of school portal opt-in page |
|
Web form / QR code / SMS keyword |
Public URL or screenshot of survey participation page showing opt-in text |
|
Web form / Paper form / SMS keyword |
Public URL or screenshot of campaign signup form or keyword opt-in prompt |
|
Web form / QR code / SMS keyword |
Public URL or screenshot of subscription form or awareness campaign page showing opt-in message |
💡 Tip:
Your proof can be either a public webpage URL or a screenshot stored in a publicly accessible location (e.g. Google Drive or company knowledge base).
If you use a screenshot link, make sure the file is shared with “Anyone with the link” access so reviewers can open it without login restrictions.
Web form
Web form opt-ins are one of the most common and reliable ways to collect SMS consent.
Customers provide their phone number through an online form — such as a signup page, checkout form, or contact form — and agree to receive specific types of text messages.
This method is accepted for most use cases, including marketing, events, customer care, delivery updates, and notifications.
Category |
Details |
When to use |
Use when customers enter their phone number on your website or landing page and check a box or see a statement giving consent. Common examples include:
|
What your proof must show |
The web page or form must clearly display: ✅ Your business or organization name ✅ The purpose of the messages (e.g. marketing, delivery updates, event reminders) ✅ A consent statement such as “By providing my number, I agree to receive text messages from ✅ Disclosure that “Msg & data rates may apply” ✅ An opt-out instruction (“Reply STOP to unsubscribe”) visible before submission
|
Example |
Example: Marketing web form “By checking this box, I agree to receive marketing text messages (e.g. offers, promotions) from |
Via text (Keyword)
SMS keyword opt-ins allow customers to initiate consent directly by texting a keyword (e.g. “JOIN,” “SUBSCRIBE,” or “RSVP”) to your toll-free number.
This action counts as express written consent, as the customer explicitly agrees by sending the keyword.
This method is accepted for use cases such as Marketing, Event, Charity / Non-profit, Polling / Non-political voting, Political / Election campaign, and some Public service announcements.
It’s not allowed for transactional or system-triggered messages (e.g. 2FA, delivery notifications, account alerts).
Category |
Details |
When to use |
Use when your audience can text a keyword to your toll-free number to subscribe or join a specific message list. Common examples include:
This method is not allowed for customer care, delivery notifications, or verification messages. |
What your proof must show |
Your keyword opt-in prompt must include: ✅ The keyword and toll-free number (“Text JOIN to 12345”) ✅ Your business or organization name ✅ The purpose of the messages (e.g. marketing, event reminders, donations) ✅ Disclosure that “Msg & data rates may apply” ✅ An opt-out instruction (“Reply STOP to unsubscribe”) Your proof can be either:
|
Example |
Example: Marketing opt-in “Text JOIN to 12345 to receive exclusive offers and promotions from “Text DONATE to 12345 to support |
⚠️ Important:
If your keyword prompt does not show the full disclosure text (“Msg & data rates may apply” and “Reply STOP to unsubscribe”), your submission will be rejected. Always include these lines wherever the keyword is displayed — whether on your website, printed poster, or social post.
Mobile/QR code
Mobile or QR code opt-ins let customers scan a QR code or tap a link to open a webpage, form, or chat window where they can provide their phone number and consent.
This method is common for events, marketing campaigns, charity drives, and public service announcements, where users engage offline or through printed materials.
Category |
Details |
When to use |
Use when customers scan a QR code or tap a link that leads to an opt-in form or message prompt. Common examples include:
|
What your proof must show |
The QR or mobile landing page must include: ✅ Your business or organization name ✅ The purpose of the messages (e.g. offers, updates, reminders) ✅ A consent statement such as “By subscribing, I agree to receive SMS messages from ✅ Disclosure that “Msg & data rates may apply” ✅ An opt-out instruction (“Reply STOP to unsubscribe”) Your proof can be either:
|
Example |
Example 1: Event poster Poster text: “Scan to RSVP and get event updates from Example 2: Charity campaign “Scan this code to join |
Paper form
Paper form opt-ins are used when customers provide written consent on a physical form, such as a sign-up sheet, service agreement, or donation form.
This method is accepted for most use cases, including customer care, education, charity/non-profit, and event registration, but not for marketing campaigns that require express digital consent via form or keyword.
Category |
Details |
When to use |
Use when consent is collected in person on a physical document. Common examples include:
|
What your proof must show |
The signed document or form must clearly include: ✅ Your business or organization name ✅ The purpose of the messages** (e.g. event reminders, school updates, donation alerts) ✅ A written consent statement, such as “I agree to receive text messages from ✅ Disclosure that “Msg & data rates may apply” ✅ An opt-out instruction, where space allows (“Reply STOP to unsubscribe”) ✅ A signature and date from the customer Your proof can be either:
Make sure handwriting and consent text are visible and legible. |
Example |
Example: Volunteer sign-up sheet Printed text: |
⚠️ Important:
If your paper form collects multiple types of consent (e.g. email and SMS), make sure the SMS checkbox or text is separate and clearly labeled. Combining multiple channels into one consent statement can lead to rejection.
Verbal
Verbal opt-ins apply when customers give spoken consent during a phone or in-person conversation.
This method is common for customer care, support, account notifications, education, charity, and service-based use cases.
Verbal consent is not allowed for marketing messages or any campaign that requires express written consent.
Category |
Details |
When to use |
Use when consent is given verbally over the phone or in person during service interactions. Common examples include:
|
What your proof must show |
You must keep a record of the consent, which can be: ✅ A CRM note or ticket log showing when and how the customer gave verbal consent ✅ A recorded call (if applicable) with a clear statement of consent ✅ Internal documentation that includes the date, agent name, and customer confirmation Proof should include the full consent statement read to the customer and their confirmation. Screenshots of CRM logs or internal records can be uploaded as proof (ensure the file is publicly accessible via Google Drive or similar). |
Example |
|
💡 Tip:
If your team collects verbal consent, create a standardized call script and require agents to record consent in the CRM every time. Carriers often request to see the exact wording and date when verbal consent was given.
Preparing your opt-in policy image URL
Your opt-in policy image URL shows carriers exactly how customers give consent to receive SMS messages from your business.
You only need to submit one proof file or link per toll-free verification form — just make sure it clearly matches your selected use case and opt-in type.
Accepted proof formats
You can provide:
- A public URL (e.g. a web form, campaign page, or hosted screenshot link).
- A screenshot or scanned image uploaded to a public drive (e.g. Google Drive shared with “Anyone with the link”).
Carriers must be able to view the proof without logging in. Private links or cropped screenshots are not accepted.
Your proof must clearly show
- Your business or organization name
- The purpose of your messages
- The consent statement (e.g. “By signing up, I agree to receive text messages…”)
- Disclosure that “Msg & data rates may apply”
- Opt-out instruction, usually “Reply STOP to unsubscribe”
⚠️ Important:
The opt-in proof you submit must match the information you entered in your form — including use case, consent wording, and message content. Mismatched or incomplete proof is the most common reason for rejection.
Common rejection reasons
Rejection message |
What it means |
How to fix it |
Opt-in does not match the use case |
The way customers give consent doesn’t align with the type of messages you send. |
Ensure your opt-in page clearly shows what kind of messages customers will receive (e.g. marketing, notifications, alerts). |
Marketing messages require express written consent |
Promotional messages require a user’s written or digital opt-in (not implied consent). |
Add a checkbox or consent statement on your website form, and link it under “Opt-in policy image URLs.” |
Disallowed content – Third-party lead generation or multi-level marketing |
Carriers block certain message types such as loan offers, crypto, affiliate marketing, and MLM. |
Only submit messages for your own business and customers who directly opt in. |
Invalid or inaccessible website URL |
The provided link cannot be accessed or doesn’t show opt-in information. |
Ensure your URLs are live, start with https://, and publicly show your opt-in process or brand identity. |
Frequently asked questions
How long does the toll-free verification process take?
- Most reviews take 3–5 business days, but processing can take longer if additional review or clarification is needed.
- If your opt-in proof or message content doesn’t clearly match your use case, the carrier will reject your request. You will be required to delete and resubmit your verification form again.
- To delete your verification, visit this Help Center article.
Can I send messages before my number is verified?
- Messaging will not be available until your phone number has been verified
- If your submission is rejected, unverified traffic may be blocked or filtered by carriers.
Do I need separate verification for different message types?
- Yes. Each toll-free number can only be verified for one primary use case (for example, marketing or customer care).
- If your business sends multiple message types, purchase multiple phone numbers and submit a separate verification form for each phone number.
Can I use the same opt-in proof for multiple submissions?
- You can reuse the same opt-in proof only if the consent wording and message purpose are identical.
- For example, a general “marketing” opt-in form can cover multiple marketing campaigns — but not service notifications or 2FA messages.
- Always ensure your proof matches the use case you select.
What if my opt-in is collected offline or in person?
- If you collect consent via a paper form or verbal agreement, include a photo, scan, or documented process as your Opt-in Policy Image URL.
- Make sure it clearly shows the consent text and how it’s recorded (e.g., a signed form or CRM note with date/time).
Can I edit or resubmit my verification form?
- Yes. If your application is rejected, you will need to delete your current verification form, and re-submit your opt-in proof, description, or message content for review.
- To delete your verification, visit this Help Center article.
Who receives verification updates?
- Status updates are sent to the email address you entered in the form under “Email for notifications”.
- SleekFlow and the carrier do not send marketing emails through this channel — only status notifications.
Do I need to reverify my number in the future?
- No, toll-free verification is a one-time process per number, as long as your use case and consent method remain the same.
- If you change your message purpose (for example, from support to marketing), you’ll need to submit a new verification request.