If your contact centre runs Genesys with Salesforce through the Genesys Cloud CTI Adapter, there’s a date you need to know: February 2028. That’s when the adapter, and the Open CTI model it’s built on, reaches end of life.
Two years sounds like plenty of runway. For a voice migration inside a live contact centre, it’s less than you think. Here’s what’s changing, why it’s happening, and how to make sure this lands as an upgrade rather than a scramble.
What’s actually happening
Since 2015, the standard way to connect Genesys and Salesforce has been the CTI Adapter: a softphone embedded in the Salesforce Service Console, with Genesys handling the telephony behind it. It worked. Thousands of contact centres run on it today.
But it was always a bolt-on. The phone lives in an iframe, the routing lives in the IVR, and Salesforce mostly finds out about calls after they’ve happened. That architecture has a ceiling, and the industry has hit it.
So Genesys and Salesforce changed course. In 2023 they launched CX Cloud, a joint product that combines Genesys routing and workforce management with native Salesforce Service Cloud Voice. Since then, the two companies have been building a shared roadmap around it, including AI capabilities like Agentforce and Einstein. The old adapter isn’t part of that future. Hence the retirement date.
Why this isn’t just an IT housekeeping item
It’s tempting to file this under “vendor forces upgrade, we comply.” That framing will cost you.
The honest version: staying on the adapter until the deadline means two more years of accumulating technical debt on a platform with no future roadmap, while the capabilities being built for contact centres, particularly the AI ones, land on the other side of the fence.
And the move itself isn’t a component swap. Service Cloud Voice works on a fundamentally different model. Voice becomes a channel inside Salesforce rather than a system beside it. Calls route through the same engine as chat and email. Transcription happens in real time, inside the customer record. Supervisors see voice and digital in one place.
That’s a different agent experience, a different supervisor experience, and different reporting. Which means the real question isn’t “what do we replace the adapter with?” It’s “what do we want our contact centre to be able to do once we’ve moved?”
Some organisations will answer “exactly what it does today, just supported.” That’s legitimate. Others will use the migration to fix the workflow problems they’ve been living with for years. Both are valid destinations. Not choosing is the only bad option, because it usually means someone else chooses for you in a hurry in late 2027.
The maths on the timeline
February 2028 minus today is about 19 months. Now subtract:
- Budget cycles. If this needs FY27/28 funding, the business case has to exist well before the money does.
- Discovery and scoping. Understanding your current call flows, workflows, reporting and compliance requirements takes real time, especially in regulated industries.
- The migration itself. Depending on scope, these programs run months, not weeks.
- The queue. Every other Genesys-Salesforce customer in the country is looking at the same deadline. Delivery capacity, yours and your partners’, gets scarce as the date approaches.
Organisations that start scoping in 2026 migrate on their own terms. Organisations that start in mid-2027 migrate on the deadline’s terms. Same project, very different experience.
What good preparation looks like
You don’t need a full program plan yet. You need answers to a handful of questions:
Do you know your current state? What’s actually configured in your CTI setup, which workflows depend on it, and what would break if it changed. Most organisations are surprised by this list.
Do you know your licensing position? Service Cloud Voice has its own licensing model, and getting this wrong is the most common source of budget surprises.
Do you know your ambition level? A like-for-like move, an improved agent experience, or an AI-augmented contact centre are genuinely different projects with different timelines. Deciding this early shapes everything else.
Do you know who’s doing the Genesys side and who’s doing the Salesforce side? These migrations sit across two platforms. Clear ownership of each half saves months of finger-pointing.
If you can answer all four, you’re ahead of most. If you can’t, that’s normal, and it’s fixable in weeks rather than months if you start now.
Where 8Squad fits
We’re a Salesforce Summit Partner and Global Winner of the Salesforce Partner Innovation Award for Service Cloud Consulting. We’ve delivered Service Cloud Voice across regulated industries at every scale, from 7-agent pilots to national contact centres, with a 100% onshore Australian team.
We’ll also tell you the unglamorous truths: not every migration needs the full transformation, some of this work won’t be quick, and the Genesys side of the equation matters as much as the Salesforce side.
If you’re running the Genesys CTI Adapter today, start with our complimentary Service Cloud Voice readiness assessment. A 60-minute conversation about your current setup, then a clear view of your licensing, configuration and timeline within 5 business days. No obligation, no pitch theatre. Just the answers you need to plan properly.
