Where Salesforce Edge Messaging fits after Live Chat retirement, how it compares to Digital Engagement, the setup steps and the migration pitfalls to plan for.
Live Chat has been retired by Salesforce, but many organizations are still working through the transition to Salesforce's newer messaging framework. For teams planning the move, the challenge is less about migration and more about understanding what changes after implementation. Will it replace the prior systems, or will it develop the architecture in one layer? The short answer: Salesforce Edge Messaging only updates how messages travel through web or mobile apps. Built on a global Edge network, it offers lower latency, higher security, and more scalability. The platform doesn't remove your current licensing or change the agent's workspace.
It's important to understand because Edge Messaging is often mistaken for a complete replacement of the Live Chat architecture. In reality, it affects only one part of the overall setup. In this blog, we explain where Salesforce Edge Messaging fits, what it replaces, and what remains unchanged. We’ll also share a few tips to help you successfully make the move from legacy Live Chat.
How Does Salesforce Edge Messaging Work?
It routes customers' traffic via distributed Edge nodes, not a single data-center connection. The handshake is completed by the nearest node, and then data is routed over optimized paths to the Salesforce instance. Since the distance is shorter, delays become smaller, and customers get faster responses.
The Edge nodes are positioned between the customer's device and Salesforce. They carry the conversation to Omni-Channel (where an agent is assigned to the conversation), and Messaging Sessions and Cases remain within the CRM. Thus, transport and workforce management exist as separate layers. Key features:
- Reduced message delays: Real-time exchanges are immediate for the client.
- Stronger security: Protected through rigid protocols and controlled data residency, allowing sensitive conversations to be protected.
- Session persistence: Asynchronous conversations flow freely between web and mobile apps.
Edge Messaging vs Digital Engagement
| Factors | Edge Messaging | Digital Engagement |
|---|---|---|
| Nature | A routing and transport layer | A licensed bundle of channels and capacity |
| Purpose | Speed, security, scale | Capacity and access to channels |
| Licensing | Included in the platform upgrade | Separately licensed |
| Channels | Powers web and in-app sessions | Adds SMS, WhatsApp, and others |
| Routing | Passes conversations to Omni-Channel | Relies on Omni-Channel for assignment |
| Agent view | Unchanged | No console changes, but more channels are added |
| Cost driver | Depends on implementation | Per-channel licensing |
| Best used for | High-volume, performance-critical routing | Expanding the channel mix and managing licensing |
For any Salesforce Digital Engagement licensing cost, budget owners should ask for an up-to-date quote, as pricing varies by channel and volume. If SMS is the main channel you need, see how to send SMS from Salesforce without Digital Engagement.
What Does Salesforce Edge Messaging Replace?
It replaces three older patterns:
- Legacy Live Chat: Web components that work only while a live session is open. When the session ends, the chat also ends, and users can’t continue the conversation.
- Standard messaging channels: Existing Salesforce messaging channels for web and mobile move to Enhanced Messaging infrastructure with more powerful routing and media capabilities.
- Direct-to-data-center routing: Requests are sent through distributed Edge nodes rather than a single regional server, helping conversations start faster.
What Does Salesforce Edge Messaging NOT Replace?
Four components remain stable:
- Conversation routing: Omni-Channel continues to control queue assignment, capacity limits, and agent availability.
- Digital Engagement licensing: Edge features are enabled with a platform upgrade, but licenses for third-party channels such as SMS and WhatsApp are still required.
- Agent workspace: Users continue to work in the Service Console. Edge Messaging only changes how messages are delivered.
- Core CRM data models: Messaging Sessions, Contacts, and Cases remain central.
The bottom line: queue design, presence configuration, and console training stay valid, and budgets for third-party channels remain separate.
What Does Edge Messaging Setup Involve?
Before implementing a reliable Edge Messaging setup, make sure you have a Service Cloud license, current Messaging permissions, and Omni-Channel set up with the appropriate presence statuses. Then follow these steps:
Enable Messaging
Turn on Messaging features by opening Setup and selecting Messaging Settings.
Create the Channel
Add an Enhanced Messaging channel for customer conversations or connect to an external messaging platform.
Configure Routing
Assign queues, Omni-Channel routing configurations, or Agentforce agents.
Deploy Web Components
Messaging components can be added to Experience Cloud or external sites using the code snippet.
Test and Verify
Assess connection latency and verify agent status in Omni-Channel.
Pro tip: If possible, test with real queues and peak-hour volumes. Settings that worked in a sandbox might not hold up in production under your routing rules.
How Should Teams Plan the Migration?
Start with an inventory of all active Live Chat deployments, pre-chat forms, custom scripts, and routing rules. Before cutover, decide which Live Chat features Edge Messaging will replace. This sequence lets you uncover gaps while they're cheaper to fix. Choose a Live Chat to Enhanced Messaging migration partner based on facts, not promises; our messaging migration checklist covers the essentials.
Check for a documented history of migrations from Live Agent, a well-thought-out testing strategy, and post-launch support. Ideally, Salesforce Edge Messaging implementation partners should have experience with architecture validation, the right certifications, custom LWC implementation, and security compliance. Three pitfalls deserve early attention:
- Conversations can end up in the wrong place when existing configurations are not carried over.
- Access to previously shared content becomes unreliable when media references expire or break.
- Information shared during earlier conversations may no longer be available when needed.
Conclusion: Next Steps
With Live Chat discontinued, migration is no longer a decision that can be deferred. Salesforce Edge Messaging, by providing speed, agility, and security at scale, offers a way to modernize business communications. It improves how messages are delivered but doesn't replace licensing, routing, or the agent's workspace. Before making the move, analyze your current deployment, confirm requirements, and plan spending carefully. Moving early ensures continuity and prepares your business for seamless engagement across channels.
Add SMS and WhatsApp to Your Salesforce Messaging
See how GirikSMS adds texting channels without extra Digital Engagement licenses.
