Integrate with PingOne using Telesign's telephony solution
September 3rd, 2025
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.