Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


ON THIS PAGE


Chat Channel Section shows all the interactions managed by the Agents and coming from a Chat on a Website.

The Customer and the Agent can exchange chat messages (including files, emoticons, pictures and so on) and have the following benefits:

  • the Customer can use an easy chat contact point (a snippet on a web page)

  • the Agent interaction happens inside the XCALLY Motion common environment

  • the Agent can manage several types of interactions at the same time

  • the Agent can start a Video Call session (this feature is optional and requires an activation from the Administrator) with a Customer directly from the chat

  • the interaction content is shared, easily retrieved and managed

  • all the Customers information is stored in the Contacts Manager 

If your Agent Desktop is running on MAC with OS High Sierra and using the Browser Safari, remember to enable the audio notifications in Safari in order to receive an audio alert for all incoming interactions

Whenever customers interact with the Contact Center using a chat contact point in a website, the Agents belonging to the specific chat channel queue will receive a request on the Omni Desktop interface.

They can reject it and the request is passed to another Agent in the same queue (in this case ChatQueue)

The interaction starts when one agent accepts it: all the others will be notified that the interaction has already been taken by somebody else.

The number of concurrent chat sessions that can be managed by all the Agents is according to the sessions license limit of your system.

Starting a pause during a chat session
If the Agent pauses during a chat session, this action prevents any further interaction notification to be displayed to him but the chat in progress will not be automatically stopped: the live chat messages will still arrive to him, unless the interaction is intentionally closed (in this way, any new message belonging to the same session will be routed to the first free agent and the chat session is reopened)

Let's see how a typical chat session looks like: 

Customer's side

Agent's side

the customer starts a chat session on a web page, writing a request in a snippet:

after accepting the notify of the incoming chat request, a new chat tab is opened:

  • No labels