PingOne

Configuring a Twilio account for PingOne

Use the information in this section to configure PingOne to use your Twilio account. To set up a Twilio Messaging Service account, refer to Creating a Twilio Messaging Services notification sender for PingOne.

Before you begin

Ensure that you have:

  • Your Twilio account string identifier (SID) and Auth Token from the Twilio dashboard.

  • One or more Twilio phone numbers that support SMS and Voice.

Steps

  1. Go to Settings > Senders.

  2. Click +, enter the following options, and then click Next:

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

    2. In the Provider Type list, select Twilio.

    3. In the Twilio Account Type list, select Twilio Services.

  3. Click Next.

  4. In the Provider Configuration window, enter the following information to configure your Twilio account to work with PingOne:

    • Provider Name: Enter a meaningful name for the Twilio account.

    • Account SID: Enter the Twilio account SID.

    • Auth Token: Enter the Twilio account’s Auth Token.

    You can’t change the Auth Token after you save this configuration. To use a new Auth Token, create a new Twilio configuration with the updated token, then delete the original configuration.

  5. Click Verify. This validates the account to PingOne and populates the Organization Numbers list from your Twilio account.

    • If the Auth Token is incorrect, an error message is displayed.

    • If there are no organization phone numbers in the Twilio account, it won’t be validated to PingOne.

    After the account is successfully verified, Organization Numbers displays.

  6. Select one or more phone numbers available to this Twilio account.

    1. For Toll-free and Short code numbers, you can configure supported Countries for notification recipients:

      • Click in the Countries field. The Configure countries modal opens.

      • Click in the Select countries field to display the list of countries. Select a country from the list.

        • Toll-free: You can add multiple countries in the Select countries list. If no country is specified, the specified toll-free number can only be used to dispatch notifications to United States recipient numbers.

        • Short code: You can select only one country in the Select countries list. If no country is specified, the specified short code can only be used to dispatch notifications to United States recipient numbers.

    2. Click the Show only selected or Show all toggle to show only the marked phone numbers and hide the numbers that aren’t selected, or to show selected and unselected numbers.

    3. Click Select all or Unselect all to select or deselect all the organization numbers for this account.

    • If you intend to use both SMS and voice, all your selected numbers must support both SMS and voice.

    • Twilio allows the use of sender IDs (in place of telephone numbers) for commercial use or to comply with regulations requiring SMSs to be sent as transactional and not promotional.

    • Sender IDs defined in Twilio aren’t displayed. PingOne uses the actual phone numbers.

    • Sender IDs are displayed according to the Sender IDs sent in the API requests.

  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. Learn more in Notification Policies.

Fallback

If PingOne receives an error during the message dispatch process that the used number is invalid, it retries using the fallback option defined in the Notification policy.

  • If there is no way of originating the SMS or voice event with the tenant’s own account, and you defined a fallback to Syniverse, the event is originated from the fallback account.

  • The following errors will cause fallback:

    • All API errors (but not SMS delivery errors)

    • No organization number was found on the Twilio account

  • If a transaction was charged to a specific account, it doesn’t imply that subsequent transactions will be charged to the same account. The account charged for each transaction is determined on an individual basis. Preference is always given to the custom account.