Stand up a modern embedded conversation by creating an Embedded Service Deployment that uses Enhanced Chat or Messaging for Web, then installing its generated snippet on your site. This assumes Messaging for In-App and Web is provisioned and Omni-Channel routing exists.
- Prepare the org
Confirm Messaging for In-App and Web is enabled, you are in Lightning Experience, and an Experience Builder or Salesforce site exists to serve as the endpoint. Set up Omni-Channel and an Omni-Channel Flow to route conversations.
- Create the deployment
In Setup, open Embedded Service Deployments and click New Deployment. Choose Enhanced Chat or Messaging for Web as the conversation type. Remember the type is permanent for this deployment once you save.
- Set endpoint and routing
Select the site endpoint so the session runs under a guest user profile. Point the deployment at your routing flow or queue, then configure pre-chat fields, branding, and supported languages.
- Install the snippet
Copy the generated code snippet and your enhanced domain reference, add the host site as a trusted URL, then paste the snippet into your site template or tag manager and publish.
- Test and iterate
Open the page, start a conversation, and confirm it reaches an agent through Omni-Channel. Verify pre-chat data, styling, and any bot handoff before scaling to more pages.
A human-readable label for the deployment that appears in Setup and reporting.
The developer name auto-populated from the label, used in code and metadata references.
Enhanced Chat or Messaging for Web. The selection is locked once the deployment is saved.
An Experience Builder or Salesforce site that supplies the guest user profile for unauthenticated visitors.
- The conversation type cannot be changed after you save the deployment, so picking the retired Embedded Chat type instead of Enhanced Chat means starting over.
- No site endpoint appears in the menu if your org has no Experience Builder or Salesforce site configured. Create one first.
- Enhanced Chat requires Lightning Experience. Orgs still on Salesforce Classic must migrate to Lightning before deploying it.
- Conversations go nowhere until Omni-Channel and a routing flow are in place. Build routing before you publish the snippet.