If your Toll-Free verification request fails for eligible reasons, you can correct and resubmit your request. For a full list of eligible rejection reasons see below. If eligible, you can resubmit your Toll-Free verification after correcting the identified content violation.
Rejection types eligible for resubmission
Each of the following below are rejection reasons for TFN Verification. To resolve these issues, please take the corrective action(s) outlined in the table below, and then re-submit your Toll-Free Verification request with the updated information.
Rejection category |
Rejection reason |
Correction needed |
Content Violation - SHAFT - Alcohol with no robust age gate - Eligible for Resubmission with robust age gate |
Age gate on site or in submission was similar to: “Are you 21+” “Click Yes or No” |
Changing the Age gate to be collecting the Birthday in the form of Month/Day/Year. Alcohol-related content is allowed in the US only for TFN. The minimum legal drinking age is 21 in the US.
Example: Please Enter Your Birthday: MM/DD/YYYY |
Campaign Violation - Age Gate Not Present / Not Acceptable - Eligible for Resubmission with Robust Age Gate implemented |
Age gate on site or in submission was similar to: “Are you 18/21+” “Click Yes or No” |
Changing the Age gate to be collecting the Birthday in the form of Month/Day/Year.
Example: Please Enter Your Birthday: MM/DD/YYYY |
High Risk - Public URL Shortener - Correct to branded URL domain |
URL link is a free public domain link associated with high abuse rates
|
If you are using a URL shortener, we strongly recommend using a proprietary one. The URL shortener should be unique to each business to make it clear to consumers what the content is and where they’re being directed to.
Update URL link to show brand or paste full unshortened link to website
Example: http://bit.ly/12345 -> https://sunshinecafe.com/12345 |
High Risk - Non-secured URL - correct to https:// |
Rejected for insecure URL in message contents - only secure URL links may be sent for A2P Messaging |
Adding the https protocol
Example: sunshinecafe.com -> https://www.sunshinecafe.com |
Missing Information - No messages samples provided |
Sample messages field was filled with “N/A”, “see attached” or not included. Submission should include sample messages of the content that the end-user/mobile handset will be receiving in the SMS. |
Include SMS messages that the end business will be sending out to the customer’s mobile handset.
Example:
|
High Risk - No Business Name (Branded) in the Messages Samples Provided = SPAM |
The message samples provided are not branded with the business name, which may be flagged as spam and/or have the number blocked with the wireless carriers. |
Check if the Business Name is included in the message samples and every message to avoid the number from being filtered or blocked with the wireless carriers.
Example:
|
Invalid Information - Can't Verify Business Information - Correct Business Information / Address / Contact / URL - Eligible for Resubmission |
End-user business information could not be verified, was not provided, is not valid |
Check if the end-user business is registered in their country/state’s database and provide the end business information in all fields
Example:
Please see this page for more information on checking a business address and registration status: 10DLC, Toll-Free and Short Code Number Brand Identity Resources |
Invalid Information - Can't Validate URL - Website is not accessible / not available - Eligible for Resubmission |
Corporate URL link/Website provided did not resolve, is not yet live, says “Coming Soon”, password protected, 404 error… etc. |
Ensure the Corporate URL link/Website is live, working, and publicly accessible
Example: https://www.sinch.com/ |
Invalid Information - ISV Contact Information Provided, Need Assigned End User - Eligible for Resubmission |
Business information provided is an ISV (ISV (Independent Software Vendor/Reseller) and not the actual business name that will be on the TFN’s welcome/confirmation message, HELP message, or STOP message. |
Providing the end-business name, address, first and last name contact, email address, and URL link that will be directly engaging with the SMS subscriber/mobile handset
Example:
|
Opt-in - Not sufficient for campaign type - Express Written Consent Required - Eligible for Resubmission |
Use case is Marketing/Promotional, but does not show express written consent in the opt-in |
Express written consent is when someone explicitly agrees, either in writing or digitally, to receive marketing/promotional messages such as calls or texts.
This approval cannot be part of a transaction, terms of service, or privacy policy page. It must be a stand-alone approval for sending SMS messages when user signs-up.
Example:
Please see this page for more information on opt-in requirements: What opt-in documentation is required for Toll-Free sender verification? |
Opt-in - Consent for messaging is a requirement for service - Eligible for Resubmission |
Opt-in provided does not include language that the mobile user is consenting to receive SMS messaging. Users signing up their email address is not consent for SMS. |
There must be clear and visible language where the customer understands giving their phone number means they are signing up to receive SMS.
At a minimum, the user must be informed something like "By entering your number, you agree to receive text messages…" upon sign-up.
This does not include the customer simply providing their phone number as part of a transaction, filling out a form, agreeing to their T&Cs or Privacy Policy etc.
Please see this page for more information on opt-in requirements: What opt-in documentation is required for Toll-Free sender verification? |
Opt-in - No opt-in provided - Eligible for Resubmission |
|
Please see this page for more information on opt-in requirements: What opt-in documentation is required for Toll-Free sender verification? |
Opt-in is shared with 3rd Parties - Remove language for information sharing / Add language that opt-in is not allowed - Eligible for Resubmission |
Opt-in language and/or Privacy Policy page includes that SMS will come from another business the customer is signing up with but also from other affiliates, partners, etc. |
Opt-in must be 1-to-1, can't be shared with 3rd parties, and can't be implied. Update Opt-in language and Privacy Policy to make it clear that users’ personal info. will not be shared or sold to third parties for the purpose of marketing and/or sweepstakes.
|
Campaign Violation - Single Number Used for Multiple Businesses - please assign a TFN per business - Eligible for resubmission |
One number is being used to send messages for multiple businesses. VSFs should be submitted for one TFN per end business |
Get 1 number for each business
Example:
|
Additional Information Requested - Justification for more than 5 numbers / business |
More than 5 numbers listed with the same business name and address |
Explain why 1 business at 1 location/address needs more than 5 numbers. Are they for different agents at one location? Are they used for different departments in a single location? Different locations (like a franchise) - if so, provide the address to each location
Example:
|
Unverified toll-free numbers (TFNs) and Pending Verification toll-free numbers (TFNs) are subject to industry-wide message blocking. Unverified toll-free numbers are TFNs that have not completed the toll-free sender verification process. Pending Verification toll-free numbers are TFNs where a verification request has been submitted, but the request is pending review and approval.
Note: In the past it was possible to send messages from an Unverified TFN or Pending Verification TFN. However, as a result of industry-wide changes, all toll-free numbers, regardless of the use case, must be Verified to originate traffic.
UNVERIFIED toll-free numbers (TFNs) are subject to industry-wide message blocking, effective November 8, 2023.
PENDING VERIFICATION toll-free numbers (TFNs) are subject to industry-wide message blocking, effective January 31, 2024.
All toll-free numbers (TFNs) must be in a VERIFIED state in order to originate traffic.
Unverified TFNs and TFNs pending verification will be blocked with Sinch error code 64 “Blocked due to exceeded quota”. Please see Toll-Free Delivery Report Errors for a full list of Sinch Toll-Free error codes.