---
schema_version: "1"
id: 679d9185b021dc19bdf18037d1c2b740c413dd7c6dcd5818c564a78c3ed0654c
title: Connect an Agent to Enhanced Chat v1
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/agent_deploy_enhanced_chat_v1.md
canonical_url: https://help.salesforce.com/s/articleView?id=ai.agent_deploy_enhanced_chat_v1.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c363485ae61605026ded940c6848567533bc449a4c698628a307c49c773e1335
description: Connect an Agentforce Service agent to Enhanced Chat v1 or an Agentforce Employee agent to your Experience Cloud site with Enhanced Web Chat v1.
products:
  - Agentforce
  - Cross Cloud
release: "264"
---
# Connect an Agent to Enhanced Chat v1

Connect an Agentforce Service agent to Enhanced Chat v1 or an Agentforce Employee agent to your Experience Cloud site with Enhanced Web Chat v1.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
        <colgroup>
          <col>
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and
              <strong>Developer</strong> Editions. <a href="https://help.salesforce.com/s/articleView?id=ai.agent_setup_explore_types.htm&amp;release=264.0.0&amp;type=5" title="Learn about agent types and default templates for specific clouds and common use cases.">Required
                add-on licenses vary by agent type.</a>
            </td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p><span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/resources-global/_corporate/images/checkmark.png" alt="Check mark"></span>This article applies to: Agentforce Service agents and Agentforce Employee
                agents</p>
              <p style="margin-bottom:0;">To learn about channel support for other agent types, see the documentation for
                that type.</p>
            </td>

          </tr>
        </tbody>
      </table>

![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/images/icon_warning.png)

