--- sourceDocument: Australia Conversational Interfaces sourceDocumentLink: https://www.servicenow.com/docs/r/conversational-interfaces Release : - australia ft:locale : - en-US ft:publication_title : - Australia 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: Australia * * 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 guide outlines how to manage the transfer of conversations from Virtual Agent to a live agent, including automatic and manual transfer methods. It is crucial for ensuring effective chat support and handling customer inquiries efficiently. Show full answer Show less ## Key Features * **Automatic Transfer:** Conversations automatically transfer to a live agent when an unrecoverable error occurs. * **Scripted Transfer:** Use the `vaSystem.connectToAgent()` method in scripts to transfer conversations based on user urgency and impact, allowing for proactive handling of critical requests. * **Manual Transfer:** Users can manually select the option to contact a live agent, with specific commands required in certain integrations, such as "Hi" or "agent." * **LLM Conversations:** In LLM topics, users can prompt a transfer by stating their intent to speak with a live agent. ## Key Outcomes The transfer process is seamless, ensuring that users continue their conversation in the Virtual Agent interface. Depending on your setup: * **Agent Workspace:** Conversations are routed to an available agent based on configured queues. * **Connect Support:** Conversations are directed to the specified chat support queue for agent handling. Additionally, user sentiment analysis can be conducted on conversations, enhancing the understanding of customer interactions. Make sure at least one live agent is available to avoid situations where users receive a "no agents available" message. 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 in several ways. This transfer happens automatically when an unrecoverable error occurs, but it can also be triggered by a script in a topic, when a user manually selects that option, or when a user inputs the request during an LLM 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/SE890aioSqFB3n6_P4gOkg "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 want 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 Hi or agent to access the live agent transfer option. If your environment isn't configured for live agents, the agent command doesn't work. For more information, see [Integrating Virtual Agent with messaging apps](https://www.servicenow.com/docs/eYn0beX_CQLOgHdD3uqHuA "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 Manual transfer to a live agent in LLM conversations : In a Virtual Agent conversation using LLM topics, you can enter a statement such as I need to talk to a live agent, transfer me to a live agent, or other similar statements. The LLM then turns your chat over 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 switch to a live agent is a seamless transfer. 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/SE890aioSqFB3n6_P4gOkg "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/SE890aioSqFB3n6_P4gOkg "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/8xaqsz_0VIi7HK_vowRThA "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.").