GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
LLM and Generative AI Logs
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Composite Entities
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Channel Enablement
  5. Add the Syniverse Channel

Add the Syniverse Channel

To set up Syniverse as a channel, the developer needs to associate the bot with a Syniverse app, set up a subscription, and enable the delivery events for this app. This document explains the steps to add the Syniverse as a channel to your bot.

Create an App

To create the Syniverse app, follow the steps below:

  1. Log in to the Syniverse developer portal and navigate to the Applications section.
  2. Click Create New if you want to create your first app. If you want to access existing apps, click Your App.
  3. In the Create App screen, enter the app name, description, select account, and click Save.

Capture Auth Keys

Once you create an app, to capture Auth keys, follow the steps below:

  1. Navigate to the created app in the Applications section and open the app.
  2. Use the Auth Keys (see the following screenshot) to complete the configuration in the Kore.ai platform and send the SMS via bot.

Delivery Configurations

The next step is to configure how messages will be delivered via the Webhook URL configured on the XO Platform for Syniverse. To set up the delivery configurations, follow the steps below:

  1. Navigate to the Event Manager on the top menu bar and select Delivery Configurations.
  2.  If you want to use an existing delivery configuration to set up the bot’s webhook URL, select one of the configurations from the displayed table (see the following screenshot), else, click New Delivery Configuration.
  3. In the Create Delivery Configuration pop-up, enter the following values:
  • Provide a Delivery Configuration Name.
  • Address: Copy and paste the webhook URL value from the XO Platform’s Syniverse Channel Configuration section.
  • Set Is Active: to Yes.
  1. Click Create.

Subscriptions

To set up subscriptions, follow the steps below:

  1. Navigate to the Event Manager on the top menu bar and select Subscriptions.
  2.  If there are existing subscriptions, select one from the table to set up the event subscription (see the following screenshot), else, click New Subscription.
  3. In the New Topic Subscription pop-up, enter the following values:
  • Topic: Select SCG Message from the drop-down.
  • Event Type: Select mo_message_received from the drop-down.
  • Delivery Configuration: Select delivery configuration configured in the Delivery Configurations section.
  • Start Date: Select a date from when this subscription has to be active.
  • End Date: Select an end date. Leave it blank if you want this event subscription to work for a lifetime.
  1. Click Create.

Capture Sender ID

To ensure that messages flow between the two systems, you should obtain the Sender ID from Syniverse, and provide it on the XO Platform. To obtain the Sender ID, follow the steps below:

    1. Navigate to the Voice and Messaging Console on the top menu bar of your Syniverse Developer Portal account, and double click Sender ID from the Messaging Accounts in left Navigation Menu. Click +Purchase or Migrate Sender Address button to purchase a new Sender ID.
    2. Scroll down to Alias, and copy the value.

    1. Paste this value in the Syniverse Configurations panel of the Kore.ai platform.

  1. Select Yes for Enable Channel.
  2. Click Save.

Configuring the Request and Response

  • Internally, the XO Platform integration extracts and uses the sender_id_alias value (from Syniverse) in the API call to send the messages.
  • To identify the source channel, the system trims the sender_id_alias from the format Channel type_Channel ID (if present)_sending number, and considers Channel Type as the source.
  • To identify whether the request came through Channel Id or Sender Id, and also respond to Syniverse accordingly, the following is considered:
    • If the sender_id_alias has the format Channel type_Channel ID_sending number, then the request is from the Channel. This information is used to reply to the Channel. In this case, the sender_id_id field which contains the value of sender id is not used to respond.
    • If the sender_id_alias has the format Channel type_sending number, then the request is from the Sender Id. This information is used to reply to the Sender Id. In this case, the sender_id_id field is used to respond.

Add the Syniverse Channel

To set up Syniverse as a channel, the developer needs to associate the bot with a Syniverse app, set up a subscription, and enable the delivery events for this app. This document explains the steps to add the Syniverse as a channel to your bot.

Create an App

To create the Syniverse app, follow the steps below:

  1. Log in to the Syniverse developer portal and navigate to the Applications section.
  2. Click Create New if you want to create your first app. If you want to access existing apps, click Your App.
  3. In the Create App screen, enter the app name, description, select account, and click Save.

Capture Auth Keys

Once you create an app, to capture Auth keys, follow the steps below:

  1. Navigate to the created app in the Applications section and open the app.
  2. Use the Auth Keys (see the following screenshot) to complete the configuration in the Kore.ai platform and send the SMS via bot.

Delivery Configurations

The next step is to configure how messages will be delivered via the Webhook URL configured on the XO Platform for Syniverse. To set up the delivery configurations, follow the steps below:

  1. Navigate to the Event Manager on the top menu bar and select Delivery Configurations.
  2.  If you want to use an existing delivery configuration to set up the bot’s webhook URL, select one of the configurations from the displayed table (see the following screenshot), else, click New Delivery Configuration.
  3. In the Create Delivery Configuration pop-up, enter the following values:
  • Provide a Delivery Configuration Name.
  • Address: Copy and paste the webhook URL value from the XO Platform’s Syniverse Channel Configuration section.
  • Set Is Active: to Yes.
  1. Click Create.

Subscriptions

To set up subscriptions, follow the steps below:

  1. Navigate to the Event Manager on the top menu bar and select Subscriptions.
  2.  If there are existing subscriptions, select one from the table to set up the event subscription (see the following screenshot), else, click New Subscription.
  3. In the New Topic Subscription pop-up, enter the following values:
  • Topic: Select SCG Message from the drop-down.
  • Event Type: Select mo_message_received from the drop-down.
  • Delivery Configuration: Select delivery configuration configured in the Delivery Configurations section.
  • Start Date: Select a date from when this subscription has to be active.
  • End Date: Select an end date. Leave it blank if you want this event subscription to work for a lifetime.
  1. Click Create.

Capture Sender ID

To ensure that messages flow between the two systems, you should obtain the Sender ID from Syniverse, and provide it on the XO Platform. To obtain the Sender ID, follow the steps below:

    1. Navigate to the Voice and Messaging Console on the top menu bar of your Syniverse Developer Portal account, and double click Sender ID from the Messaging Accounts in left Navigation Menu. Click +Purchase or Migrate Sender Address button to purchase a new Sender ID.
    2. Scroll down to Alias, and copy the value.

    1. Paste this value in the Syniverse Configurations panel of the Kore.ai platform.

  1. Select Yes for Enable Channel.
  2. Click Save.

Configuring the Request and Response

  • Internally, the XO Platform integration extracts and uses the sender_id_alias value (from Syniverse) in the API call to send the messages.
  • To identify the source channel, the system trims the sender_id_alias from the format Channel type_Channel ID (if present)_sending number, and considers Channel Type as the source.
  • To identify whether the request came through Channel Id or Sender Id, and also respond to Syniverse accordingly, the following is considered:
    • If the sender_id_alias has the format Channel type_Channel ID_sending number, then the request is from the Channel. This information is used to reply to the Channel. In this case, the sender_id_id field which contains the value of sender id is not used to respond.
    • If the sender_id_alias has the format Channel type_sending number, then the request is from the Sender Id. This information is used to reply to the Sender Id. In this case, the sender_id_id field is used to respond.
Menu