What happened
Salesforce announced the agreement on November 2, 2026. The company describes Cresta as a voice-first operating system for customer experience. According to Salesforce’s announcement, Cresta’s voice agents can resolve complex customer calls end to end. They are built to hold natural, real-time conversations, handle interruptions, and operate at enterprise scale. Salesforce names Marriott, Comcast, and Alaska Airlines as brands using the platform.
Cresta is intended to work with human service staff as well as autonomously. Salesforce says the platform guides human representatives in real time and analyzes every interaction. It also tests and improves voice agents. The company says human representatives and voice agents are held to the same quality standard, with the aim of using each interaction to improve the next one. That framing makes the product a service-operation system, not simply a speech interface that answers incoming calls.
Salesforce’s stated rationale is that customer conversations contain useful information but are often isolated from customer context and from systems that can act on it. Salesforce says it brings customer history and the systems used to get work done, while Cresta brings conversation intelligence and voice-agent execution. With Service Cloud, the companies intend to connect each conversation to the relevant customer and to an outcome such as resolution, retention, or revenue.
The announcement does not describe a new combined product as available today. It says Cresta will be brought together with Service Cloud after the transaction closes. Cresta will continue to support the contact-center and telephony platforms its customers use today. Salesforce expects closing in the first quarter of fiscal year 2028, subject to customary closing conditions, including required regulatory approvals. The company does not disclose the purchase price, financial terms, a technical integration architecture, or a rollout schedule for customers.
What the archive adds
New Runtime’s earlier coverage of Salesforce in Claude on September 23, 2026 examined a permissioned sales-workflow agent that brings CRM context into assistance. This is a new event, not a restatement: Salesforce is seeking voice customer-service capabilities through an acquisition, rather than extending the sales workflow in that earlier note.
Trend signal
This supports the pattern agent-ready software exposes capabilities. Cresta supplies an agentic conversation layer, while Salesforce intends to supply customer context and systems for action. The proposed combination points toward service software where agents can move from understanding an interaction to acting on business data, although Salesforce has not described permissions, APIs, or integration mechanics.
Why now
Salesforce says voice is where customers bring their highest-stakes service issues and where service must work in the moment. Its announcement also argues that listening alone is insufficient as voice agents handle more complex interactions: insight must connect to customer records and operational tools. The deal is positioned as an answer to that gap, but Salesforce gives no timetable for when the proposed combined capabilities will reach customers.
Connections to other events
An earlier New Runtime note on Salesforce in Claude described Salesforce CRM context being used in a permissioned sales workflow. Cresta addresses a different operational surface: real-time customer-service conversations. Together, the two developments suggest Salesforce is placing agentic interfaces around both sales work and service work, while retaining CRM as the context and action layer.
Why it matters
For teams building customer-service agents, the acquisition underlines that voice quality alone is not the complete product. A useful service workflow needs customer history, authority to take the next action, and a process for checking and improving both human and automated work. Salesforce is proposing that the customer record, the conversation, and the measured business outcome should sit in one operational loop.
That direction could make CRM integration more important when teams select contact-center AI. It also creates practical questions about portability, access control, and ownership of interaction data. Cresta’s planned continued support for existing contact-center and telephony platforms matters for organizations that do not want to replace their stack. Builders should assess whether a future combined offering can retain those integrations while safely using CRM context to complete service work.
What happens next
- Salesforce completes or delays the Cresta transaction after regulatory review. (6 months, 70%). Watch for: closing confirmation or revised timing.
- Salesforce outlines how Cresta connects with Service Cloud and customer records. (12 months, 65%). Watch for: product documentation, availability dates, or integration details.
Limits and uncertainty
This is a signed agreement rather than a completed acquisition. Closing remains subject to customary conditions, including regulatory approvals, and Salesforce expects it in the first quarter of fiscal year 2028. Salesforce has not disclosed the purchase price, commercial terms, integration design, rollout dates, or how access to customer records will be governed in a combined product.
Salesforce’s descriptions of Cresta’s scale and capabilities are company claims. The announcement supplies no call-volume figures, resolution rates, customer-retention results, revenue measurements, pricing, or independent comparison with other voice-agent systems. It also does not say whether current Cresta customers will face product, contract, or platform changes after closing.
Skill to build now
Map one customer-service workflow from conversation to outcome this week. List the customer data an agent needs, the actions it may take, the systems where those actions occur, and the points where a human must review the result. Then test whether the workflow can preserve permissions and leave an auditable record. That exercise exposes whether a voice or chat agent is merely summarizing a conversation or can safely complete useful work.
Reader takeaway
Salesforce is buying Cresta to bring voice customer-service agents closer to CRM records and service outcomes. The strategic direction is clear: conversations should trigger informed action, not remain isolated transcripts. But this is not yet a shipped integration, and the terms, controls, rollout, and measured performance of the combined product remain unknown.
Open question
Can Salesforce integrate Cresta’s voice workflows with Service Cloud while preserving customer choice of contact-center and telephony platforms, along with clear controls over what an agent may access and do?