Warning Ensure that the routing procedures don’t simultaneously route conversations to a service rep and an AI agent. For more information, see [_Knowledge Article_: Messaging Session Stuck in Waiting or Inactive Status When a Bot and an Agent Are Engaged](https://www.google.com/url?q=https://help.salesforce.com/s/articleView?id%3D004518025%26type%3D1%26language%3Den_US&sa=D&source=docs&ust=1741369183913264&usg=AOvVaw2NlhM_DYxhX715qEmS7vCn&language=en_US).

For detailed instructions on creating Omni-Channel flows for Enhanced Chat, see [Prepare a Salesforce Org for Enhanced Chat](https://help.salesforce.com/s/articleView?id=service.miaw_prepare_org_1.htm&type=5&language=en_US).

## Connect a Service Agent to Enhanced Chat v1

Route conversations to a service agent with Enhanced Chat v1.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
          <colgroup>
            <col style="width:50%">
            <col style="width:50%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" id="d122977e138">User Permissions Needed</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d122977e141">&nbsp;</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e138 ">To build and manage Service Agents:</td>

              <td data-label="" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e141 ">
                <p>Manage Agentforce Service Agents AND Manage AI Agents</p>
                <p>OR</p>
                <p style="margin-bottom:0;">Customize Application</p>
              </td>

            </tr>
          </tbody>
        </table>

1. [Add the Messaging connection](https://help.salesforce.com/s/articleView?id=ai.agent_connections_set_up.htm&release=264.0.0&type=5 "To get started with deploying your agent to channels, add connections to it. Each connection includes behind-the-scenes instructions that help an agent reason and respond for one or more channels. Each connection contains adaptive response formats that help your agent structure responses and deliver multimedia content, such as images, buttons, links, and videos. You can find adaptive response formats and other settings, including the Omni-Channel flows that route conversations to and from an agent, in your connection settings.") to your agent.
2. [Create an inbound Omni-Channel flow](https://help.salesforce.com/s/articleView?id=service.omnichannel_create_a_flow.htm&type=5&language=en_US) from scratch that routes messages to your agent. For the Route Work action in your inbound Omni-Channel flow, enter these field values.
    
    - Record ID: The recordID variable that you created.
    - Service Channel: Messaging
    - Route To: Select the Agentforce Service Agent type, and then select your agent's name. If your agent type and name don’t appear, activate your agent, refresh Flow Builder, and try again.
    - A messaging queue. When your inbound Omni-Channel flow can't route conversations to your agent, it sends the conversation to this queue.
3. Add your inbound flow to a messaging channel, and then activate the channel. You can connect your agent to multiple inbound channels, but an inbound channel can be connected to only one agent.
4. Open your agent in Agentforce Builder. Save and commit your agent and then select the Messaging connection. Confirm that your inbound Omni-Channel flow appears in the Inbound Routing section of the canvas. If a flow doesn’t appear, activate the flow and refresh the builder.
5. Open your agent in the legacy Agentforce Builder. On the Connections panel, confirm that your inbound Omni-Channel flow appears in the Inbound Routing section of the Messaging connection. If a flow doesn’t appear, activate the flow and refresh the builder.
6. Add your agent to a messaging interface by configuring an embedded service deployment.
    
    - [Configure an Enhanced Web Chat Deployment](https://help.salesforce.com/s/articleView?id=service.miaw_configure_web_deployment_1.htm&language=en_US&type=5)
    - [Configure an Enhanced Web Chat Deployment in an Experience Builder or Commerce Cloud Site](https://help.salesforce.com/s/articleView?id=service.miaw_deployment_experience_builder.htm&language=en_US&type=5)
    - [Configure an Enhanced In-App Chat Deployment](https://help.salesforce.com/s/articleView?id=service.miaw_deployment_mobile.htm&language=en_US&type=5)

Agents connected to a messaging channel use the Escalation subagent and an outbound Omni-Channel flow to transfer conversations. After you've set up inbound routing for your agent, [set up outbound routing](https://help.salesforce.com/s/articleView?id=ai.service_agent_escalation.htm&release=264.0.0&type=5 "When an agent encounters conversations that it can’t resolve, it uses the Escalation subagent to escalate the conversation. In the new Agentforce Builder, you can also run the Escalation subagent using the escalate utility function in Agent Script. Escalation and transferring works differently depending on the agent type and channel. You can customize the experience that customers receive when transferring isn’t possible.").

## Connect an Employee Agent to Enhanced Web Chat v1

Add an Agentforce Employee agent to your Experience Cloud site with Enhanced Web Chat v1.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
          <colgroup>
            <col style="width:50%">
            <col style="width:50%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" id="d122977e293">User Permissions Needed</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d122977e296">&nbsp;</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e293 ">To build and manage Employee agents:</td>

              <td data-label="" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e296 ">
                <p>Manage AI Agents</p>
                <p dir="ltr">OR</p>
                <p style="margin-bottom:0;" dir="ltr">Customize Application</p>
              </td>

            </tr>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e293 ">To create an Experience Cloud site:</td>

              <td data-label="" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e296 ">Create and Set Up Experiences AND View Setup and Configuration</td>

            </tr>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e293 ">To customize or publish an Experience Cloud site:</td>

              <td data-label="" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e296 ">
                <p>Create and Set Up Experiences AND View Setup and Configuration AND be a member of the
                  site</p>
                <p>OR</p>
                <p style="margin-bottom:0;">View Setup and Configuration AND be a member of the site AND have appropriate <a href="https://help.salesforce.com/s/articleView?id=experience.networks_access_control_overview.htm&amp;type=5&amp;language=en_US" target="_blank">role-based site access</a></p>
              </td>

            </tr>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e293 ">To set up Omni-Channl Flow and Messaging:</td>

              <td data-label="" class="slds-cell-wrap" style="vertical-align:top;" headers="d122977e296 ">Customize Application</td>

            </tr>
          </tbody>
        </table>

Agentforce Employee agents connected to Enhanced Web Chat on Experience Cloud sites run in the context of the logged-in user. Permissions and licenses must be assigned to each user. Unauthenticated users aren’t currently supported.

Before you begin:

- Give users access to [your Agentforce Employee agent](https://help.salesforce.com/s/articleView?id=ai.agent_manage_aea_access.htm&release=264.0.0&type=5 "Control user access to specific Agentforce Employee agents with permission sets or profiles. In Agentforce Builder, use the Agent Access page. In the legacy Agentforce Builder, use the Agent Access tab."). Following the principle of least privilege, assign each user any licenses and permissions necessary to run agent actions.
- To learn more about user access to Experience Cloud sites, see [Who Can See What in Experience Cloud Sites](https://help.salesforce.com/s/articleView?id=platform.networks_visibility.htm&type=5&language=en_US).

1. [Create an inbound Omni-Channel flow](https://help.salesforce.com/s/articleView?id=service.omnichannel_create_a_flow.htm&type=5&language=en_US) from scratch that routes messages to your agent, and then activate your flow.
    
    For the Route Work action in your inbound Omni-Channel flow, enter these field values.
    
    - Record ID: The recordID variable that you created.
    - Service Channel: Messaging
    - Route To: Select the Agentforce Employee agent type, and then select your agent's name. If your agent type and name don’t appear, activate your agent, refresh Flow Builder, and try again.
    - A messaging queue. When your inbound Omni-Channel flow can't route conversations to your agent, it sends the conversation to this queue.
2. [Create an Enhanced Chat channel.](https://help.salesforce.com/s/articleView?id=service.miaw_quick_start.htm&type=5&language=en_US)
    1. Add the domain of your Experience Cloud site to your messaging channel. You can copy and paste your domain name from the Domains Setup page.
    2. Add your inbound flow to your messaging channel, and then activate the channel. You can connect your agent to multiple inbound channels, but an inbound channel can be connected to only one agent.
    3. After you finish, [turn on credential-based user verification for your channel](https://help.salesforce.com/s/articleView?id=service.miaw_credential_user_verification_setup.htm&type=5&language=en_US). Later, you’ll add user verification to your site.
3. Open your agent in the legacy Agentforce Builder.
    1. On the Connections panel, confirm that your inbound Omni-Channel flow appears in the Inbound Routing section of the Messaging connection.
    2. If a flow doesn’t appear, activate the flow and refresh the builder.
4. Add your agent to your site.
    1. [Configure an embedded service deployment.](https://help.salesforce.com/s/articleView?id=service.miaw_deployment_experience_builder.htm&type=5&language=en_US)
    2. [Add credential-based user verification to your site.](https://help.salesforce.com/s/articleView?id=service.miaw_credential_user_verification_setup.htm&type=5&language=en_US)
    3. Review and, if necessary, [adjust your site’s security and privacy settings](https://help.salesforce.com/s/articleView?id=experience.networks_security_csp_scriptlevel.htm&type=5&language=en_US). For best performance with an embedded service deployment, we recommend setting your security level to Relaxed CSP: Permit Access to Inline Scripts and Allowed Hosts and adding your enhanced service URL to your trusted sites for scripts.
5. When you're ready, publish your site.

Agents connected to a messaging channel use the Escalation subagent and an outbound Omni-Channel flow to transfer conversations. After you've set up inbound routing for your agent, [set up outbound routing](https://help.salesforce.com/s/articleView?id=ai.service_agent_escalation.htm&release=264.0.0&type=5 "When an agent encounters conversations that it can’t resolve, it uses the Escalation subagent to escalate the conversation. In the new Agentforce Builder, you can also run the Escalation subagent using the escalate utility function in Agent Script. Escalation and transferring works differently depending on the agent type and channel. You can customize the experience that customers receive when transferring isn’t possible.").