Manage Agent Chat Console Settings
Agent Chat Console is an interface for Support Agents to handle multiple inbound requests from End-users. As Administrators, you can manage and configure the Agent Chat Console settings like messages, timeout intervals for agents and end-users, User Information to be displayed on the Agent chat console.
To manage the Agent Chat Console settings, Navigate to the Tenant Settings page and click on the Agent Chat Console tab as shown below.
Agent Chat console setting tab has three sections i.e Messages, Timeouts, and Additional User Information
Messages
In this section, you can customize information messages to be shown to the users for various scenarios during the end-user and Support Agent chat process. Default messages will be provided for each scenario. To edit the default messages, follow the steps provided below:
Click on Edit Settings.
Scroll to the Messages section or click Messages on the right--hand menu.
Edit the messages as required. It is suggested to configure easy and simple messages to help the end-user understand the status of the current agent chat conversation.
Click on Save button to save the changes.
Timeouts
The following Timeout parameters and corresponding messages are required to configure to give a better end-user experience and messages related to timeouts are configured here to give a better user experience to the end-users.
Waiting Queue Critical Time Out
Define the amount of time that an end-user could wait until a Support Agent accepts the incoming chat request. When the time limit is reached, the request expires and the user is automatically returned to the Bot Context.
Time out | Default value | Minimum Limit | Maximum Limit |
---|---|---|---|
Waiting Queue Critical Timeout | 2 | 2 | 15 |
For example, the Waiting Queue Critical Timeout is set to 10 min. In this case, the conversation will be in the Request queue for 10 mins. If the conversation is still not accepted by any available Support agent, then the conversation will be timed out and the end-user will be returned to the Bot for any further conversations.
Waiting Queue Warning Time Out
Define the time when the Support Agent is warned that the user conversation is about to reach the Critical time out in the Agent Chat Console Waiting queue. The Conversation will be highlighted in RED, warning the Support Agent of the approaching Waiting Queue Critical Timeout.
If the conversation is still not accepted by any available Support Agent, then the user returns to the Luma Agent context, and the conversation is removed from the queue.
Time out | Default value | Minimum Limit | Maximum Limit |
---|---|---|---|
Waiting Queue Warning Timeout | 1 | 1 | 10 |
For example, the Waiting Queue Warning Timeout is set to 2 min and Waiting Queue Critical Timeout is set to 10 min. In this case, the Support Agent will be warned and the conversation will be highlighted in red after 8 mins (10 min-2 min) of user requests being in the waiting queue.
User Idle Time Out
Define the idle time limit for which an End-User can be idle (i.e. does not respond) in an Ongoing conversation after the Support Agent accepts the chat. Once the time limit is reached, the conversation times out, and the end-user is automatically returned to the bot context. The Support Agent can now see the conversation in the Closed queue.
You can also configure the message to be sent to the end-users if the conversation expires due to no response from their end.
Time out | Default value | Minimum Limit | Maximum Limit |
---|---|---|---|
User Idle Time Out | 5 | 1 | 60 |
For example, if you set User Idle Timeout to 5 minutes, the maximum time for which the User can remain idle in the conversation is 5 minutes. In case the user still does not respond, then the conversation expires and the user returns to Luma Bot.
Agent Idle Time Out
Define the time limit for which an Agent can be idle (i.e. does not respond) after accepting the chat or in an Ongoing conversation with an End-User. Once the time limit is reached, the conversation expires and the end-user is automatically returned to Bot. The conversation is closed and moved to the Closed queue where the Support Agent can view the details of the conversation.
You can also configure a message to be sent to the user if the Agent has not responded before Agent idle timeout.
Time out | Default value | Minimum Limit | Maximum Limit |
---|---|---|---|
Agent Idle Time Out | 10 | 1 | 60 |
For example, if you set 12 minutes, the maximum time the Agent can keep the user waiting is 12 minutes. In case the Agent still does not respond beyond this time, the user returns to Luma Bot.
To update timeouts, follow the below steps:
Click Edit settings.
Scroll to the Timeouts section or click on ‘Timeouts’ in the right-hand menu.
Update timeouts as required.
Click Save to save changes.
It is recommended that the Agent Idle timeout should be higher than the User idle timeout. The Support Agents may take longer to respond to the conversation as they may be handling one or more user requests at a time.
The User and Agent Idle timeout can be set to a maximum of 60 mins.
As soon as the Support Agent accepts the user conversation, the Support Agent timer starts and the user waits for the Agent's response. Once the Support Agent responds, the Agent Idle timeout is reset and User Idle timer starts. This ensures the conversation timeouts only when the appropriate timeout is reached.
Additional User Information
In this section, configure the additional user information to be displayed in the Agent Chat Console.
Fields in Waiting and Ongoing Queues: Fields configured here are displayed under User conversation in Waiting and Ongoing Queues. This helps in distinguishing and identifying users so that Support Agent can decide whom to give priority. User profile, Channel, and custom user fields can be displayed in this section. To add fields, do the following:
Select Context. This represents the category of information to be displayed like ‘User’ for user information, ‘Channel’ for channel details.
Select Field Name. This is the actual information to be displayed. For Example, for Context ‘User’, select Username, title, email id, etc.
Click Set to add the field to the list.
To remove an existing field from the list, click on the 'X' button next to the field name.
Click Save to save the changes.
A maximum of 3 fields can be added.
These 3 fields will be displayed under the User Name who initiated the Agent Transfer request in the Waiting and Ongoing queues.
Fields in Chat Window: Fields configured here are displayed in the Conversation details section on Agent chat Console. This gives more detailed information about the user, the Support Agent is interacting with. To add fields, do the following:
Select Context. This represents the category of information to be displayed like ‘User’ for user information, ‘Channel’ for channel details.
Select Field Name. This is the actual information to be displayed. For Example, for Context ‘User’, select Username, title, email id, etc.
Click Set to add the field to the list.
To remove an existing field from the list, click on the 'X' button next to the field name.
Click Save to save the changes.
Â
© 2019 Serviceaide 1-650-206-8988 http://www.serviceaide.com info@serviceaide.com