Who is affected: Intelligence customers who need to migrate to Intelligence Cloud API.
Products affected: Intelligence and Intelligence Cloud API

Changes

• Intelligence Cloud API launched: Telesign has launched a new Intelligence cloud-powered platform that will replace the current "on-prem" Intelligence platform. This version of Intelligence has significantly lower latency and enhanced security, reliability, and scalability.
• Easy migration: To migrate to the cloud-powered version, update your Intelligence endpoint to: https://detect.telesign.com/intelligence/phone and start submitting the phone number in the API request body (instead of in the URL). For more details about the migration please see this support center article.
• Existing Intelligence version is deprecated: The existing "on-prem" Intelligence is deprecated. The existing reference page will remain available for reference until the migration to Intelligence Cloud API is complete.
• TeleBureau how-to pages removed: TeleBureau is not used with the Intelligence Cloud API so the pages related to its use are not included in the new Intelligence Cloud guide pages. This change does not affect other products which use TeleBureau.

How this may affect you

• New customers: New customers will get onboarded to Intelligence Cloud starting on Oct 1st 2025.
• Existing customers: Existing customers are requested to update their endpoint to the new endpoint for Intelligence Cloud API, and start submitting the phone number in the API request body (instead of URL). See Intelligence Cloud - Submit a phone number to evaluate for more information on the new endpoint.

Additional information

• For an overview of Intelligence Cloud API, see Intelligence Cloud - Overview.
• The developer docs reference page is Intelligence Cloud - Submit a phone number to evaluate .
• More details about the migration process can be found in this support center article.
• If you are new to Telesign or have any questions about Intelligence Cloud API, please reach out to your dedicated CSM or contact Customer Support.

Who is affected: Fraud teams, product teams, risk analysts, and operations leaders managing risk based decisioning logic via API integration
Products affected: Phone ID and Intelligence

Changes

• Flow Builder feature launched on the Protect Platform: This new feature enables you to create, customize, and manage risk based decisioning logic using Phone ID and Intelligence alongside third-party data sources via API integration. Use the combination of Phone ID and Intelligence with external signals (e.g., KYC providers, IP reputation APIs, device fingerprinting tools) to increase decision accuracy.
• A no-code/low-code solution that speeds up decision making workflows: Flow Builder, as a no-code/low-code feature, allows your fraud teams, product teams, risk analysts, and operations leaders to create and manage complex workflows without writing code, so that they can accelerate and improve decision-making precision while reducing reliance on engineering resources.
• Enhanced usability for non-technical users: Drag and drop flow creation allows your fraud analysts, risk managers, and other non-engineers to build complex decision trees without writing code. From there, your developers can implement the flows created by their colleagues in their applications with just a few steps. Flow Builder also reduces dependence on development teams, enabling faster iteration and experimentation.
• No Advanced learning required: Ready to go templates available in Flow Builder make it easy for you to implement flows as soon as you sign into the Protect Platform.
• Faster time-to-market: You can deploy new risk logic and workflows in hours instead of weeks to adapt quickly to emerging fraud patterns or regulatory requirements.
• Easy integration with third-party tools: Flow Builder natively supports external APIs to enable seamless integration of any service without deep development work. This encourages robust workflows, data enrichment and multi-source validation.
• Work with multiple risk signals: Use the drag and drag controls in Flow Builder to combine multiple risk signals, test decision strategies, and adapt instantly to emerging threats or shifting regulatory environments.

How this may affect you

• Select regional availability: The Protect Platform and Flow Builder are currently available for customers with end users in select countries. To find out if Flow Builder is available in your region, contact a Telesign expert. Available for full-service accounts only.

Additional information

• If you are new to Telesign OR have questions regarding Flow Builder or the Protect Platform, please contact us.

Who is affected: PingOne customers who need to migrate to a new telephony provider.
Products affected: SMS and voice

Changes

• PingOne customers can use Telesign as their telephony provider: Effortlessly integrate with PingOne using Telesign API solutions to deliver SMS and voice OTP messages. Telesign's integrated fraud prevention solution will help you "bring your own platform" to PingOne, replacing Ping Identity's previous internal platform for SMS and voice telephony.
• Easy migration: Telesign offers easy migration and scalability for existing PingOne customers choosing a new telephony service provider to send OTPs and ARN SMS messages. See our guide pages listed below for our recommended settings when using the PingOne platform.
• Send default SMS and voice messages: Use the SMS Verify API and the Voice Verify API endpoints with PingOne to send one-time passcodes (OTPs) using a default template. See Ping Telephony – Send OTP-only SMS and voice messages for more information.
• Send custom OTP and ARN SMS messages: Use the SMS endpoint to send customized one time passcode (OTP) and ARN (notification) messages. See Ping Telephony – Create custom OTP and ARN messages for more information and a list of common use cases.

