{"id":1848,"date":"2025-11-19T23:08:47","date_gmt":"2025-11-20T06:08:47","guid":{"rendered":"https:\/\/salesforcechronicles.com\/?p=1848"},"modified":"2025-11-23T21:28:29","modified_gmt":"2025-11-24T04:28:29","slug":"embedded-services-in-salesforce","status":"publish","type":"post","link":"https:\/\/salesforcechronicles.com\/?p=1848","title":{"rendered":"Salesforce Embedded Service: Comparing v1 and v2 Deployments"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

Embedded Service in Salesforce has evolved from its early Snap ins Chat framework into two distinct deployment models \u00a0Version 1 and Version 2. As organizations begin adopting\u00a0Agentforce\u00a0to power AI driven customer interactions, understanding these deployment models becomes essential. While both versions deliver chat and messaging capabilities within a website or portal, they follow different architectural patterns and interaction models.<\/p>\n\n\n\n

What is Embedded Service?<\/h2>\n\n\n\n

Embedded Service (previously known as Snap-ins Chat) allows you to embed live chat or messaging capabilities directly into your website or mobile application. It acts as a real-time communication bridge between your customers and Salesforce Service Cloud. Customers can connect with live agents, chatbots, or even Flows all without leaving your website or portal.

Think of it as the ‘Chat with us’ bubble you see on modern websites. It looks simple, but it\u2019s powered by Omni Channel routing, automation, and Salesforce data behind the scenes.<\/p>\n\n\n\n

Version 1 \u2014 Enhanced Chat<\/h2>\n\n\n\n

Version 1 is the original Embedded Service Deployment model. It provides a synchronous chat experience like a phone call where both the customer and the agent interact in real time. When the chat window is closed, the session ends immediately.

This version is configured in Setup under ‘Embedded Service Deployments’ and uses the embedded_svc.js script snippet. It supports custom Lightning components for pre chat and post chat logic, routes chats via Omni Channel, and allows CSS based branding.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n
\n
<\/div>\n<\/div>\n\n\n\n

Example: A retail website wants to assist customers instantly about shipping or refunds. A visitor clicks on ‘Chat Now’, connects with an agent, and closes the chat once their query is resolved. It\u2019s a straightforward, real time exchange that ends when the session closes.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Version 1 works well for businesses that need quick responses and control over their UI. It\u2019s ideal when you need a custom pre-chat experience, but it does not support persistent chat or multi device continuity.<\/p>\n\n\n\n

Version 2 \u2014 Enhanced Chat<\/h2>\n\n\n\n

Salesforce introduced Version 2 (Enhanced Chat) to deliver a modern, persistent messaging experience similar to modern messaging applications.

This version is configured under ‘Enhanced Chat Deployments’ and uses the enhanced chat.js script. It\u2019s built on a managed runtime, integrates deeply with Flow Builder, Einstein Bots, and Omni Channel, and simplifies theming and setup. However, it does not currently support custom Lightning components in the chat UI.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Example: A banking customer starts chatting about a loan on the website and later continues in the mobile app without losing context. This flexibility makes Version 2 ideal for businesses offering multi device support and asynchronous messaging.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Key Differences Between Version 1 and Version 2<\/h2>\n\n\n\n
Feature<\/strong><\/td>Version 1 (Enhanced Chat)<\/strong><\/td>Version 2 (Enhanced Chat)<\/strong><\/td><\/tr>
Interaction Type<\/td>Real time, synchronous chat<\/td>Persistent, asynchronous messaging<\/td><\/tr>
Framework<\/td>Aura (supports custom components)<\/td>Managed runtime (no custom components)<\/td><\/tr>
Deployment Script<\/td>embedded_svc.js<\/td>enhanced-chat.js<\/td><\/tr>
Customization<\/td>Custom pre-chat\/post-chat components<\/td>doesn’t support custom components<\/td><\/tr>
Branding<\/td>CSS and component overrides<\/td>Setup-based theming<\/td><\/tr>
Session Continuity<\/td>Ends when closed<\/td>Chat persists<\/td><\/tr>
Mobile & App Support<\/td>Limited<\/td>Fully supported<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

When to Choose Each Version<\/h2>\n\n\n\n

From a business standpoint, Version 1 feels like a traditional phone conversation immediate, live, and ends when you hang up. Version 2 is more like a text chat that you can revisit at any time.
<\/p>\n\n\n\n

Choose Version 1 if:<\/p>\n\n\n\n

\u2022<\/span> You want a quick, real-time website chat.
\u2022 You already have custom pre-chat components.
\u2022 You\u2019re maintaining a legacy chat implementation.<\/p>\n\n\n\n

Choose Version 2 if:<\/p>\n\n\n\n

\u2022 You want persistent, asynchronous conversations.
\u2022 You rely on Flows or Einstein Bots for automation.
\u2022 You need cross device chat continuity.<\/p>\n\n\n\n

Technical Takeaways<\/h2>\n\n\n\n
Need<\/strong><\/td>Recommended Version<\/strong><\/td><\/tr>
Support custom Lightning Components<\/td>Version 1<\/td><\/tr>
Persistent, asynchronous messaging<\/td>Version 2<\/td><\/tr>
Flow or Bot Integration<\/td>Version 2<\/td><\/tr>
Quick, real-time setup<\/td>Version 1<\/td><\/tr>
Long-term roadmap support<\/td>Version 2<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

Salesforce now offers two distinct approaches for embedding chat. Version 1 is suitable when custom Lightning components and UI control are required. Version 2 provides a modern, persistent messaging framework aligned with Salesforce\u2019s current roadmap. For new implementations, Version 2 is the recommended choice. Existing Version 1 deployments should plan a gradual transition.
<\/p>\n\n\n\n

References<\/h2>\n\n\n\n

\u2022 Salesforce Help: Enhanced Chat Feature Comparison<\/a>
\u2022 Salesforce Help: Snap-ins Chat (Embedded Service)<\/a> <\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction Embedded Service in Salesforce has evolved from its early Snap ins Chat framework into two distinct deployment models \u00a0Version 1 and Version 2. As…<\/p>\n","protected":false},"author":1,"featured_media":1886,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[36],"tags":[38,37,31],"class_list":["post-1848","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agentforce","tag-agentforce","tag-embedded-deployment-services","tag-salesforce"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t