---
schema_version: "1"
id: 90ac18f0891ac335bcf217c436239dbc19a03d4b968da750a6d4a0c67130cba2
title: Transfer Conversations from an Enhanced Bot to an Agentforce Service Agent
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/bots_service_asa_transfer_conversation.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.bots_service_asa_transfer_conversation.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4a88b494aa3d7c0570f0cc07f63986bf4f385612f67a5f005f1e3baf95f8dcdb
description: Transfer conversations from an enhanced bot to an AI agent with an Omni-Channel flow. You can save time and resources by routing customers to the point of contact that fits their use case best—whether that’s a simple self-service bot, AI agent, or service rep. For example, an Einstein bot can greet customers, resolve common inquiries, verify customer information, and filter spam messages. When a customer’s intent is complex, sensitive, or requires more personalization, the bot can transfer the conversation to an Agentforce Service agent.
products:
  - Service Cloud
  - Service Intelligence
release: "264"
---
# Transfer Conversations from an Enhanced Bot to an Agentforce Service Agent

Transfer conversations from an enhanced bot to an AI agent with an Omni-Channel flow. You can save time and resources by routing customers to the point of contact that fits their use case best—whether that’s a simple self-service bot, AI agent, or service rep. For example, an Einstein bot can greet customers, resolve common inquiries, verify customer information, and filter spam messages. When a customer’s intent is complex, sensitive, or requires more personalization, the bot can transfer the conversation to an Agentforce Service agent.

### 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 with Foundations or Agentforce 1 Editions.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">To use enhanced Messaging channels with AI agents, <a href="https://help.salesforce.com/s/articleView?id=service.messaging_editions.htm&amp;language=en_US" target="_blank">see required editions</a>.</td></tr></tbody></table>

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

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d98963e84 ">
              <p>Customize Application</p>
              <p>OR</p>
              <p>Modify Metadata</p>
              <p>OR</p>
              <p style="margin-bottom:0;">Manage Bots</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d98963e84 ">To build and manage Agentforce Service agents:</td>

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

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

1. Create an Omni-Channel flow that transfers a messaging session to an AI agent.
    
    1. [Create an Omni-Channel flow from scratch](https://help.salesforce.com/s/articleView?id=service.omnichannel_create_a_flow.htm&type=5&language=en_US).
    2. Add a Route Work action immediately before the end of the flow. Give the action a descriptive label, such as Transfer to AI Agent.
    3. Under Set Input Values, complete the required fields. For Record ID, select **New Resource** and then create a variable called RecordId with the data type Text that’s available for input. For Service Channel, select **Messaging**. For Route To, select **Agentforce Service Agent** and then your agent’s name.
        
        If Agentforce Service Agent or the agent’s name don’t appear in the Route To options, activate your agent, refresh Flow Builder, and try again.
    4. Save and activate the flow.
    
    All active Omni-Channel flows that route conversations to your agent with the Route Work flow action appear in the Inbound Omni-Channel Flows section of the agent’s Details page.
2. Create a bot dialog that transfers the messaging session with the Omni-Channel flow that you created.
    1. Open your bot in Bot Builder. If your bot is active, deactivate it.
    2. From the menu, select **Dialog**.
    3. [Add a dialog](https://help.salesforce.com/s/articleView?id=service.bots_service_new_dialog.htm&type=5&language=en_US) and give it a descriptive label, such as Transfer to AI Agent.
    4. From the Dialog Component Library, drag the Set Routing Type action onto the canvas. In the Step Properties panel, complete the required fields. For Route Type, select **Omni-Channe**. For Route Source, select the Omni-Channel flow that you created. For Destination Variable, select **New Id Variable** and then create an ID variable with a descriptive name, such as AI Agent.
        
        If your Omni-Channel flow doesn’t appear in the Route Source options, activate your flow, refresh Bot Builder, and try again.
    5. Click **Add Rule Action**. For the Rule Action field, select **Transfer**. For Destination Variable, select the ID variable that you created.
    6. Save the dialog and activate your bot.