Developer Guide to Toll-Free Verification

The Messaging Compliance API offers an alternative method of toll-free registration via the Twilio Console, but it is better suited for handling large quantities of registrations and integrating into existing application workflows. The messaging industry, along with Twilio, is shifting towards a more compliant and transparent ecosystem to protect users from bad actors, spam, and unwanted communications. Toll-free numbers will enter a Pending state after submission, with sending limits in place until verified, and messages sent through unverified toll-free numbers will be blocked starting January 1, 2024. Developers should use either 10DLC or toll-free numbers, depending on their business needs, and can check the status of their toll-free verification requests by making GET requests to the Verifications endpoint. The Messaging Compliance API supports both registered and unregistered phone numbers, with different parameters required for each scenario. Once verified, toll-free numbers will be approved, but if rejected, developers can edit and resubmit or delete the submission. Twilio is committed to creating a trusted and compliant messaging ecosystem as it continues to evolve.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.