---
title: Creating a Syniverse Channels sender
description: Create a PingOne notification sender that uses channels defined for your Syniverse account.
component: pingone
page_id: pingone:settings:p1_sender_syniverse_channels
canonical_url: https://docs.pingidentity.com/pingone/settings/p1_sender_syniverse_channels.html
llms_txt: https://docs.pingidentity.com/pingone/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-07-30T00:00:00Z
section_ids:
  steps: Steps
  adding-syniverse-notification-tracking-to-pingone-audit-logs: Adding Syniverse notification tracking to PingOne audit logs
---

# Creating a Syniverse Channels sender

Follow these steps to create a PingOne notification sender that uses the channels that have been defined for your Syniverse account.

|   |                                                                                                                                                                                                                              |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Use separate channels for SMS and voice. If you're using both, you must go through the steps on this page twice, once to create a Syniverse Channel sender for SMS and once to create a Syniverse Channels sender for voice. |

## Steps

1. Go to **Settings > Senders**.

2. Click **+** and enter the following options:

   1. In the **Sender Type** list, select **SMS/Voice**.

   2. In the **Provider Type** list, select **Syniverse**.

   3. In the **Twilio Account Type** list, select **Syniverse Channels**.

3. Click **Next**.

4. In the **Provider Configuration** window, enter the following information:

   * **Provider Name**: Enter a meaningful name for your provider.

   * **Access Token**: Enter the access token for the Syniverse account where you've defined channels. PingOne uses the token to retrieve the relevant information for your channels.

5. Click **Verify**. This validates the account to PingOne and populates the **Organization Channels** list from your Syniverse account.

   After the account is successfully verified, **Organization Messaging Services** displays.

6. Select the channel you want to use for sending PingOne notifications.

7. Click **Save**. A **Third-party Service Consent** message shows. Click **I Consent** to proceed and save your changes.

After configuring this sender, add it to a notification policy to control when PingOne uses it for SMS or voice notifications or to use it as a fallback option. Learn more in [Notification Policies](../user_experience/p1_creating_a_notification_policy.html).

## Adding Syniverse notification tracking to PingOne audit logs

To help troubleshoot any potential issues, include Syniverse notification events in the PingOne audit logs. To include Syniverse notification events in the PingOne audit logs:

1. In the list of configured senders, locate your sendert.

2. Click the sender name. The summary of the sender configuration is displayed on the right side of the screen.

3. Copy the URL from the **Address** field.

4. In your Syniverse account:

   1. In the **Delivery Configuration**, paste the URL that you copied from the PingOne **Address** field.

   2. Create two subscriptions: **SCG-Message** and **SCG-Voice-Calls**.

      Learn more in the Syniverse article [How to setup a Webhook for Receiving Messages and Notifications](https://sdcsupport.syniverse.com/hc/en-us/articles/360001528033-How-to-setup-a-Webhook-for-Receiving-Messages-and-Notifications).

   |   |                                                                                                                                                                                                                                                                        |
   | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | These Syniverse configurations are required in order that Ping Identity's dashboards and reports will reflect complete and accurate data. Ping Identity won't be able to troubleshoot SMS or voice events related to Syniverse if these configurations are incomplete. |