Smarter, faster solutions at your fingertips – Live Agent Transfer connects you to a Live Agent in seconds!

Overview

The transfer of the bot conversation from Digital Agent and an End User to a Live Agent (Analyst) is known as a "Live Agent Transfer" (LAT).

LAT basically provides an option to the end user to invoke Live Agents during the conversation with Digital Agent. This enables the end user to escalate or provide immediate attention to a logged service request (SR) or an incident (INC) by the assigned analyst.

LAT acts as a bridge that fills the gap between the end user and the analyst. It builds an immediate connectivity between the two.

When a Digital Agent cannot accurately respond to an end user's queries or when the end user requests that the conversation be transferred to an analyst, the Digital Agent may transfer the conversation to the analyst using the LAT.

Persona

End User

Business Benefits

The following infographic depicts the business benefits of Live Agent Transfer:

Figure: Benefits of LAT

Live Agent Transfer increases customer satisfaction since a live analyst can promptly respond to end user queries by providing the most relevant resolutions. Also, the end user can view the full history of their previous conversations.

The end user can continue to interact with Digital Agent bot, even after the Live Agent ends the conversation. If there are no further queries, the end user can end the conversation with the Digital Agent.

Configuring Live Agent Transfer in Digital Agent Dashboard

To successfully bridge the connection between the Live Agent and the end user, perform the following steps:

Login to Summit Application.
Navigate to Admin > Infrastructure > Workgroup. On the Workgroup page, select a tenant and a Workgroup name.
The Workgroup page has a new Enable Live Agent Transfer check box. Once this check box is enabled, the LAT icon is displayed on the Quick Access bar to the analysts for the selected Workgroup at the selected location.

Figure: Enable Live Agent Transfer
Select the Analyst Workgroup location. This will connect the end user from a specific location to the Live Agent who has the same Workgroup location. This process is referred to as Queue Routing.

Figure: Selecting Analyst Workgroup Location

Notes

If we select all locations, the live agent and end user will not get connected.
Select a particular location for a particular Workgroup.
If the end user does not have the location being configured, then the Digital Agent will trigger the alternative flow.
The Live Agent can access the Live Chat icon only from the Summit application. This icon is not present in MS Teams or Slack.
The same set of LAT operations is applicable for MS Teams as well. However, the LAT in MS Teams and Slack does not have the reset option.
MS Teams and Slack does not have the analyst module. The analyst module is only in the web chat of Summit application.

Skill-based Routing in Live Agent Transfer

When an end user is conversing with the Digital Agent and requests for Live Agent Transfer, by default, based on the configuration of end user location and the Workgroup location, the routing of LAT happens. However, the Digital Agent can also connect to a Live Agent based on the skills.

Whenever an end user provides an input to the Digital Agent, the Digital Agent identifies the entity in the input. Accordingly, the Digital Agent routes the conversation to a Live Agent whose skills match the identified intent.

With skill-based routing Live Agents will be able to provide tailored assistance, understand the customer's requirements better and offer specialized solutions or recommendations.

Prerequisites

Workgroup should be active.
Workgroup location is not selected as All.
Enable Live Agent option should be enabled.

Configuration

By matching the end user with Live Agents who have the relevant skills matching their problems, it enables a more personalized customer experience. The Digital Agent will extract the entity from the user utterance, identify the entity and based on the identified entity, the Digital Agent will connect an Analyst from a Workgroup whose skills match with the entity.

To enable the skill-based routing in LAT, you need to manually map a Workgroup having a specific skill set.

To add Workgroup pertaining to a specific skill, perform the following steps:

Login to SummitAI portal.
Navigate to Admin > Productivity > Skill Category.
Select Workgroup from the dropdown menu of Category Name.
Select a Sub Category Name for which you want to add the skills.
Click Submit.

After adding a Workgroup, you need to add skills to that Workgroup.

To add skills for a Category in a Workgroup, perform the following steps:

Navigate to Admin > Productivity > Skill.
Select Workgroup from the dropdown menu of Category Name.
Select a Sub Category Name for which you want to add the skills.
Manually add the skill names such as Outlook, laptop, to the sub category related to each entity.
Click Submit.

Notes

Skill-based routing in LAT is possible only before a ticket for an Incident or Service Request is created. If the end user requests for LAT after creating a ticket for Incident or Service Request, then the skill-based routing of Live Agent will not happen.
If the skill-based routing does not happen then by default, the Digital Agent will trigger the location-based routing and continue the conversation.
Entities like Outlook, Windows, printer, laptop, password, should be configured on the for skill-based routing.

Suppose the end user provides an input ‘my Outlook in my laptop is not working’.

Below is a sample screenshot:

Figure: End user provides an input to Digital Agent

The Digital Agent identifies the entity – Outlook and laptop - from the input provided by the end user. The end user wants to talk to a Live Agent and provides an input to the Digital Agent to transfer the conversation to a Live Agent.

Below is a sample screenshot:

Figure: Digital Agent confirms LAT

The Digital Agent transfers the conversation to the Workgroup whose skill matches the identified entity and to an Analyst (Live Agent) who belongs to that Workgroup.