How this may affect you

• PingOne customers need to bring their own telephony provider: Effective January 1, 2025, Ping Identity announced that all PingID and PingOne customers using Ping’s Telephony account to send SMS and voice messages with MFA will need to transition to a Bring Your Own Telephony (BYOT) model before their renewal date or by December 31, 2025. Telesign is offering the Ping BYOT solution to fulfill this need and integration directly with PingOne to deliver OTPs via SMS and voice.

Additional information

• If you are new to Telesign OR have questions regarding integrating with PingOne using Telesign's telephony solution, please contact us.

Who is affected: Customers using Messaging
Products affected: Messaging

Changes

• Three templates added to Messaging: These templates allow you to use Telesign Messaging to send a Viber message that includes a video file that you host to an end-user.
• Video with fallback channels: Use the video template to send a Viber message with a video with a fallback channel option (SMS, MMS, or WhatsApp).
• Video and text Use the text_video template to send a Viber message with a video and text.
• Video, text, and button Use the url_action_video template to send a Viber message with video, text, and a button.
• Accepted video formats: Viber accepts .3gp, .m4v, .mov, .mp4 videos.
• Video file size: You may include a video file that is up to 200 MB.

How this may affect you

• Increased support for videos: This changes allows you to send videos when using Messaging to send messages via Viber instead of just links.

Additional information

• Go to Messaging - Send video with Viber, Messaging - Send video and text with Viber, and Messaging - Send video, text, and button with Viber in our developer documentation for more information on these new templates.
• To set up Viber in your account for use with Messaging, see Messaging - Set up Viber for your account .
• If you would like to enable Telesign Messaging for your account, please contact us

Who is affected: Customers using the Telesign SMS for Dynamics 365 app
Products affected: Microsoft Dynamics 365 - Marketing, Sales, Customer Service

Changes

• New version: v1.8 of the Telesign SMS for Dynamics 365 app is now available for installation in the Microsoft AppSource store.
• Architectural adjustments related to platform compatibility: This release focuses solely on architectural adjustments that allow the application to run without relying on the Marketing module.
• Changes to dependencies and integrations: All dependencies and integrations related to the Dynamics 365 Marketing module (including Customer Journey, Subscription Lists, Real-Time Marketing, and related entities) have been removed.
• Marketing module no longer used: The application no longer requires or interacts with entities or components from the Marketing module.
• Sales and Customer services apps: The solution now operates exclusively within the Sales and Customer Service apps in Dynamics 365.

How this may affect you

• Reduced license dependency and complexity: If you use the Sales or Customer Service apps, you can now deploy and use the solution without needing the Marketing module which significantly reduces license dependency and complexity.
• Marketing-specific functionality removed: If you are currently using Marketing-specific functionality (e.g., Customer Journeys, Marketing Lists, keyword-based automation via Marketing), you should be aware that upgrading to this version will remove those capabilities from your environment.
• Prior Marketing-related logic configurations will not function after upgrade: Upon upgrade, any previously configured Marketing-related logic will no longer function, as related entities and processes are no longer part of the solution. See the Compatibility notice below.
• Documentation: Users still on previous versions can refer to the "Legacy Instructions for Marketing Module Support" section in the documentation for historical guidance.

❗️

WARNING

Compatibility notice:

• This version (v1.8) of the TeleSign SMS solution has been redesigned to work exclusively with Dynamics 365 Sales and Customer Service modules.
• If your organization currently relies on marketing module features in Dynamics 365 (such as Customer Journeys, subscription list opt-ins/opt-outs, or marketing triggers), please be advised that these functionalities are no longer supported in v1.8.
• Users still on previous versions can refer to the "Legacy Instructions for Marketing Module Support" section in the documentation for historical guidance.
  
  

By installing or upgrading to this version:

• All legacy marketing-based configurations and capabilities will be permanently overwritten.
• There is no backward compatibility with older Marketing-based journeys or automation.

Additional information

• If you would like more information about Telesign SMS for Dynamics 365 or this version, please contact us.
• The Telesign SMS for Dynamics 365 app is available in the Microsoft AppSource store.
• The Telesign Voice Add-on for Dynamics 365 app is also available in the Microsoft AppSource store.

Who is affected: Full-service customers
Products affected: Phone ID

Changes

• New identity attribute added to Phone ID: The Active Call Status identity attribute allows you to check if the end user is actively engaged in an ongoing call. This helps prevent fraud by using ongoing call activity and type to determine the presence of Authorized Push Payment fraud.
• Use case: This identity attribute allows banks and and companies in the eCommerce/mCommerce industry to identify users who are suspected of being actively engaged in a conversation with a scammer.
• Flexible control: Active Call Status allows you to take extra steps when the end user initiates a transaction. If the end user is actively engaged in a conversation with a potential scammer, you can decide whether you want to allow the transaction.
• Information provided by Active Call Status: Based on the phone number provided in the API request, Active Call Status provides a true/false response (indicating whether the end user is participating in a call). It provides the information on whether the end user initiated or received the call and its duration.
• Coordinated coverage: Active Call Status works with other Phone ID identity attributes through the same API.

