Configure Salesforce Embedded Service Chat (Messaging for Web) for a website via Setup
domain: help.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Setup, enter "Embedded Service" in Quick Find and open the Embedded Service configuration page (requires Customize Application AND Modify Metadata permissions)
Click New Deployment and choose "Embedded Chat" as the conversation type; this choice is permanent for that deployment once saved
Enter an Embedded Service Deployment Name (the API Name auto-populates) and select a Site Endpoint from the dropdown — an Experience Builder site or Salesforce site is required so guest users can be associated with a guest user profile; create a site first if none is listed
Save the deployment, then configure chat settings (routing, pre-chat form, offline form, post-chat survey) and general branding via the linked setup pages under the deployment
Add the generated Embedded Service JavaScript code snippet to the target website's HTML, and add the website's domain to the CORS allowlist so the browser can call Salesforce
Test the deployment in the embedded chat test window before publishing to production
Known gotchas
This is a declarative, point-and-click setup done entirely in Setup UI plus an Experience Builder/Salesforce site — there is no public REST/SOAP API for creating or configuring an Embedded Service Chat deployment itself; don't invent API calls for it
Legacy Chat (the original Live Agent-based product, sometimes still called Snap-ins in older docs) is being retired on February 14, 2026 in favor of enhanced Chat (formerly Messaging for In-App and Web) — new implementations should be built on enhanced Chat, not the legacy product. Note routing for messaging channels here can use basic queue-based routing; Omni-Channel Flow is an optional advanced-routing upgrade, not a requirement.
Once a conversation type (Embedded Chat) is selected for a deployment and saved, it cannot be changed later — switching approaches requires creating a new deployment
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?