Below is a sample screenshot:

Figure: Digital Agent transfers the conversation to Live Agent

Transferring the Digital Agent – End User Conversation to Live Agent

Digital Agent works in two different ways to transfer the conversation to the Live Agent. It either directly provides the option of LAT to the end user or works as per the request of the end user.

Transfer of the conversation between Digital Agent and End User to the Live Agent happens in either of the following ways:

Digital Agent Transfers the Conversation to Live Agent

When an end user begins a conversation with Digital Agent, the Digital Agent tries to provide a response/solution to the end user’s queries. If the end user is not satisfied with the response/solution provided by the Digital Agent for three consecutive times, then the Digital Agent asks whether the end user wants to transfer the conversation to an analyst. If the end user says ‘Yes’, then the conversation on the Digital Agent interface is retained and the conversation is transferred to an available analyst.
End User Wants to Talk to the Live Agent

If an end user wants to talk directly to the Live Agent even before conversing with the Digital Agent, the Digital Agent connects the end user with the Live Agent. As in the following use case, the end user provides an input - 'live agent' - in the Digital Agent without having any conversation with the Digital Agent. So, the Digital Agent then transfers the conversation to the Live Agent.

Figure: End user confirms Live Agent Transfer

LAT Flow for End User

The flow of Live Agent Transfer with respect to the end user works in a manner to streamline the entire process of transferring the conversation and provide faster resolutions to the end user.

The following flowchart demonstrates the flow of LAT for the end user:

Figure: Flow of LAT for end user

For the end user to have a conversation with the Live Agent, the end user must have the location configured.

LAT Flow for Live Agent

Once the Digital Agent transfers the conversation to the Live Agent, the Live Agent will need to perform certain steps to start the conversation with the end user.

To start conversation with an end user, perform the following steps:

The Live Agent logs into the Summit Application with Analyst access in order to participate in the conversations transferred from the Digital Agent to the Live Agent.
Using the Live Chat icon on the Analyst Dashboard page, the Live Agent (Analyst) can 'Accept' or 'Ignore' the conversation transfer request from the end user.

Figure: Live Agent dashboard with Live Chat icon
Once the Live Agent clicks on , a new tab will open in the browser (refer the below screenshot), where the Live Agent can accept or reject the chat transfer request, view history log of conversations, and user details.

Figure: Live Agent Hub screen
Live Agent will see all the new conversation transfer requests under the New Requests panel. Once the Live Agent clicks on the end user name under the New Requests panel, the Live Agent Hub window will display all the details related to that specific end user. The right side of Live Agent Hub window will show the options to Ignore or Accept the conversation transfer request. (Refer the below screenshot)

Figure: Ignore or Accept chat transfer request
The middle panel of the Live Agent Hub screen displays the initial conversation that happened between Digital Agent and end user. When the Live Agent accepts the Live Agent Transfer request, the following toast message is displayed stating that the Live Agent is connected with the End User.

Figure: Chat accepted

The conversation between the Live Agent and end user is displayed in the middle panel.
After the Live Agent accepts the conversation transfer request and starts the chat, the Live Agent Hub will have an End option (refer the below screenshot). The Live Agent can click End to end the chat.

Figure: Live Agent Hub - end chat option

Live Agent Hub

The Live Agent Hub acts as a unified platform for Live Agents to view and manage conversations and conversation transfer requests. This hub allows Live Agents to access user details, historical conversation logs, and relevant data in real-time, facilitating a more informed response.

Live Agents have access to the following details in the Live Agent Hub window:

New Requests: New conversation requests from the end users appear on the New Requests panel (refer to the screenshot below). Live Agents can navigate to the New Requests panel to accept or reject the conversation transfer request.
Active Requests: All the active conversations which the Live Agent has accepted and having conversation appear on the Active Requests panel. The active conversations are displayed end user-wise along with the end user name. Click on the end user name to chat with a particular end user.
History: The History panel displays the last five conversation history of a Live Agent with the name of the Live Agent, date and time of the conversation. Click on a particular history detail to view the entire conversation. Even if the end user ends the chat, the details of the conversation will appear on the History panel. (Refer the below screenshot)

Figure: Agent history
User Details: The User Details panel on the right side of the Live Agent Hub screen displays information about the end user like the company name to which the end user belongs, location and email address.
User's Record History: The User's Record History panel provides a log of the recent five tickets for the selected end user. There are two tabs in the User's Record History panel segregating Open and Closed tickets. (Refer the below screenshot)

Figure: User's record history

Once the Live Agent clicks on any ticket, it will open a new window where the details of the ticket can be found. The Incidents and Service Requests are displayed according to the Live Agent’s tenant access. For instance, if a Live Agent has IT tenant access but an Incident is generated in the HR tenant, that incident would not be visible to the Live Agent.
Action Panel: Live Agents can create an Incident or Service Request themselves through the Action Panel. (Refer the below screenshot). There are two tabs in the Action Panel – Create Incident and Create SR. Click on the respective tabs to log an Incident or SR.

