Skip to contentSkip to contact
Sébastien Tang

News AI in Salesforce

Salesforce to acquire Cresta: what to freeze, what to keep

Signed, not closed. Plan voice AI on products available today, freeze bets on a combined Salesforce-Cresta product and get answers in writing.

Written for
Companies planning voice or contact-centre AI on Salesforce, and the integrators and training firms that serve them
Author
, Program and Delivery · Seoul
Published
Reading time
4 min

In short

  • Salesforce has signed a definitive agreement to acquire Cresta, a voice-first platform for customer service calls. The transaction has not closed.
  • Plan voice and contact-centre work on what Service Cloud and Cresta sell today, as two vendors. Freeze milestones that assume a combined product.
  • This month, get roadmap, licensing and existing-integration answers in writing, from Salesforce and from your integrator.
Text

If your plan includes voice or contact-centre AI, build it on products you can buy and configure today. Treat anything that assumes a combined Salesforce and Cresta product as unscheduled. The agreement is signed and the transaction has not closed. A concrete case: a Service Cloud rollout whose phase two reads “Cresta voice agents in the service console” now has a milestone that rests on a sentence in the future tense.

What did Salesforce announce about Cresta?

Salesforce announced that it has signed a definitive agreement to acquire Cresta, which it calls “the voice-first operating system for customer experience”. Cresta’s voice agents resolve complex customer calls end to end. The same platform guides human representatives in real time, analyses every interaction, and tests and improves the voice agents. Salesforce cites Marriott, Comcast and Alaska Airlines among the brands where these agents operate.

For a buyer, two sentences of the announcement matter most. The first: “Together with Service Cloud, businesses will be able to connect every conversation to the customer and to the outcome it drives: resolution, retention and revenue.” The second: “After the transaction closes, Cresta will continue to support the leading contact center and telephony platforms its customers rely on today.” Both are in the future tense, and both depend on the transaction closing. Until the close, plan for two separate vendors.

What is available now, and what is only announced?

Sort every voice item in your plan into two columns, the same exercise as for the Braze agreement.

Available now, from two vendors:

  • Cresta’s platform, sold by Cresta: voice agents, real-time guidance for representatives and interaction analysis, on the contact-centre and telephony platforms its customers use today.
  • Service Cloud as it stands in Winter ‘27. The legacy chat has been retired since 14 February 2026, replaced by Messaging for In-App and Web. Standard Omni-Channel was retired in Summer ‘26, so every org runs on optimised Omni-Channel. In a new org, Agentforce is active by default and former bots become Agentforce agents.

Only announced:

  • Every conversation connected to the customer in Service Cloud, and to the outcome it drives.
  • Bringing “the customer, the conversation and the outcome into one place”, in the words of Kishan Chetan, EVP and GM of Agentforce and Service Cloud.
  • Continued support, after the close, for the contact-centre and telephony platforms Cresta customers use.

An announced item becomes something you can plan when it has a product name, a licence you can price and a release you can test in a sandbox.

What does it change for a Salesforce launch, a training plan, an intermediary?

A company launching Salesforce. Write the voice requirement against what runs today: your telephony or contact-centre platform, the Service Cloud channels in your org, and Cresta only if you buy it now as a separate product. Remove any acceptance criterion that names a combined feature. Ask the Salesforce account team, in writing, for the roadmap and for how a Cresta licence would sit beside your Service Cloud licences. Waiting for the combined product can be the right call, but the sponsor signs that decision with a review date, in the plan of record. If you already run Cresta on another contact-centre platform, the post-close sentence on telephony support is the one to turn into a contract term.

A training plan. Train contact-centre staff and Service Cloud admins on the channels and console their org shows today. A module on voice AI in Service Cloud with nothing to click teaches people to expect screens they will not find, and it gets rewritten once a real product exists. Since October 2026, I rehearse every step of my ADX261 Service Cloud material before the session in a fresh org created like the trainees’ own, so each step works as written. Apply the same test to any voice module: a step that cannot be done in your org today is not in the plan yet. The timing rule does not change: decide the training plan before UAT.

An intermediary. An integrator or IT services firm should not sell a combined Salesforce-Cresta offer, and a training organisation should not open a session on one. What clients need from you this month is an inventory: which delivered integrations touch Cresta or a telephony platform, what each one depends on, and who pays if it has to change after the close. Put it in writing before the client asks. For the contract points to settle with an integrator, see choosing a Salesforce integrator.

What should you do this month?

