--- schema_version: "1" id: c2872e8baed141e2fabc1df88e37b6714f084ec46b504695a786820045fcf497 title: About Cloning a Standard Bot as an Enhanced Bot collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/bots_service_enhanced_create_clone_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=service.bots_service_enhanced_create_clone_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: c87c903d91ad9c99ec00cd8770b8447f1976a525c27a362c596a892fc6231433 description: When you clone a standard bot as an enhanced bot, the guided cloning experience reconfigures features that work differently for enhanced bots. products: - Service Cloud - Service Intelligence release: "264" --- # About Cloning a Standard Bot as an Enhanced Bot When you clone a standard bot as an enhanced bot, the guided cloning experience reconfigures features that work differently for enhanced bots. ### Required Editions
View supported editions for Einstein Bots.
View supported editions for Messaging.
## Context Variables We map the following [context variables](https://help.salesforce.com/s/articleView?id=service.bots_service_context_system_variables.htm&release=264.0.0&type=5 "Access important information during bot conversations with context and system variables. Context variables let your bot gather customer information regardless of channel. System variables store back-end information about conversations.") to their corresponding messaging objects. | Context Variable | Object | Field Label | API Name | | --- | --- | --- | --- | | Routable Id | Messaging Session | Messaging Session ID | MessagingSession.Id | | End User Id | Messaging Session | Messaging User | MessagingSession.MessagingEndUserId | | Contact Id | Messaging User | Contact | MessagingEndUser.ContactId | If you don't reference the Chat Key context variable in your dialogs, we delete it from your variables. If you reference the Chat Key variable, we generate a list of affected dialogs. Download the list, remove references to the variable from your dialogs, and then restart the cloning process. The list doesn’t include any references to the Chat Key variable in merge fields. After you clone your bot, consider reviewing the messages your bot sends your customers. ## Conversation Routing
Inbound: Send conversations to your enhanced bot Outbound: Transfer conversations from your enhanced bot

When you clone a standard bot as an enhanced bot, we create a simple inbound Omni-Channel flow for your bot. It’s saved as Route to [Bot Name] and appears in the Inbound Omni-Channel Flows section of the Bot Overview page.

To use this flow:

  • In Flow Builder, specify a fallback queue in the Route Work action. Then make any other customizations and activate the flow.
  • Add your flow to a Messaging channel. You can add your flow to an existing channel from the Inbound Omni-Channel Flows section of the Bot Overview page. Otherwise, go to the Messaging Settings page in Setup.

Otherwise, create an inbound Omni-Channel flow from scratch.

When you clone a standard bot as an enhanced bot, we create a simple outbound Omni-Channel flow for your bot. It’s saved as Route from [Bot Name] and appears in the Outbound Omni-Channel Flow setting on the Bot Overview page.

To use this flow, in Flow Builder, specify an agent, bot, queue, or skill as the transfer destination in the Route Work action. Then make any other customizations and activate the flow.

Otherwise, create an outbound Omni-Channel flow from scratch and specify it in the Outbound Omni-Channel Flow setting.
Any Omni-Channel flow that Salesforce creates doesn’t route conversations to or from your bot until you customize and activate it in Flow Builder.
## Custom Dialogs - All of your dialogs ending in the [Transfer to Agent Next Step](https://help.salesforce.com/s/articleView?id=service.bots_service_setup_dialog.htm&release=264.0.0&type=5 "After you add a dialog, set it up by adding steps (outbound messages, questions, actions, rules) and tell the bot what to do after the dialog finishes. If you’re using intents, train the bot to understand the customer intent associated with the dialog.") are cloned and routed to the default outbound Omni-Channel flow. After you clone your bot, you can specify a different outbound Omni-Channel flow on the Bot Overview page. - We revert the [Transfer to Agent system dialog](https://help.salesforce.com/s/articleView?id=service.bots_service_system_bot_dialog.htm&release=264.0.0&type=5 "Einstein Bots are built for conversation. To make setup a breeze, some of the most common dialogs are included with each new bot. These dialogs allow you to quickly transfer conversations to a service rep, or gracefully end a chat. You can customize each message to your company’s voice and tone.") to default, so any customizations aren’t cloned. - Any custom dialog that uses the Set Routing Type rule step to transfer conversations to [a queue](https://help.salesforce.com/s/articleView?id=service.bots_service_transfer_queue.htm&release=264.0.0&type=5 "You can route bot conversations to a queue of service reps by using Rule dialog steps. And you can help customers who initiate a transfer when service reps are offline with the No Available Agents dialog.") or to [a bot](https://help.salesforce.com/s/articleView?id=service.bots_service_transfer_bot.htm&release=264.0.0&type=5 "Create custom solutions in your org by adopting a multi-bot strategy. Use dialog Rule steps to transfer bot conversations to another bot.") is cloned as an empty placeholder dialog. The steps within the dialog aren’t cloned.