Chat configuration made in ACE Admin

Major parts of chat handling are configured via ACE Admin, in the same way as for other media in ACE. Examples of general configurations are:

Access rights. See Basics about access roles.
Queues and waiting lists as well as Template queues and waiting lists. See Where to configure queues and waiting lists.
Custom work levels.
Routing, Routing search order and Escalation points. See The Routing of contacts window.
Contact data, per contact type and Contact data, exception names.
Thresholds for service levels. See The Thresholds for Service levels term.
System parameters for chat.
Different display options for ACE Agent such as e.g. Configure Contact data for ACE Agent and Current contacts in ACE Agent and Waiting lists in ACE Agent.
Client setting to automatically accept chat in ACE Agent. See ACE Agent default settings.

The chat function also have some quite unique configurations made via ACE Admin. Some examples:

For automatic distribution of parallel chats you set the agent’s chat capacity as described in Before you start configuring chat.
The different messages the customer will see in ACE Chat Client described in customised chat message texts and Basics about auto generated texts in chats.

The Chat menu choice

Chat unique configurations for ACE Chat Engine and chat entrances are made under the Media | Chat menu choice.

The Chat engines window is where you activate a chat entrance and its association to a chat engine. Also see Deployment of changes for chat.

The Chat entrances window is where settings per chat entrance are made, such as e.g.

entrance name,
display methods for agent and customer name respectively,
automatically generated phrases and messages.

Access rights

To be allowed to configure chat entrances in the specific chat windows in ACE Admin, you require the Own chat entrances access right.
To make configurations in ACE Chat Engine via ACE Admin you require the Own Chat Engine access right.

To see history for chats, via Interaction View in ACE Agent, you require one of the following access functions:

View Interaction View, all interactions.
View Interaction View, allowed task types.

If you have limited who will be able to see and handle content in historic chats, by connecting task types to subareas, you should also make sure that concerned users belong to the correct subarea, i.e. not access areas.