Graphlogic.ai documentation

How to deploy your Agent to channels

Deployment of Agent to different channels

A distinction must be made between

@Connector⁠

@Project Channel⁠

s, and

@End Channel⁠

⁠

@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

End Channels

End Channel

Type

Messaging

360Dialog (WhatsApp)

Messaging

Jivo

Omnichannel

Webim (External Bot API 1.0)

Omnichannel

Webim (External Bot API 2.0)

Omnichannel

Edna Chat Center

Omnichannel

Livetex

Omnichannel

Debug widget

Messaging

Chat2Desk

Omnichannel

Chat API

Omnichannel

Messaging

Microsoft Teams

Messaging

Edna Pulse

Messaging

Viber

Messaging

VK Teams

Messaging

Line messenger

Messaging

360Dialog (cloud)

Messaging

Widget

Messaging

Bitrix24

Omnichannel

Voice Box API

Messaging

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.

⁠

The

@Agent⁠

settings window will open, in which you need to go to the Channels tab.

⁠

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.

⁠

Then you need to click on the Channel field and select the required

@End Channel⁠

from the drop-down list.

⁠

Types of Agent Channels by Destination

Types of Agent Channels by Destination

Name

Descriptiom

Messaging

Type of

@Project Channel

⁠

s for communicating with an

@Bot User

⁠

in channels like Messengers

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.

⁠

This header will appear when you hover over the

@Project Channel⁠

icon on the

@Agent⁠

card.

⁠

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:

⁠

Information about which Service messages and in what form are transmitted from the

@End Channel⁠

s is contained in the articles about

@End Channel⁠

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.