The carriers responsible for toll-free text messaging in North America mandate verification of toll-free numbers before you can use a toll-free number to send application-to-person (A2P) messages. This change aligns toll-free messaging with 10DLC and short codes, which already have business verification measures in place. The intent is to ensure that message senders on all services are reviewed and that businesses that send messages are documented and verified.
The verification process involves the carrier responsible for verification reviewing the submitted information and either approving or rejecting the application. The process can take up to two weeks.
Irrespective of the volumes of application-to-peer (a2p) messages you intend to send on toll-free numbers, you must verify each toll-free number.
Plivo recommends that you begin sending messages only after a toll-free number has been verified.
How to get toll-free numbers verified
- You can rent messaging-enabled toll-free numbers on the console.
- Once you rent a messaging-enabled toll-free number, you have 2 ways to submit details for verification:
- Via toll-free verification API –
- This is the recommended method if your business has a frequent requirement of toll-free number provisioning
- A submission via API is directly made into carrier systems with no manual review by Plivo team
- As soon as a toll-free number is verified, you will get a call-back and can initiate a2p messaging traffic on-the-go
- Via manual flow –
- You can either submit the toll-free number verification form with relevant details, or
- For bulk toll-free number verification, fill this sheet and share with Plivo support team by creating a ticket. Once we receive your information, we submit it to the carriers for review.
- Via toll-free verification API –
- You can follow the verification status for any toll-free number on the console by visiting Phone Numbers > Active. By default numbers are classified as “unverified”. Once a number is submitted for review, it’s marked “pending verification”.
- When the carrier notifies us of the successful completion of the verification request, we change the status to “verified”.
- If you had submitted the request via the toll-free verification API, you will also get a call back with the terminal status of your verification request – “rejected” or “verified”.
- If the carrier rejects the verification request, we change the status to “unverified”. You should get this update as a callback if the request was submitted via Plivo toll-free number verification API. In case a verification request is rejected and the request was submitted manually, you will get an email from Plivo Support team.
Verified numbers are subject to the least amount of filtering — but that doesn’t mean customers can use them in unapproved ways. All messaging must still comply with best practices for A2P messaging and must not be used for any use case that is not allowed by carriers in the US or Canada.
Once verified, a number does not need to be re-verified for the same use case in the future. If you want to use any given toll-free number for a different or an additional use case, you should submit a new verification request. Failure to do so can be considered noncompliance by the carriers and may result in your messaging services being suspended.
