Skip to content
Gallery
Graphlogic.ai documentation
Docs guide
How to create a bot
FAQ
What to prepare before creating your Agent
What is Graphlogic.ai
Releases history
How to get started with the Platform
How to create your Agent
How to use Chat Context in your Agent
How to succesfully train your Agent
How to deploy your Agent to channels
Agent usage
How to check Analytics for yur Agents
Additional information
Channel Integration
Resources & infrastructure requirements copy
Onboarding task
Share
Explore
How to deploy your Agent to channels

icon picker
Deployment of Agent to different channels

A distinction must be made between
@Connector
⁠
s,
@Project Channel
⁠
s, and
@End Channel
⁠
s:
⁠
@End Channel
⁠
is the software in which
@Conversation
⁠
takes place between the
@Bot
⁠
and the
@Bot User
⁠
(messengers, social networks, omnichannel platforms, etc.).
⁠
@Project Channel
⁠
is an
@Agent
⁠
setting, i.e. connection of the
@Agent
⁠
to the
@End Channel
⁠
configured in the
@Platform
⁠
(messenger, social networks, widgets).
A connector is a functionality of the
@Platform
⁠
and a set of rules, a driver for connecting an
@Agent
⁠
to a specific
@End Channel
⁠
.
The following
@End Channel
⁠
s exist in the
@Platform
⁠
:
End Channels
1
End Channel
Type
1
Telegram
Messaging
2
360Dialog (WhatsApp)
Messaging
3
Jivo
Omnichannel
4
Webim (External Bot API 1.0)
Omnichannel
5
Webim (External Bot API 2.0)
Omnichannel
6
Edna Chat Center
Omnichannel
7
Livetex
Omnichannel
8
Debug widget
Messaging
9
Chat2Desk
Omnichannel
10
Chat API
Omnichannel
11
VK
Messaging
12
Microsoft Teams
Messaging
13
Edna Pulse
Messaging
14
Viber
Messaging
15
VK Teams
Messaging
16
Line messenger
Messaging
17
360Dialog (cloud)
Messaging
18
Widget
Messaging
19
Bitrix24
Omnichannel
20
Voice Box API
Messaging
21
Facebook Messenger
Messaging
There are no rows in this table
⁠

Agent channel configuration

In order to deploy an
@Agent
⁠
in one or more available
@End Channel
⁠
s, you must:
Go to the desired
@Agent
⁠
, click on the gear button and click Edit. ​
image.png
⁠
⁠
The
@Agent
⁠
settings window will open, in which you need to go to the Channels tab. ​
image.png
⁠
⁠
On the Channels tab, in the line of the same name, two options are displayed:
Messaging - implies direct connection to instant messengers.
Omnichannel - implies connecting the Agent to the
@End Channel
⁠
through omnichannel platforms.
More details:
Types of Agent Channels by Destination
⁠
.
To add a new
@Project Channel
⁠
, you must select one of the Messaging or Omnichannel options and click the +Add another channel button. ​
image.png
⁠
⁠
Then you need to click on the Channel field and select the required
@End Channel
⁠
from the drop-down list. ​
image.png
⁠
⁠
Types of Agent Channels by Destination
Name
Descriptiom
1
Messaging
Type of
@Project Channel
⁠
s for communicating with an
@Bot User
⁠
in channels like Messengers
2
Omnichannel
⁠
@Project Channel
⁠
type for communication between
@Agent
⁠
s and
@Bot User
⁠
s through omnichannel platforms. In such channels,
@Agent
⁠
connects to communication with the
@Bot User
⁠
“as another operator” and can at any time disconnect and/or transfer the
@Dialog
⁠
to another (human) operator.
There are no rows in this table
⁠

Channel titles

When creating an
@Project Channel
⁠
, you can optionally set a title for it in the Title field. ​
image.png
⁠
⁠
This header will appear when you hover over the
@Project Channel
⁠
icon on the
@Agent
⁠
card. ​
image.png
⁠
⁠

Channel service messages

Channel service messages are technical messages generated by the
@End Channel
⁠
in response to any events in it.
You can activate the receipt of service messages from the
@End Channel
⁠
by toggling the toggle switch in the
@Project Channel
⁠
settings:
⁠
image.png
⁠
⁠
Information about which Service messages and in what form are transmitted from the
@End Channel
⁠
s is contained in the articles about
@End Channel
⁠
s.
End Channels
Agent channel configuration
Types of Agent Channels by Destination
Channel titles
Channel service messages
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.