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.

Who is affected: Customers using the Telesign Full-service Python SDK
Products affected: Telesign Full-service Python SDK

Changes

• The Telesign Full-service Python SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service Python SDK provides support for additional communication channels, including Rich Communication Services (RCS), WhatsApp, Viber, MMS, SMS, and email.

How this may affect you

• Send messages to additional channels: You can send messages on your users’ channels of choice using Messaging.
• Send one-time passcodes (OTPs) to additional channels: You can send OTPs on your users’ channels of choice using the Verify API.
• Maintaining compatibility: This change does not impact the use of other APIs through the Telesign Full-service Python SDK.

Additional information

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

Who is affected: Customers using the Telesign Full-service C# SDK and Telesign Self-service C# SDK
Products affected: Telesign Full-service C# SDK and Telesign Self-service C# SDK

Changes

• The Telesign Full-service C# SDK and Telesign Self-service C# SDK now support the latest .NET Core versions. The .NET Core supported versions for both C# SDKs are:

  • .NET Core 6, 7, 8, and 9.

• .NET Core warnings resolved: Some versions of .NET Core generated warnings. This issue has been fixed.

• The Telesign Full-service C# SDK and Telesign Self-service C# SDK now support .NET Framework v4.8+. Both SDKs no longer support the following older .NET Framework versions:

  • .NET Framework v4.5.2, v4.6, v4.6.1, v4.6.2, v4.7, v4.7.1, and v4.7.2.

How this may affect you

• Latest version support for .NET Core: If you are using modern versions of .NET/.NET Core actively supported by Microsoft, you can now integrate with Telesign with full confidence that Telesign supports your framework.
• .NET Framework users may need to update: If the .NET Framework version you are using is no longer supported by Telesign (see above), you should update to one of our supported .NET Core or .NET Framework versions.

Additional information

• Full-service C# SDK: Go to its GitHub Readme for the latest version range support or go to its changelog for more information.
• Self-service C# SDK: Go to its GitHub Readme for the latest version range support or go to its changelog for more information.
• For additional assistance, contact us.

Who is affected: Customers using the Telesign Full-service Node.js SDK
Products affected: Telesign Full-service Node.js SDK

Changes

• The Telesign Full-service Node.js SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service Node.js SDK provides support for additional communication channels, including Rich Communication Services (RCS), WhatsApp, Viber, MMS, SMS, and email.

How this may affect you

• Send messages to additional channels: You can send messages on your users’ channels of choice using Messaging.
• Send one-time passcodes (OTPs) to additional channels: You can send OTPs on your users’ channels of choice using the Verify API.
• Maintaining compatibility: This change does not impact the use of other APIs through the Telesign Full-service Node.js SDK.

Additional information

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

Who is affected: Customers using the Telesign Full-service Ruby SDK
Products affected: Telesign Full-service Ruby SDK

Changes

• The Telesign Full-service Ruby SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service Ruby SDK provides support for additional communication channels, including Rich Communication Services (RCS), WhatsApp, Viber, MMS, SMS, and email.

How this may affect you

• Send messages to additional channels: You can send messages on your users’ channels of choice using Messaging.
• Send one-time passcodes (OTPs) to additional channels: You can send OTPs on your users’ channels of choice using the Verify API.
• Maintaining compatibility: This change does not impact the use of other APIs through the Telesign Full-service Ruby SDK.

Additional information

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