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 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.

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 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 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 or to a bot is cloned as an empty placeholder dialog. The steps within the dialog aren’t cloned.