Supported channels

Channel allows end-users to interact with the bot

By default, your Bot is unavailable to users unless you define one or more channels through which it can communicate. So, after creating a Bot, you can add delivery channels that end-users can use to access and interact with it. SentiOne Automate provides many built-in connectors to connect the most common messaging and voice channels.

Supported channels

Below is a list of all channels you can connect to via the SentiOne Automate platform:

ChannelSupportedDescriptionConfiguration
Voice ✅ YES, via external voice integratorAny external voice integrator that is able to communicate with SentiOne Automate via Gateway serviceDocumentation:
- Voice Data flow
- Gateway API
Webchat ✅ YESSentiOne provide its own webchat solution.

SentiOne Support within configuration: 5 workdays
Documentation:
- Webchat
Facebook Messenger (Meta)✅ YES
(via Channels module)
Message is being delivered to the dedicated bot handler application (channels-connector) using webhooks technology. Integration is available in Channels module.Prerequisites:
1. Fanpage with administration permissions
2. Official Facebook application that successfully went through the review process

Configuration: To Be Done

Documentation:
- Channels Connector
WhatsApp ✅ YES
(via Channels module)
You can integrate with the WhatsApp channel via the Twilio and Vonage platform. Integration is available in Channels module.

🛑 See channel limitations.
Configuration:
- via Twillio
- via Vonage

Tech Documentation:
- Channel connectors
Twitter (direct messages) ✅ YES, internal connectorMessage is being delivered to the dedicated bot handler application (twitter-bot) using webhooks technology.

Application needs manual SentiOne configuration:

- on-premise: 5 workdays
- cloud: 1-2 workdays
Prerequisites:
1. Access to Twitter Enterprise API
2. Account with administration permissions
3. Prepared official Twitter application and go through review.

Documentation:
- twitter-bot component configuration
Skype for Business ✅ YES, internal connectorMessage is being delivered to the dedicated bot handler application (skype-bot).

Application needs manual SentiOne configuration:

- on-premise: 5 workdays
- cloud: 1-2 workdays
Prerequisites:
1. Credential to Skype API

Documentation:
- skype-bot component configuration
Instagram via API ❌ NO (possible to implement)
Telegram ✅ YES, internal connectorMessage is being delivered to the dedicated bot handler application using webhooks technology.

Application needs the manual SentiOne configuration.

- on-premise: 5 workdays
- cloud: 1-2 workdays
Microsoft Teams✅ YES (via Channels module)Message is being delivered to the dedicated bot handler application (ms-teams-bot) using webhooks technology. \n \nApplication needs manual SentiOne configuration: \n \n- on-premise: 5 workdays \n- cloud: 1-2 workdaysPrerequisites: 1. Registered App in Microsoft's Azure Active Directory 2. Generated RSA asymmetric keys (Public & Private) for message encryption Documentation:
- Channels Connector
Other channels -You can use our Gateway API Service to build your custom connector to other text channels.

SentiOne Support within configuration: 5 workdays
Documentation:
- Gateway API Service

What’s Next