CIM Messages are a communication interface between 3rd-party applications and Expertflow CX. Multiple message types are supported. You can:
-
send messages via Channel Connector using CIM Message REST APIs.
-
send messages through Socket.io for event-based architecture such as custom Agent Desk.
-
send messages via Bot Connector to Bot.
Based on the above mentioned points, two keywords associated with messages are defined as follows:
|
Inbound Messages |
Messages received by CCM from any 3rd party (channel connector, custom agent desk or bot connector) are called inbound messages. |
|---|---|
|
Outbound Messages |
Messages sent by CCM to any 3rd party (channel connector, custom agent desk or bot connector) are called outbound messages. |
Structure of CIM Messages
The CIM Messages#request and CIM Messages#response structure of CIM Messages is given as follows:
Request
In the Expertflow CX Object Model, a message request contain two parts - Header and Body.
-
Header
-
-
a standard format is set for all types of messages. The generic header format is described below in the Header tab.
-
-
-
fields can be added to the header as per requirement such as in case of Agent Desk and Bot Connector.
-
-
Body
-
the message body changes with respect to the message type. The standard parameters in the body are described below in the Body tab.
-
there are six basic types of messages i.e. Plain, Media (Image, Video, Audio, File, Sticker), Location, Contact, URL and Button.
-
a specific type of message such as WrapUp Message is used in Agent Desk to wrap up agent-customer conversation.
-
A unique ID is also generated to identify each message in a conversation. The payload of Messages is described below.