When support volume rises, the biggest gap often isn’t email or chat. It’s the phone line, where context gets lost, handoffs are slower, and managers have less structured data to work with.
If your business already uses AI for written support but treats calls as a separate workflow, that divide is starting to look expensive.
Salesforce moves deeper into voice support
Salesforce has announced plans to acquire Cresta, a contact-center software company known for AI voice agents for customer service. Silicon Republic reports Salesforce wants to use the deal to expand from digital support into phone-based support by combining Cresta’s voice capabilities with its own agent and cloud products.
The reported $2.7 billion valuation came from Dealroom citing an anonymous source, while Salesforce said only that the transaction is expected to close in the first quarter of fiscal 2028 and remains subject to closing conditions.
- Voice becomes a priority. Salesforce said it plans to acquire Cresta to add voice-powered customer service capabilities to its support stack.
- Phone and digital support converge. The company said it intends to pair Cresta’s voice agents with its own agents and cloud, extending digital support into phone calls.
- Conversation intelligence comes into platform workflows. Cresta’s leadership said the combination is meant to embed real-time conversation intelligence and agentic customer experience features inside Salesforce’s service platform.
- Closing is still ahead. Salesforce said the transaction is expected to close in the first quarter of fiscal 2028, subject to standard closing conditions.
Why the channel split matters less now
For business owners, the important part isn’t the deal size. It’s the direction: major platforms are treating voice as part of the same service workflow, not as a side system managed on its own.
That changes how teams should think about support operations. Once phone conversations become structured inputs for AI-assisted work, managers can apply the same playbooks, approvals, summaries, and follow-up processes across channels instead of rebuilding them for each one.
It also raises the bar for consistency. If a customer calls after using chat or email, your team needs the same context, rules, and account history available in one place or the experience breaks down fast.
How Metomorph helps teams operationalize the same shift
Metomorph is useful here because the operational problem is broader than voice itself. The real challenge is turning every support interaction into structured work the rest of the business can act on.
Imagine your team runs a high-value service project for a client with frequent support requests. Inside a Metomorph project, the assistant already has the project context, attached documents, and business rules, so follow-up work doesn’t start from a blank thread each time.
After a call summary or support notes are added to the project knowledge base, the team can use organization skills to produce a consistent incident recap, draft the client update, or prepare an internal handoff using the same approved process every time. That helps reduce the channel-to-channel drift that shows up when one person handled the call and another writes the follow-up.
From there, the task board can turn that follow-up into visible work with owners and due dates, while dynamic reports can pull from live project records to show recurring issues or slipped actions. The point isn’t that Metomorph provides Cresta-style voice agents. It’s that when customer interactions create work, Metomorph helps teams capture context once and run the response process consistently.
What to do this week
- Map one support issue from first contact to final follow-up. If phone, email, and internal tasks live in different places, note where context gets retyped or lost.
- Pick one repeatable post-call workflow to standardize, such as an escalation summary or client follow-up. A reusable process matters more than adding another standalone AI tool.
- Set explicit rules for sensitive responses and approvals before you automate follow-up steps. Consistency usually fails at the handoff, not the transcript.
- Start with one project or service line in Metomorph and build the support follow-up flow there first. Then measure whether summaries, tasks, and reporting stay aligned across the team.
Explore Project context, Organization skills, Task board in Metomorph.
Source: Silicon Republic, Salesforce to acquire Cresta in deal reportedly valued at $2.7bn (November 3, 2026).