Messaging for Web
Messaging for Web is the Salesforce Service Cloud feature that lets customers exchange messages with support agents through a chat widget embedded on a website.
Definition
Messaging for Web is the Salesforce Service Cloud feature that lets customers exchange messages with support agents through a chat widget embedded on a website. Customers click a Chat-with-us button on the company''s site; a chat window opens; messages flow to Salesforce where they appear in the Service Console for an agent to respond. The product is the web-based sibling to Messaging for In-App, with similar architecture and behavior but deployed via a JavaScript snippet on the website instead of a native mobile SDK.
Messaging for Web replaced the older Live Agent (now Salesforce Chat) product as the strategic direction for web-based customer messaging. Both products handle customer-to-agent web chat, but Messaging for Web ships modern async-conversation support (customers can close the browser tab and return hours later), tighter Einstein Bot integration, and a unified Messaging Session data model shared with In-App, SMS, and WhatsApp messaging. New deployments default to Messaging for Web; existing Live Agent deployments are typically migrated.
How Messaging for Web modernizes customer-website chat
The JavaScript snippet
Web developers add a small JavaScript snippet to every page that should host the chat widget. The snippet loads the Salesforce-hosted chat library, renders the chat button, and handles the entire conversation flow. The integration is lightweight; the snippet is typically 5-10 lines of code per page.
Async conversation support
Messaging for Web supports both real-time and async conversations. A customer can start a chat, close the browser tab, and return later to find the agent''s response in the same conversation. The persistent identity (via cookies or authenticated session) keeps the conversation tied to the customer across visits.
Einstein Bot integration
Most Messaging for Web deployments start the conversation with an Einstein Bot. The bot greets the customer, recognizes intent, attempts self-service, and escalates to a human agent when needed. The integration is configured the same way as for In-App and SMS Messaging; the bot configuration is reusable across channels.
Omni-Channel routing
Messages route through Omni-Channel the same way In-App, SMS, and WhatsApp Messaging do. The platform matches conversations to agents based on skills, capacity, and presence. The unified routing across channels means an agent can handle a web chat, an SMS conversation, and a WhatsApp inquiry from the same Service Console session.
Live Agent migration
Live Agent (now Salesforce Chat) was the previous-generation web chat product. Salesforce supports both products in parallel but encourages migration to Messaging for Web for new deployments. Migration is non-trivial: the snippet, the Service Console configuration, and the Einstein Bot definitions all change. Plan a multi-week project.
Customer identity and context
The JavaScript snippet can pass authenticated user context to Salesforce. If the customer is logged into the website, the snippet forwards the user ID; Salesforce looks up the matching Contact and surfaces account history to the agent. Anonymous visitors get a session-scoped identity that persists across page loads but not across sessions.
Branding and customization
The chat widget supports significant branding customization: company colors, logo, button placement, opening greeting, agent display name. The customization runs through Setup, Messaging configurations; admins can tune the look-and-feel to match the brand without custom development.
Roll out Messaging for Web on a customer site
Messaging for Web rollout is a coordinated project between Salesforce admins and the web team. Plan multi-week effort for snippet integration plus Salesforce-side configuration.
- Confirm Messaging licensing
Messaging for Web is licensed separately. Confirm contract terms with the Salesforce account team.
- Configure Messaging in Setup
Setup, Messaging, configure the deployment for Web. Set up Omni-Channel routing, agent skills, and Service Console layout.
- Build the Einstein Bot
Design the bot conversation: greeting, intent recognition, self-service actions, escalation rules. Test thoroughly before exposing to customers.
- Deploy the JavaScript snippet
Web developers add the snippet to relevant pages. Test the chat widget loads, opens, and connects to Salesforce.
- Configure customer identity passing
For authenticated users, configure the snippet to forward the user ID. Salesforce looks up the matching Contact for agent context.
- Pilot, measure, expand
Launch to a subset of pages or customer cohorts first. Measure deflection rate, customer satisfaction, agent feedback. Expand once baselines exist.
- Messaging for Web replaces Live Agent. Migration from Live Agent is non-trivial; plan a multi-week project.
- The JavaScript snippet must load on every page that should host the chat widget. Missed pages produce missed conversation opportunities.
- Einstein Bot quality drives deflection. A poorly-trained bot frustrates customers and increases escalation volume.
- Messaging licensing scales with conversation volume. Plan capacity for promotional spikes.
Trust & references
Cross-checked against the following references.
- Messaging for WebSalesforce Help
- Salesforce Messaging OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Messaging for Web.
- Salesforce Chat (Live Agent)Salesforce Help
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 is Messaging for Web?
Q2. How does it differ from traditional web chat?
Q3. What does it replace?
Discussion
Loading discussion…