Run this list before anyone signs a voice or contact-centre commitment. Each answer comes back in writing, with a name and a date.

Voice AI plan checks while the Cresta deal is signed, not closed1. Sort every voice item: available or announced: Tag each scope line, milestone and budget line. Announced means no product name, licence or release you can buy and test today. 2. Freeze milestones built on a combined product: Move them out of the plan of record. The sponsor signs the freeze and the date it will be reviewed. 3. Ask Salesforce for the roadmap in writing: What ships with Service Cloud, under which name, in which release, and what happens to your current contact-centre setup. 4. Ask how licensing works after the close: Which contract covers Cresta, whether your Service Cloud or Cresta terms change, and from which date. 5. Turn the telephony promise into a clause: If you run Cresta on another contact-centre platform, get continued support for that platform written into the contract. 6. Get the integrator’s inventory in writing: Every delivered integration touching Cresta or telephony, what it depends on, and who pays if it has to change. 7. Keep training on what your org shows today: Channels and console as configured in your org. Rehearse each step in an org like the trainees’ before the session. 8. Name who reopens the plan when the deal closes: One owner, one review meeting, and the sorted list from the first check as its input.Sort every voice item: available or announcedTag each scope line, milestone and budget line. Announced means no product name,licence or release you can buy and test today.Freeze milestones built on a combined productMove them out of the plan of record. The sponsor signs the freeze and the date it will bereviewed.Ask Salesforce for the roadmap in writingWhat ships with Service Cloud, under which name, in which release, and what happens toyour current contact-centre setup.Ask how licensing works after the closeWhich contract covers Cresta, whether your Service Cloud or Cresta terms change, and fromwhich date.Turn the telephony promise into a clauseIf you run Cresta on another contact-centre platform, get continued support for that platformwritten into the contract.Get the integrator’s inventory in writingEvery delivered integration touching Cresta or telephony, what it depends on, and who paysif it has to change.Keep training on what your org shows todayChannels and console as configured in your org. Rehearse each step in an org like thetrainees’ before the session.Name who reopens the plan when the deal closesOne owner, one review meeting, and the sorted list from the first check as its input.Voice AI plan checks while the Cresta deal is signed, not closed1. Sort every voice item: available or announced: Tag each scope line, milestone and budget line. Announced means no product name, licence or release you can buy and test today. 2. Freeze milestones built on a combined product: Move them out of the plan of record. The sponsor signs the freeze and the date it will be reviewed. 3. Ask Salesforce for the roadmap in writing: What ships with Service Cloud, under which name, in which release, and what happens to your current contact-centre setup. 4. Ask how licensing works after the close: Which contract covers Cresta, whether your Service Cloud or Cresta terms change, and from which date. 5. Turn the telephony promise into a clause: If you run Cresta on another contact-centre platform, get continued support for that platform written into the contract. 6. Get the integrator’s inventory in writing: Every delivered integration touching Cresta or telephony, what it depends on, and who pays if it has to change. 7. Keep training on what your org shows today: Channels and console as configured in your org. Rehearse each step in an org like the trainees’ before the session. 8. Name who reopens the plan when the deal closes: One owner, one review meeting, and the sorted list from the first check as its input.Sort every voice item: available orannouncedTag each scope line, milestone and budgetline. Announced means no product name,licence or release you can buy and testtoday.Freeze milestones built on a combinedproductMove them out of the plan of record. Thesponsor signs the freeze and the date it willbe reviewed.Ask Salesforce for the roadmap inwritingWhat ships with Service Cloud, underwhich name, in which release, and whathappens to your current contact-centresetup.Ask how licensing works after thecloseWhich contract covers Cresta, whether yourService Cloud or Cresta terms change, andfrom which date.Turn the telephony promise into aclauseIf you run Cresta on another contact-centreplatform, get continued support for thatplatform written into the contract.Get the integrator’s inventory inwritingEvery delivered integration touching Crestaor telephony, what it depends on, and whopays if it has to change.Keep training on what your org showstodayChannels and console as configured in yourorg. Rehearse each step in an org like thetrainees’ before the session.Name who reopens the plan when thedeal closesOne owner, one review meeting, and thesorted list from the first check as its input.
Table 1 Eight checks to run this month before anyone signs a voice or contact-centre commitment.

Sources

  1. SalesforceSalesforce Signs Definitive Agreement to Acquire Cresta - Salesforce

Contact

Is this on your table?

Tell me where your programme or your team stands, and what you need to decide.

Request a call

WorkshopsTrainer profile

Same module

All notes