SMS Verify and Verify Plus: New version includes Intelligence risk insights and improves latency
Products affected: SMS Verify and Verify Plus
Changes: Telesign introduced a new version of SMS Verify. The previous version was deprecated on 3/30/23 GMT. In the new version, some features (the 229, 230, and 233 statuses and the Verify Plus packages) are returned asynchronously in the Delivery Receipt. If you are an SMS Verify customer who logged in and had blocklisting and/or Verify Plus active before 3/30/23 GMT, you are pinned to the old version to allow you enough time to plan integration changes. All other customers are pinned to the new version.
New features: In the new version of SMS Verify, Verify Plus uses Intelligence 2.0 which includes Intelligence's
risk_insights package. The
risk_insights package will provide you with additional detail explaining why Telesign issued a particular score.
Additional info: To upgrade to the newest version of SMS Verify (and use Intelligence 2.0), reach out to our Customer Support Team. Contact our Customer Support Team if you have questions about which procedure you should use for your integration.
How this may affect you:
- New SMS Verify version: The new version improves the latency for Verify Plus by 30% over the previous version. Check that your integration does not depend on parsing the HTTP response for the status codes listed above or for Verify Plus packages if you are pinned to this version. If your integration does, it needs to be changed or it may break. Intelligence 2.0 uses a different score scale which you can find on this page. See this procedure for screening recipients using Verify Plus.
- Existing SMS Verify version: If you are pinned to this version, you can continue to use your current integration but you should plan to transition to the new behavior. If you want to enjoy the advantages of Intelligence 2.0 and are pinned to the old version, you will need to either prepare to transition to the new version and ask Customer Support to switch you to the new version or ask Customer Support to upgrade you to Intelligence 2.0 and then adjust your integration accordingly. When you transition to the new behavior, check that your integration does not depend on parsing the HTTP response for the status codes listed above or for Verify Plus packages. If it does, it needs to be updated or it may break. Intelligence 2.0, which is used in the new version of SMS Verify, uses a different score scale which you can find on this page. While you remain on the old version of SMS Verify, you'll use this legacy procedure for screening recipients using Verify Plus but once you transition, you'll use this new procedure for screening recipients.