Embedded Service
Embedded Service is the Salesforce feature that puts service capabilities (chat, Knowledge search, case submission, video calls, appointment booking) into an external website through a small JavaScript snippet.
Definition
Embedded Service is the Salesforce feature that puts service capabilities (chat, Knowledge search, case submission, video calls, appointment booking) into an external website through a small JavaScript snippet. Customers on your marketing site, e-commerce store, or help center can start a chat, find a Knowledge article, file a case, or schedule a service appointment without leaving the page or logging into anything. The embedded experience is configured in Salesforce and renders on the external site via the snippet, with bidirectional data flow back to Service Cloud.
Embedded Service is part of Service Cloud and Service Cloud Voice; it requires a license and lives at Setup, then Embedded Service Deployments. Each deployment defines the configuration: which channels are available, what languages, which agents handle the requests, how the widget looks. Multiple deployments can target different sites or audiences (a B2B portal versus a consumer site), each with its own visual style and routing rules.
What Embedded Service includes and how it integrates
Channels offered through Embedded Service
Embedded Service Chat: real-time chat with a Service Cloud agent, threaded through Omni-Channel. Embedded Service Messaging: asynchronous messaging (WhatsApp-like) that persists across sessions. Embedded Service Appointment Booking: schedule a service visit through Field Service. Embedded Service Video: video chat with a remote agent. Knowledge browser: searchable help articles. Case form: structured case submission. Each channel is enabled per deployment.
The deployment configuration in Setup
Setup, then Embedded Service Deployments. Create a new deployment, configure the channels, set the visual style (colors, position, branding), and pick the audience (specific URLs, query parameter filters). Each deployment generates a snippet of JavaScript to embed in the target site''s HTML.
Authentication and the customer experience
Embedded Service can run anonymously (the customer is not logged in) or authenticated (the customer logs in through SSO). Anonymous mode is fastest to deploy: any visitor can start a chat. Authenticated mode passes customer context to the agent (account, recent purchases, support history), giving a more personalized experience but requiring SSO integration.
Routing to agents through Omni-Channel
Embedded Service chats and messages route to agents through Omni-Channel, the same routing engine that handles inbound calls and cases. The Embedded Service chat enters a queue, Omni-Channel matches it to an available agent based on skill, capacity, and priority. The agent sees the chat in their Lightning Service Console alongside any other Omni-Channel work.
Brand customization and the visual identity
Each Embedded Service deployment can be visually styled to match the host site. Colors, fonts, button shapes, opening behavior (auto-open after 30 seconds, manual click only), greeting message, and positioning (right-bottom, left-bottom, custom) are configurable. Advanced styling uses CSS overrides for organizations with strict brand guidelines.
Multi-language and locale support
Embedded Service supports multi-language deployment: greeting text, button labels, status messages, error messages, all localized per supported language. The customer''s browser language drives the experience automatically, with manual override available. Multi-language Knowledge integration ensures customers see articles in their language.
Pre-chat forms and the qualification step
Before connecting to an agent, Embedded Service can show a pre-chat form: collect the customer''s name, email, account number, issue category. This data populates the chat session''s metadata and routes to the right queue. Skipping pre-chat (anonymous direct connect) is fastest; collecting more data routes more accurately. Most production deployments find a middle ground.
How to set up an Embedded Service Chat deployment
Setting up Embedded Service Chat takes about an hour for the basic configuration: enable the feature, create a deployment, configure channels and styling, generate the snippet, embed on your site. The work continues as you tune routing and conversation flows.
- Enable Embedded Service in Setup
Setup, then Embedded Service, then Enable Embedded Service. The feature activates the deployment objects and the Lightning components for agents.
- Create an Embedded Service Deployment
Setup, then Embedded Service Deployments, then New. Pick the deployment type (Chat, Messaging, Appointments). Give it a name and assign it to a Service Cloud queue.
- Configure channels and styling
In the deployment, enable the channels you want and set the visual style. Branding colors, position on page, opening behavior. Save.
- Set up Omni-Channel routing
Create a Service Cloud queue for the deployment. Assign Service Cloud licensed agents. Set the routing rules: skill, priority, capacity. Test by sending a chat from your test site.
- Generate the embed snippet
From the deployment detail page, copy the JavaScript snippet. The snippet is a single script tag with your deployment ID and configuration.
- Embed on the target site
Paste the snippet into the HTML of every page where the chat should appear, or load it conditionally via your CMS. Most teams put it in the site''s footer or include file. Verify the widget appears in the right position with the right styling.
Real-time chat. Agent and customer connect immediately, session ends when chat closes.
Persistent thread that survives across sessions. Like WhatsApp or SMS in feel.
Schedule a service visit through Field Service from the website.
Video session with a remote agent. Used for high-touch service.
- Embedded Service requires Service Cloud and Service Cloud Voice licensing. Standard Salesforce orgs cannot use it without the upgrade.
- The JavaScript snippet must be embedded on every page where chat should appear. Single-page apps that load content dynamically need extra configuration to keep the widget alive.
- Pre-chat form fields must map to Salesforce fields for the data to flow. Missing mappings cause data loss when the chat ends.
- Style conflicts between the host site''s CSS and Embedded Service''s CSS can produce ugly results. Test the widget on your actual site, not just in preview, before launching.
Trust & references
Straight from the source - Salesforce's reference material on Embedded Service.
- Embedded Service OverviewSalesforce Help
- Embedded Service Developer GuideSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Embedded Service enable?
Q2. What kinds of components can be embedded?
Q3. What's a common embedded service pattern?
Discussion
Loading discussion…