---
sourceDocument: Zurich Conversational Interfaces
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/conversational-interfaces

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Transferring Virtual Agent conversations to a live agent

# Transferring Virtual Agent
conversations to a live agent {#ariaid-title1}

Release version: Zurich  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Transferring Virtual Agent conversations to a live agent

This feature enables ServiceNow customers to seamlessly transfer Virtual Agent conversations to live agents within their chat support systems.
Transfers can occur automatically due to errors, be triggered by scripted conditions, or initiated manually by the user.
The transfer preserves the conversation context and routes it to the appropriate live agent interface based on the organization's configuration, enhancing customer support continuity and responsiveness.
Show full answer Show less  

## How Transfers Occur

* **Automatic Transfer on Error:** Conversations automatically transfer to a live agent if an unrecoverable error occurs during the Virtual Agent interaction.
* **Scripted Transfer:** Administrators can configure scripts in conversation topics using `vaSystem.connectToAgent()` to transfer users based on conditions such as urgency or impact. The system checks agent availability with `vaSystem.isLiveAgentAvailable()`, which varies slightly depending on whether Agent Workspace or Connect Support is used.
* **Manual Transfer:** Users can manually select the "Contact Live Agent" option or use specific commands (e.g., "Hi" or "agent" in messaging integrations) to request a live agent.
* **LLM Conversations:** Natural language requests like "I need to talk to a live agent" trigger an immediate transfer without additional responses.

## Routing and Agent Interfaces

When a conversation is transferred:

* The conversation continues in the same client interface to maintain user experience.
* Routing depends on the configured Agent Chat settings:
  * **Agent Workspace:** The conversation is assigned to a qualified available agent based on chat service channels and queue configurations. The agent receives the chat assignment in their inbox and joins the conversation upon acceptance.
  * **Connect Support:** Conversations are routed to a specified chat queue. Agents accept queue assignments to join and interact with users.
* If no agents are available, users receive a notification that live agents are unavailable, and the conversation is not transferred.

## Configuration and Important Notes

* The Glide Virtual Agent plugin activates the Glide Conversation Server plugin automatically for chat support.
* If Agent Chat is not used, it should be deactivated to prevent unnecessary transfers.
* Agent availability checks do not consider agent skill sets, only online status and queue schedules.
* Administrative controls exist for defining messages shown during transfer and managing chat queues.
* User sentiment analysis can be configured for both Virtual Agent and live agent conversations, with data stored in the Interaction Insights table.

## Practical Benefits

ServiceNow customers can expect smoother escalation paths from automated Virtual Agent interactions to live support, improving customer satisfaction and handling complex or high-priority requests effectively. The integration supports flexible transfer mechanisms suitable for different business rules and ensures agents handle conversations within their preferred interfaces.  
Manage live chat support, including the chat support interface used when a Virtual Agent conversation is transferred to
a live agent.  
Note:  
The Glide Virtual Agent plugin (com.glide.cs.chatbot) automatically activates the Glide Conversation Server plugin (com.glide.cs) for chat support.
Conversations in Virtual Agent are transferred to a live agent.

The transfer happens automatically when an unrecoverable error occurs. It can also be triggered by a script in a topic, when a user manually selects that option, or when a user asks for a live agent during a conversation.

Automatic transfer to a live agent when an error occurs

:   When a conversation encounters an error, the conversation automatically transfers to a live agent.

    Note:  
    If you don't plan to use Agent Chat, be sure to deactivate it in the Agent Chat settings. For more information, see [Setting up Agent Chat](https://www.servicenow.com/docs/1C6~K57XLxHCIHxZNiYHaA "Configure Agent Chat to enable live agents to chat with customers and manage various conversation features for agents and end users. Through Agent Chat, agents interact with end users, create incident or case records, or transfer chats to another agent or queue.").

Automatic transfer to a live agent that is triggered by a script in a topic

:   In situations where you need a support agent to handle the conversation, you can create a script in your topic that uses the vaSystem.connectToAgent() method. This method triggers a transfer to a live agent. This
    option can be useful for conversations involving negative customer sentiment, high-priority requests, or requests outside the scope of your topic process. For example:

        (function execute() {
            if (vaInputs.urgency == 1 && vaInputs.impact == 3)
                if(vaSystem.isLiveAgentAvailable()) { 
                   vaSystem.connectToAgent()
                }
            })()

    This script action control transfers the conversation to a live agent based on the incident impact and user urgency. The script uses the vaSystem.isLiveAgentAvailable() method as follows:

    * In Agent Workspace, the vaSystem.isLiveAgentAvailable() method checks the queue schedule and whether agents are online.
    * In Connect Support, the vaSystem.isLiveAgentAvailable() method only checks the queue schedule.
    {#transfer-to-live-agent__ul_tqr_4rs_nsb}  
    Note:  
    The vaSystem.isLiveAgentAvailable() method only checks whether agents are online, regardless of their skill set.

Manual transfer to a live agent using the Contact support option
:   You can choose the Contact support option and then select Contact Live Agent to transfer the conversation to a live agent.  
    Note:  
    Users running a Virtual Agent messaging integration must enter the command <kbd class="ph userinput">Hi</kbd> or <kbd class="ph userinput">agent</kbd> to access the live agent transfer option. If your environment isn't configured for live agents, the <kbd class="ph userinput">agent</kbd> command doesn't work. For more information, see [Integrating Virtual Agent with messaging apps](https://www.servicenow.com/docs/JtKNmk8nrv1u8Aj5pJ_Hvw "Enable users to run Virtual Agent bot conversations in supported third-party messaging apps. Use the Conversational Integration apps for Slack, Microsoft Teams, and Workplace that are available from the ServiceNow Store to configure these messaging apps on your ServiceNow instance.").
    Figure 1. Contact support options in Virtual Agent

Transfer to a live agent in LLM conversations

:   In a Virtual Agent conversation, you can enter a statement such as <kbd class="ph userinput">I need to talk to a live agent</kbd> or <kbd class="ph userinput">transfer me to a live agent</kbd>. By default,
    assistants are fully agentic, so the Live Agent topic is invoked directly, without a synthesized response, and the conversation is transferred to an available live agent.

## How Virtual Agent conversation transfers work {#transfer-to-live-agent__section_stq_wtm_f2b}

For a user engaged in a Virtual Agent conversation, the conversation continues with the live agent in the same interface. When a transfer is triggered, either automatically or by a user manually, the conversation is automatically
routed to the appropriate chat support interface, based on your [Agent Chat settings](https://www.servicenow.com/docs/1C6~K57XLxHCIHxZNiYHaA "Configure Agent Chat to enable live agents to chat with customers and manage various conversation features for agents and end users. Through Agent Chat, agents interact with end users, create incident or case records, or transfer chats to another agent or queue."). In Agent Chat settings, admins also define the general messages that users see during live agent transfers.

If you're using Agent Workspace, the conversation is automatically routed and assigned to an available live agent. If you're using Connect Support, the conversation is routed to the chat support queue that you specify.  
Note:  
At least one live agent must be available when transferring from Virtual Agent; otherwise, the end user is presented with a no agents available message and their conversation isn't transferred.

Transfer to a live agent in Agent Workspace
:   If you're using Agent Workspace, the Virtual Agent conversation is automatically transferred to a qualified available agent, based on the Chat service channel configuration and the queues that the agent supports, as defined in Advanced Work Assignment.

    For the user, the conversation with the agent continues in the Virtual Agent (client) interface. In Agent Workspace, the chat assignment appears in the agent's inbox. When an agent accepts the assignment, the agent joins the conversation and interacts with the user.

Transfer to a live agent in Connect Support

:   If you're using Connect Support, the Virtual Agent conversation is routed to the appropriate chat support queue. For the user, the conversation with the agent continues in the Virtual Agent client interface. In Connect Support, the agent accepts the queue with the transferred user to join the conversation and interact with the user.

    In earlier releases, admins used the Chat Setup form to assign the default chat queues for Customer Service Management, HR Service Delivery, and IT Service Management or a global queue to which Virtual Agent conversations were automatically routed if default queues weren't assigned. These queues, which admins defined in Connect Support, are stored in the Chat Queues \[chat_queue\] table. If you're using Connect Support as the fulfiller interface and must change chat settings, see [Setting up Agent Chat](https://www.servicenow.com/docs/1C6~K57XLxHCIHxZNiYHaA "Configure Agent Chat to enable live agents to chat with customers and manage various conversation features for agents and end users. Through Agent Chat, agents interact with end users, create incident or case records, or transfer chats to another agent or queue.") for details.

## User sentiment {#transfer-to-live-agent__section_ufv_ctd_dxb}

When configured, user sentiment analysis is performed on Virtual Agent and live agent conversations. The user sentiment is stored in the Interaction Insights \[sys_cs_interaction_insight\] table. For details, see [Interaction Insights table](https://www.servicenow.com/docs/adNGLQTVzaKvnLnPKeCcrA "User sentiment analysis prepares agents for the tone of incoming conversations. Business rules can be created based on this value and agents can take appropriate actions on the chat, whether it comes from Virtual Agent, another live agent, or from a queue.").