How this may affect you

• Select regional availability: This feature is currently available for customers with end users in select countries. To find out if this feature is available in your region, contact a Telesign expert.

Additional information

• Go to Phone ID - Identity attributes: Active Call Status in our developer documentation for more information on this new identity attribute.
• Learn more about Phone ID identity attributes .
• If you would like to enable Active Call Status for your account, please contact us.

Who is affected: Verify API customers
Products affected: Verify API

Changes

• Callbacks available for the Push Verify feature: The Telesign Verify SDK now allows you to use callbacks for verification push notifications to authenticate your users.
• Comprehensive callback events: Through automatic analysis of two primary events—delivery and message read—the SDK internally manages a broader set of events. This reduces development complexity and streamlines integration.
• Flexible integration options: Both Android and iOS platforms now support manual and automatic approaches, with clear guidelines and helper classes to accelerate implementation.

How this may affect you

• Improved analytics and insights: By capturing detailed information about push notification events, the callback service provides valuable analytics that can help refine user engagement strategies and troubleshoot issues more effectively.

Additional information

• Go to our developer documentation for Push Verify and Push Verify callbacks for more information.
• If you would like to enable Push Verify for your account, please contact us.

Who is affected: Customers who opt in to our early access program
Products affected: Verify API

Changes

• Limited release of QR Verify feature: For customers who opt in to our early access program, QR Verify is now available for use with Verify API. Contact a Telesign expert or your Customer Success Manager for more details.
• Cloud-based solution: QR Verify is a cloud-based, modular solution that enhances security and user experience by enabling a streamlined verification process using QR codes. Users verify their identity by scanning a QR code and signing a challenge with their registered mobile app.
• Authenticate users using QR codes: QR Verify provides a secure mechanism for device registration and identity verification using QR codes to securely authenticate your users. Once a user's device is registered with QR Verify, the user can scan a QR code and verify their identity when logging in on your website. QR Verify provides enhanced security for the transaction (no ATO, SIM Swap, or other similar fraud risks).

How this may affect you

• Expands choice of verification methods: This QR based verification alternative provides another highly secured method of verification that allows you to implement MFA for high-risk transactions while keeping your users trust. Use cases include: login, access control, sensitive data management, money transfers, and payments.

Additional information

• Go to our developer documentation for QR Verify and Verify API for more information.
• If you would like to enable QR Verify for your account, please contact us.

Who is affected: Full-service customers
Products affected: Verify API

Changes

• New channel added to Verify API: Voice joins Silent Verify, Push Verify, SMS, WhatsApp, RCS, and email as a channel for Verify API, which allows you to set up phone-based, multi-factor authentication (MFA) using multiple channels and methods.
• Voice expands your verification options: The addition of voice as a Verify API channel provides a phone call as an additional method for authenticating end users via a one-time passcode (OTP).
• Send OTP codes in the language suitable for your end users: Using Text to Speech (TTS), you can select a supported language to specify the language that the service will use when delivering a OTP to your end user. If a language selection isn't provided, the default language, English (US), is used to deliver the OTP.
• Voice expands your channel fallback options: In addition to Silent Verify, Push Verify, SMS, WhatsApp, RCS, and email, voice increases your automated fallback options from one channel to another. For example, if SMS fails or times out because your end user's mobile device isn't working, the OTP can still be sent automatically using a voice call if voice is enabled as a Verify API fallback option.

Additional information

• Go to Verify API - Get started with voice in our developer documentation for more information on this new channel.
• If you would like to enable Verify API for your account and set up a Voice Caller ID that is needed for this channel, please contact us.

Who is affected: Full-service customers who want to use flash calls to complete phone number verification on Android and iOS devices.
Products affected: App Verify API

Changes

• Telesign has reintroduced the App Verify API to Telesign's product lineup. In recent years, this product had been available for limited use and was not available to be added to accounts. Full-service customers can now add this product to their accounts. Contact us or your Customer Success Manager for more details on how to add this product to your account. App Verify API is available for full-service customers only.
• This API allows you to easily integrate frictionless phone number verification on iOS and Android using flash calls. There are two ways you can do verification using App Verify API: Frictionless App Verification (available on Android devices) and Missed Call Verification.
• Our developer docs have been updated with many improvements including new code examples on the reference pages. See App Verify API - Overview for a list of the new pages and updated reference pages. If you have old pages bookmarked, update your links using the links on this page.

Additional information

• Go to our developer documentation for App Verify API for more information.
• If you would like to enable App Verify API for your account, please contact us.