Last month, Salesforce officially retired its legacy chat products.
While most of the world was focused on Valentine’s Day, thousands of CX leaders were watching a different kind of countdown: the end of LiveAgent, Embedded Chat, and Service Chat.
If you’re still running those tools today, you’re not just using older software. You’re operating on infrastructure that no longer receives security patches, updates, or support.
And for many teams, the real challenge isn’t the retirement itself.
It’s what comes next.
The New Reality: A Costly Migration
Salesforce’s recommended replacement is Messaging for In-App and Web (MIAW).
On paper, it sounds like the natural next step. In practice, many enterprise teams are discovering the transition is far from simple.
To replicate the functionality they had before, organizations are often asked to:
-
Purchase the Digital Engagement license, typically around $75 per user per month
-
Rebuild messaging components and flows
-
Reconfigure routing, automation, and integrations
For a 100-agent team, the licensing alone can approach $90,000 per year – and that’s before any implementation work begins.
And implementation isn’t trivial. Many migrations require rebuilding parts of the messaging infrastructure inside Salesforce, from Lightning components to Omni-Channel configurations.
The result is often a 4–6 month project just to return to the baseline experience teams had before.
Why This Matters More in the AI Era
A few years ago, that might have been acceptable.
But customer service has changed.
Today, CX leaders are being asked to deploy automation, messaging, and AI-powered service experiences quickly. Waiting half a year to rebuild messaging infrastructure doesn’t leave much room for innovation.
And this is where many teams run into a deeper issue.
When your customer engagement layer is tightly coupled to the CRM, every change becomes heavier than it should be.
Even small adjustments – new workflows, automation rules, or messaging journeys – can require development work or platform changes.
That’s not a technology limitation. It’s an architectural one.
CRM Is the System of Record – It Shouldn’t Be the System of Action
Salesforce remains one of the most powerful CRM platforms available. It excels at managing customer data, cases, and operational processes.
But the interaction layer – the place where conversations happen – is a different problem.
Modern CX architecture increasingly separates the two.
Salesforce acts as the system of record, storing customer information and operational data.
A dedicated CX platform becomes the system of action, managing messaging channels, automation, and AI-driven conversations.
This model allows teams to innovate quickly without rebuilding their CRM environment every time they want to improve customer engagement.
This architecture allows organizations to introduce automation and digital service journeys without rebuilding their CRM environment.
For example, UPS ASC Israel automated 70% of its customer service workflows and achieved 86% resolution on proactive WhatsApp journeys using CommBox, while maintaining integrations with its backend operational systems.
What the Numbers Actually Look Like
When CX teams compare their options, the differences become clearer.
| Category | Legacy Chat | Salesforce MIAW | CommBox |
|---|---|---|---|
| Licensing | $0 | ~$90k/year | No Digital Engagement SKU |
| Implementation | None | $40k–$60k rebuild | ~$5k–$10k |
| AI Interaction Costs | N/A | Per interaction | Included tiers |
| Security | Unsupported | Supported | Enterprise-grade |
| Time to Production | Immediate but risky | 4–6 months | 3–4 weeks |
Instead of rebuilding messaging infrastructure inside Salesforce, CommBox operates as a customer engagement layer that integrates directly with the CRM.
Salesforce remains the source of truth, while CommBox manages conversations, automation, and AI workflows across channels.
Real Question for CX Leaders
The retirement of Salesforce chat tools forces a decision. But the question isn’t simply which tool replaces the old one.
The bigger question is architectural.
Should customer engagement live entirely inside the CRM?
Or should the CRM remain the system of record, while a dedicated platform handles the speed, automation, and flexibility modern CX requires?
More organizations are choosing the second approach.
Not because they want to replace Salesforce – but because they want to move faster than the CRM alone allows.
Is Salesforce MIAW the Only Option?
Salesforce positions Messaging for In-App and Web as the natural upgrade path, but many CX leaders are evaluating alternatives before committing to a full migration.
Dedicated customer engagement platforms can integrate with Salesforce while allowing companies to deploy messaging, automation, and AI capabilities independently of CRM release cycles.
This approach allows teams to launch modern CX capabilities in weeks instead of rebuilding messaging infrastructure inside the CRM.
How to Upgrade to Modern Architecture.
The end of legacy chat isn’t just a migration deadline. It’s an opportunity to rethink how customer engagement works.
Instead of investing months rebuilding infrastructure inside the CRM, many organizations are deploying an AI-powered CX layer on top of Salesforce – one that can go live in weeks and evolve as customer expectations change.
That’s the shift we’re seeing across the market.
And for many CX leaders, it’s the difference between simply replacing a tool and actually modernizing customer experience.
Evaluating Your Salesforce Migration Options?
Before committing to a costly MIAW migration, take a closer look at how a dedicated CX platform compares. See the full Salesforce vs. CommBox comparison
