--- sourceDocument: Australia Conversational Interfaces sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/conversational-interfaces Release : - australia ft:locale : - de-DE ft:publication_title : - Australia Conversational Interfaces ft:clusterId : - convint bundleId : - convint workflow : - Platform --- # Move from Connect Support to Advanced Work Assignment and Agent Chat # Move from Connect Support to Advanced Work Assignment and Agent Chat {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Move from ServiceNow® Connect Support to Agent Chat (live chat), which is the messaging system that agents use in Agent Workspace to interact with customers. Moving from Connect Support also involves using Advanced Work Assignment (AWA) to create the chat queues for routing chat work items to agents. ## Vorbereitungen Role required: admin Wichtig: As of Utah, Connect Support is deprecated. For similar capabilities, please move to Advanced Work Assignment and Agent Chat. ## Warum und wann dieser Vorgang ausgeführt wird Moving to modern applications such as Advanced Work Assignment and Agent Chat offers features and benefits that are not available in Connect Support. These new capabilities include: * [Automatic assignment of chats and work items to agents](https://servicenow-prod.fluidtopics.net/DkHkHugoYcAqj3OCKnM9sQ "After routing work items to the appropriate queues and corresponding agent groups, Advanced Work Assignment (AWA) pushes work to the most qualified agent using the assignment criteria that you specify. Assignment criteria revolve around the type of assignment rule (most capacity or last assigned) and whether skills are defined.") based on criteria that you define, such as agent availability, capacity, skills, [Agent Affinity](https://servicenow-prod.fluidtopics.net/lT3wetOYp60oDWTEbe9_YA "Agent Affinity is an Advanced Work Assignment feature that lets you assign work items by an agent's work history, related task, or account team affinity."), and variable [work item sizing](https://servicenow-prod.fluidtopics.net/wzAo09SiVaIpSLr2j5Uu2Q "Create a work item size override if you want Agent Affinity to calculate an agent's workload using a work item size other than the default."). * Automatic [queue overflow handling](https://servicenow-prod.fluidtopics.net/5iG1vMDk1ix8pg~k9P660w "Specify pools of agents eligible to receive overflow work assignments for a queue. An eligible assignment pool can consist of one or more groups of agents available to work on items in the queue. This feature enables Advanced Work Assignment to find a qualified agent from a wider pool of agents.") * [Chat timeout reassignment](https://servicenow-prod.fluidtopics.net/x_ehze0Tnj6cs5vu7q~7iw "Configure whether an agent who rejected a work item is eligible to be offered the same work item.") * Native [Chat surveys](https://servicenow-prod.fluidtopics.net/Sfm9SkA2VCPdaHzfnS~tHQ "Display conversational questionnaires to your end users to gather important information from them, before and after they chat with a live or virtual agent.") * Supervisor features, such as [Agent Whisper](https://servicenow-prod.fluidtopics.net/HdEJMFu42gq1O6lMpZZeGg "Agent Whisper lets agents and chat managers have a conversation without the requester knowing."), that enable managers to join ongoing public customer chats with agents or send private messages to agents. * Agent features, such as workspace [inbox controls](https://servicenow-prod.fluidtopics.net/s70YIB9T4rEDByJm51~dfg "Control certain elements of the agent experience in Agent Workspace. Define the agent presence (availability) states and the work item rejection reasons used by agents to decline work assignments in their Agent Workspace inbox.") for viewing, accepting, or rejecting incoming chats. {#migrate-from-connect-support__ul_y2l_djn_3mb} If you are currently using Connect Support APIs, see [AWA Routing API](https://www.servicenow.com/docs/access?context=queue-api&version=australia&pubname=australia-api-reference&ft:locale=en-US) for information on AWA APIs. ## Prozedur 1. Navigate to AllAdvanced Work AssignmentHome. 2. Activate the Advanced Work Assignment and Agent Chat plugins if they are not currently active. 3. If needed, review your existing Connect Support chat queues and determine whether you want to create a similar set of queues for the Chat service channel in AWA. Hinweis: You cannot use your Connect Support chat queues in AWA. Chat queues for Connect Support are stored in the Chat Queue \[chat_queue\] table. Chat queues for AWA are stored in the AWA Queue \[awa_queue\] table. 4. In the AWA Home page, [configure the Chat service channel](https://servicenow-prod.fluidtopics.net/o3PQRBkbdRRTJ5KswCExnA "Create or configure a service channel that is used in Advanced Work Assignment (AWA)."), [create the associated chat queues](https://servicenow-prod.fluidtopics.net/wxipBugudpdsaP6kwtSIYg "Define or change a queue so that you can determine which work items are routed automatically to agents through a given service channel."), and establish [agent work assignments](https://servicenow-prod.fluidtopics.net/DkHkHugoYcAqj3OCKnM9sQ "After routing work items to the appropriate queues and corresponding agent groups, Advanced Work Assignment (AWA) pushes work to the most qualified agent using the assignment criteria that you specify. Assignment criteria revolve around the type of assignment rule (most capacity or last assigned) and whether skills are defined."). 5. In [Agent Chat settings](https://servicenow-prod.fluidtopics.net/sRxU4MDV_YdfUPVCtgB9Bg "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."), access the Chat Setup form to specify Agent Workspace as the fulfiller interface for live chat and enable other live chat features. 6. Activate the [chat client on your end user Service Portal](https://servicenow-prod.fluidtopics.net/9h0Z92Pl1Di06tgm5aOHAQ "Give your users a place to interact with your bot and human agents. Choose a Service Portal chat configuration provided with your base system, such as the Service Portal Agent Chat configuration used for Agent Chat and Virtual Agent. Your end users can initiate and maintain a bot or Agent Chat conversation in any page of the portal."). {#migrate-from-connect-support__steps_fts_ffn_3mb} Troubleshooting suggestions include these common problems and solutions: Problem: While using AWA, the chat remains in routing and is not offered to an available agent. Solution: This problem may happen if AWA attempts to route the chat to a Connect Support queue. In this case, the interaction remains assigned to the Virtual Agent user and no awa_work_item record is created. A common cause of this problem is the Chat Setup entry for the chat's application still being set to Connect. Problem: When trying to route to a live agent, the requester is incorrectly told that no live agents are available. Solution: This problem may be caused by one of these situations: * Queue conditions that depend on checking interaction fields or context were created on the interaction too late for routing. * Chat service channel is not associated with the Available presence state. A common cause of this problem is deactivating and reactivating the Chat channel. {#migrate-from-connect-support__ul_pzd_dfc_wpb} Debugging suggestions include these questions to consider: Here are a few questions to ask and places to look if agents are not receiving chats: * Does an awa_work_item record exist for the interaction? If it does not, is the Assigned to field for the interaction empty or is it set to Virtual Agent? If the Assigned to field is set to Virtual Agent, it is probably trying to use Connect Support. * In the Chat setup, are the fulfillers set appropriately for each application? * In the interaction_json_blob referenced by the interaction.context_document field, is the Liveagent_application variable set to the expected value? {#migrate-from-connect-support__ul_rsh_yh5_vpb}