Figure: Action panel
Eye Icon: The Eye icon near New Requests will enable Live Agents to quickly identify and understand which chats are being viewed by other Live Agents. (Refer the below screenshot)

Figure: Eye icon in Live Agent Hub

The Eye icon is visible to all other Live Agents (except the one who is viewing the chat) if any one Live Agent opens the chat request and is viewing it.

If there is a new chat request from any end user, then the end user avatar under the New Requests section will have an orange border. (Refer the following screenshot)

Figure: New chat request - orange border in End User avatar

If any Live Agent has opened and viewed a chat request, then the respective border of the End User avatar under New Requests will change from orange to grey. The End User avatar of the chat requests which are not viewed by any of the Live Agents will have an orange border. (Refer the following sample screenshot)

Figure: Grey border on End User avatar

When the Live Agents hover-over the icon, then the tooltip will display the following information:
1. If only one Live Agent is viewing the chat, then the tooltip will display ’Currently viewed by [Live Agent name]’ to other Live Agents. (Refer the sample screenshot)
  
  Figure: Eye Icon tooltip
2. If there are two new chat requests and one is being viewed by a Live Agent, then all other Live Agents will see the Eye icon against the respective End User avatar. (Refer the following screenshot). Other chat requests which are not being viewed by any Live Agent will not have the Eye icon.
  
  Figure: Eye icon for chats viewed by Agents
3. If more than one Live Agents are viewing the chat, then the tooltip will display 'Currently viewed by [no. of Agents] other Agents' to all other Agents who are not viewing the chat. (Refer the following screenshot)
  
  Figure: Eye icon tooltip displaying the number of Agents viewing the chat

Note

If the Live Agent logs out of the application, then the Live Agent is automatically logged out of the Live Agent hub window and the below message is displayed.

Figure: Logged out message - Live Agent Hub
If the Live Agent disconnects due to internet issues, closing the Live Agent hub window, or the entire browser, the following message is displayed to the end user:

Figure: Live Agent abandon - message

The end user will be visible in the common queue for other Live Agents to address.

Use Case

Digital Agent helps end user to connect with a Live Agent through LAT. The end users can check log an INC or SR, check the status of the INS or SR, or report any other concern with the Live Agent.

To connect with the Live Agent, the end user needs to take the following steps:

When the end user starts a conversation with the Digital Agent, the Digital Agent displays a welcome message and provides options to the end user to log an Incident or Service Request (refer the below sample screenshot). These options are configurable.

Figure: Digital Agent displaying the options to the end user
The Digital Agent provides a solution in the form of knowledge articles.

Figure: End user selects one option
Click I am Done to end the conversation with Digital Agent.
The end user, however, wants to talk to the Live Agent. The end user provides an input to talk to the Live Agent.

Figure: End user requests Live Agent Transfer
The Digital Agent confirms whether the end user wants to connect with the Live Agent. If the end user says ‘Yes’, the Digital Agent transfers the conversation to the Live Agent.

Figure: Conversation transferred to Live Agent
Once the end user starts conversation with a Live Agent, an End Chat button appears, which the end user can click on to end the chat with the Live Agent. (Refer the below screenshot)

Figure: End Chat

After the end user clicks End Chat, the following message is displayed by Digital Agent:

Figure: Reset conversation
If all the human agents are busy and cannot accept the chat transfer request, then Digital Agent displays the following message to the end users:

Figure: Human agent unavailable

End User Directly Converses with Live Agent

Digital Agent has the capability to directly connect the end user with the Live Agent without the need for the end user requesting for LAT. So, whenever the end user converses with the Digital Agent, the conversation will directly transfer to the Live Agent. There is a configuration switch that needs to be enabled for transferring the conversation by default to the Live Agent.

VIP Users

Digital Agent is engineered to identify the VIP users and deliver them a personalized experience through tailored Welcome message. Also, the Digital Agent offers the VIP users to transfer the conversation directly to a Live Agent for quick resolution of the issue.

Use Cases

The following use cases demonstrate how the Digital Agent delivers enhanced experience to a VIP user.

Welcome Message for VIP User

If the Digital Agent identifies the user as a VIP user, then it prompts a special welcome message.

Below is a sample screenshot of the welcome message that Digital Agent displays to a VIP user:

Figure: Welcome message for VIP user
Redirect the user directly to Live Agent
The Digital Agent will prompt a message to the VIP user whether the user wants to directly connect to the Live Agent before prompting to select a department, log an Incident or Service Request.
Below is a sample screenshot:

Figure: LAT for VIP user
Redirect to LAT after a ticket is created
After the Incident or Service Request ticket creation, if the Digital Agent identifies the end user as a VIP user, then the Digital Agent displays a dynamic message asking the user to connect to a Live Agent to get the issue resolved faster.
If the VIP user selects the option Yes, then the Digital Agent prompts the LAT.
A sample screenshot is shown below:

Figure: LAT for VIP user after ticket creation
If the VIP user denies transferring the conversation to the Live Agent, the Digital Agent will continue the conversation flow without transferring to the Live Agent.
Below is a sample screenshot:

Figure: VIP user denies LAT

Browser not supported