You are currently viewing Salesforce Open CTI Retirement: Everything You Need to Know About Service Cloud Voiceย 
Salesforce Open CTI

Salesforce Open CTI Retirement: Everything You Need to Know About Service Cloud Voiceย 

Sharing is caring!

Salesforce is officially retiring from Open CTI (Computer Telephony Integration) on February 28, 2028, making it essential for organizations to plan their transition to Salesforce Voice (formerly Service Cloud Voice). This change marks an important shift in how businesses integrate telephony with their Salesforce CRM environments.ย 

Open CTI has been in maintenance mode since 2020, with no new features or enhancements planned. Furthermore, Salesforce stopped making Open CTI available for newly created Agentforce Service organizations on February 16, 2026. While existing implementations continue to work until the retirement date, businesses need to start evaluating their migration options to avoid operational disruptions.ย 

What to do now:ย 

  • Inventory your Open CTI users, phone numbers, reports and custom logic.ย 
  • Check whether your telephony vendor has a Partner Contact Center package on AgentExchange (formerly AppExchange).ย 
  • Pick your path, run a sandbox test and a parallel run, then cut over well before 2028.ย 

This guide explores the Open CTI retirement timeline, key differences between Open CTI and Salesforce Voice, available migration options, implementation steps, and best practices for a successful transition.ย 

What Is Salesforce Open CTI?ย 

Salesforce Open CTI is a JavaScript-based API that enables third-party telephony providers to integrate their phone systems directly into the Salesforce Service Console.ย 

It allows customer service representatives to make and receive calls, view customer information, and manage interactions without switching between multiple applications.ย 

A typical Open CTI implementation consists of three main components:ย 

  • CTI Adapter Package: Provided by the telephony vendor to connect its phone system with Salesforce.ย 
  • Call Center Definition File: Defines the configuration and integration settings required for the CTI solution.ย 
  • Softphone Layout: Determines how the softphone appears and functions within the Salesforce interface.ย 

Although Open CTI has supported CRM and telephony integration for years, its maintenance-only status limits future development and access to newer Salesforce capabilities.ย 

Salesforce Open CTI Retirement: Important Dates and Changesย 

Salesforce has established a clear retirement timeline for Open CTI. Organizations should understand these milestones to prepare their contact centers accordingly.ย 

Dateย 

Important Updateย 

2020ย 

Open CTI entered maintenance mode.ย 

February 16, 2026ย 

Open CTI became unavailable for newly created Agentforce Service organizations.ย 

February 28, 2028ย 

Open CTI will be fully retired.ย 

After February 28, 2028, the Open CTI API and its associated components, including call center adapters, softphone layouts, definition files, and custom CTI logic, will no longer function. This means businesses cannot rely on their existing Open CTI implementations after the retirement date.ย 

SCV and Open CTI milestones

SCV and Open CTI milestones ยท 2020 to 2028ย 

Salesforce’s own example migration plan runs about eight weeks per contact center, but phone number porting alone can take several weeks. Start early, especially if you run several orgs or call centers.ย 

Open CTI vs. Salesforce Voice: Understanding the Key Differencesย 

The transition from Open CTI to Salesforce Voice involves more than replacing an integration package. It represents a shift in how telephony interactions are managed within Salesforce.ย 

With Open CTI, the external telephony platform manages calls, while Salesforce receives information through the CTI adapter. With Salesforce Voice, telephony becomes a more integrated part of the Salesforce environment, supported by Omni-Channel and VoiceCall records.ย 

Open CTI vs Service Cloud Voice architecture

Open CTI vs Service Cloud Voice architectureย 

With Open CTI, the call lives in the vendor’s system and Salesforce only receive what the adapter pushes in. With SCV, the call, its transcript and its outcome all live in Salesforce, which is what makes the AI features possible.ย 

Capabilityย 

Open CTIย 

Service Cloud Voiceย 

Call controlย 

Vendor softphone in an embedded frameย 

Native Omni-Channel softphone in the consoleย 

Routingย 

Done on the telephony platformย 

Omni-Channel, including Omni-Channel Flowsย 

Data in Salesforceย 

Task or activity logged after the callย 

VoiceCall record linked to the case or recordย 

Transcriptionย 

Vendor-dependent, usually outside Salesforceย 

Real-time transcript in the consoleย 

AI assistย 

Limited or custom-builtย 

Einstein next best actions, Agentforceย 

Supervisor viewย 

Usually in the vendor’s toolsย 

Live calls next to digital work in Salesforceย 

Roadmapย 

Maintenance only, retires Feb 28, 2028ย 

Active investment every releaseย 

Four Salesforce Voice Migration Optionsย 

Salesforce supports four Voice solutions. All four give you a phone channel natively integrated with Omni-Channel, your CRM data and AI (Trailhead: Choose Your Migration Path).ย 

1. Partner Contact Centerย 

This option allows organizations to continue using their existing telephony provider through a supported Partner Contact Center package available on AgentExchange.ย 

It is suitable for businesses using providers such as Genesys, Cisco, Five9, or Talkdesk, provided their vendor offers a supported package.ย 

Best for: Organizations looking to retain their existing telephony provider while modernizing Salesforce integration.ย 

2. Partner Contact Center with Telephony from Amazon Connectย 

Businesses already using their own Amazon Connect environment can integrate it with Salesforce through this option.ย 

Organizations continue managing their AWS infrastructure while benefiting from Salesforce Voice capabilities.ย 

Best for: Businesses that already operate and manage their own Amazon Connect instance.ย 

3. Partner Contact Center with Amazon Connectย 

This option provides Amazon Connect telephony through a Salesforce-managed AWS account.ย 

Organizations can use Amazon Connect capabilities without independently managing the underlying AWS environment.ย 

Best for: Businesses that want Amazon Connect integration with less infrastructure management.ย 

4. Agentforce Contact Centerย 

Agentforce Contact Center provides a fully Salesforce-managed contact center experience without requiring a separate third-party telephony provider.ย 

It brings CRM, voice interactions, and AI capabilities together within the Salesforce ecosystem.ย 

Best for: Organizations looking to consolidate their contact center technology and adopt a Salesforce-first approach.ย 

Key Benefits of Migrating to Salesforce Voiceย 

Moving from Open CTI to Salesforce Voice can help organizations improve contact center operations while creating a stronger foundation for AI-driven customer service.ย 

  1. Unified Customer Interaction Management

Salesforce Voice brings phone interactions into the same Omni-Channel environment used for digital communication. Customer service representatives can manage calls alongside other service activities without constantly switching between applications.ย 

  1. Improved Call Routing

Omni-Channel Flows enable businesses to route incoming calls based on agent availability, skills, queues, and specific business conditions. This helps connect customers with the appropriate representatives.ย 

  1. Real-Time Transcription and AI Assistance

Salesforce Voice supports real-time call transcription, allowing agents to follow conversations while accessing relevant customer information and recommendations.ย 

Einstein capabilities and Agentforce can further support agents with next-best-action recommendations and automated workflows.ย 

  1. Better Call Reporting and Visibility

VoiceCall records provide structured information about customer interactions, including call duration, recordings, transcripts, and linked cases.ย 

This helps organizations build more meaningful reports and improve contact center performance monitoring.ย 

  1. Improved Agent and Supervisor Experience

Supervisors can monitor multiple calls alongside chats, emails, and messaging interactions. This provides better visibility into contact center activities and helps teams manage queues and agent capacity more effectively.ย 

How to Migrate from Open CTI to Salesforce Voiceย 

In SCV, every step of the call happens in, or is recorded in Salesforce. An AI agent can take the call first and hand off to a person only when needed.ย 

Inbound call flow ยท 7 steps, 1 decision

Inbound call flowย ย 

The provider’s IVR answers, and Agentforce Voice can resolve simple requests on its own. Calls it cannot resolve pass to an Omni-Channel Flow, which picks an agent by skills, case context or custom conditions. The agent works the call in the console with a live transcript and suggestions, then wraps up with an AI-drafted summary.ย 

What it looks like in Salesforceย 

With Voice, calling moves into the same Omni-Channel widget reps already use for digital channels, with recordings and real-time transcription built in (Trailhead). The two mockups below show the agent’s screen and the admin’s setup. They are illustrations with sample data, not real screenshots.ย 

The agent’s view during a callย 

Agent console during a live call ยท illustrative mockup

Agent console during a live callย ย 

The agent controls the call from the Omni-Channel widget while the transcript, case and recommendations stay on the same screen.ย 

The admin’s view in Setupย 

Contact center setup ยท illustrative mockup (1)

Contact center setupย ย 

Admins add reps to a contact center and assign each phone channel an Omni-Channel flow for routing. For Salesforce’s own screenshots, see the Open CTI to Voice Migration Trailhead module.ย 

An incoming callย 

Incoming call in the Omni-Channel utility ยท illustrative mockup

Incoming call in the Omni-Channel utilityย ย 

The call rings inside the Omni-Channel utility at the bottom of the console, with the caller and queue shown before the rep accepts. There is no separate softphone window to manage.ย 

The Voice Call record after the callย 

Incoming call in the Omni-Channel utility ยท illustrative mockup

Voice Call record after the callย ย 

Unlike an Open CTI Task, the VoiceCall record holds the recording, the full transcript, duration and the linked case, so reports and AI can use it.

The supervisor’s viewย 

Incoming call in the Omni-Channel utility ยท illustrative mockup

Supervisor view of live calls and chats ยท illustrative mockupย 

With Open CTI, calls sit in a silo. With Voice, supervisors monitor several calls at once alongside chats, email and messaging, and manage queues and capacity in one place.ย 

What SCV offers todayย 

All four Voice paths unlock capabilities that Open CTI cannot offer. Some features depend on your path and licenses, so confirm each one for your setup.

Areaย 

Featureย 

What it doesย 

Agent experienceย 

Unified phone experienceย 

Calls arrive in the same Omni-Channel widget reps use for digital channelsย 

Agent experienceย 

VoiceCall recordsย 

Call data lands on a core Salesforce object, with recording links, duration and multiparty legsย 

AI assistย 

Real-time transcription and recordingsย 

Built into the console during and after the callย 

AI assistย 

Next best actionsย 

Recommendations surface during live callsย 

AI assistย 

Conversation Catch-Upย 

Gives reps full context when they join a callย 

AI assistย 

Automatic case wrap-upย 

Case wrap-up happens after the call endsย 

AI voice agentsย 

Agentforce Voice handoffย 

AI agents and reps share full conversation context, so customers don’t repeat themselvesย 

Routingย 

Omni-Channel flows for voiceย 

Route calls by queue, skill, rep or bot, and handle screen pops declarativelyย 

Routingย 

Route a Voice Call API (Spring ’26)ย 

Added to the Telephony Integration API for Salesforce-first routingย 

Routingย 

Route Agentforce Voice calls using SIP (Spring ’26)ย 

Sends Agentforce Voice calls over SIPย 

Supervisorย 

Cross-channel visibilityย 

Monitor multiple calls alongside chats, email and messaging; manage queues and capacityย 

AI voice agentsย 

Autonomous scheduling with Agentforce Voice (Winter ’27)ย 

Voice agents check real-time availability and book the right technicianย 

Platformย 

Contact Center in 30+ countries (Winter ’27)ย 

CRM, channels and AI together for global contact centersย 

Workforceย 

Hybrid workforce in WEM (Winter ’27)ย 

Manage and train employees and AI agents from one placeย 

Migration roadmapย 

Start with an inventory, not a platform choice. Salesforce’s example plan takes about eight weeks per contact center, with a parallel run on real call volume before cutover (Trailhead: Plan Your Migration).ย 

Keep the Open CTI package installed through cutover. If something goes wrong, reps can be moved back to the Open CTI call center in 15 to 30 minutes with no data loss. Your project’s pace may differ, and several orgs or call centers mean several runs of this plan.ย 

Setup walkthrough and screenshots to captureย 

Real screenshots should come from your own sandbox, so readers see your setup and nothing confidential. Menu names shift between releases, so check each path against Salesforce Help: Migrate from Open CTI before publishing.ย 

High-level setup stepsย 

  • Inventory today’s setup in Setup > Call Centers: every user, phone number, report and piece of custom logic tied to Open CTI.ย 
  • Install your vendor’s Partner Contact Center package from AgentExchange, or turn on Voice, depending on your path.ย 
  • Set up the contact center, then Omni-Channel: service channels, queues and presence statuses.ย 
  • Add reps to the contact center. When you add them, they are removed from the old Open CTI call center automatically.ย 
  • Build an Omni-Channel flow for routing and screen pops and assign it to the phone channel.ย 
  • Rebuild reports and dashboards on the VoiceCall object instead of the Task object.ย 
  • Validate in a sandbox, run in parallel with real volume, then cut over.ย 

Screenshot checklistย 

s.no.

Screenshotย 

Where to capture itย 

What it shows readersย 

1ย 

Existing call centersย 

Setup > Call Centersย 

The Open CTI footprint that must moveย 

2ย 

Vendor package listingย 

AgentExchange (formerly AppExchange)ย 

Partner Contact Center is a supported pathย 

3ย 

Voice setup pageย 

Setup > Voice Setupย 

Where Voice is switched onย 

4ย 

Contact center detailย 

Setup > Contact Centersย 

Contact Center Users and Contact Center Channelsย 

5ย 

Omni-Channel flowย 

Flow Builder, Omni-Channel flowย 

Routing and screen-pop logicย 

6ย 

Softphones with incoming callย 

Service Console, Omni-Channel widgetย 

The native agent experienceย 

7ย 

Live transcript and recommendationsย 

Voice Call record during a test callย 

Real-time AI assistย 

8ย 

VoiceCall record after the callย 

Voice Call record pageย 

Recording, duration and linked caseย 

9ย 

Rebuilt reportย 

Reports, VoiceCall report typeย 

Richer call data than Task-based reportsย 

10ย 

Supervisor viewย 

Omni-Channel supervisorย 

Calls monitored alongside digital workย 

Before posting, blur names, phone numbers, org IDs and customer data in every screenshot.ย 

Common Open CTI Migration Challenges and How to Avoid Themย 

Organizations may encounter technical and operational challenges during migration. Addressing these issues early can help minimize downtime and implementation of risks.ย 

Migration Challengeย 

Recommended Approachย 

Phone Number Portingย 

Initiate porting requests early, as the process may take several weeks.ย 

Existing CTI Customizationsย 

Identify and rebuild custom routing and screen-pop logic using Omni-Channel Flows.ย 

ย 

Task-Based Reportingย 

Recreate relevant reports using the VoiceCall object.ย 

Agent Availabilityย 

Use separate agent groups for parallel testing where required.ย 

ย 

Incomplete Testingย 

Validate the solution using real call volumes, not only simulated calls.ย 

ย 

Premature Package Removalย 

Keep the Open CTI package installed until the new implementation is stable.ย 

ย 

Conclusionย 

The retirement of Salesforce Open CTI is an important technology transition for organizations that rely on integrated telephony and CRM operations. With the February 2028 deadline approaching, businesses should begin evaluating their existing infrastructure and selecting an appropriate Salesforce Voice migration path.ย 

Beyond meeting the retirement deadline, this transition offers an opportunity to modernize contact center operations through unified call management, intelligent routing, real-time transcription, AI assistance, and improved reporting.ย 

A structured migration strategy, supported by technical expertise and thorough testing, can help organizations minimize disruption while preparing their customer service operations for the future.ย 

Looking to migrate from Open CTI to Salesforce Voice?ย Cloud Analogyย helps businesses implement, integrate, and optimize Salesforce solutions to support evolving customer service requirements. Connect with our Salesforce experts to evaluate your existing CTI environment and plan a smooth transition to Salesforce Voice.ย 

Frequently Asked Questions (FAQs)

Salesforce will fully retire Open CTI on February 28, 2028. After this date, its API and associated integration components will stop working.ย 

No. Since February 16, 2026, Open CTI has been unavailable for newly created Agentforce Service organizations.ย 

No. Organizations can continue using their existing telephony providers if a supported Partner Contact Center package is available on AgentExchange.ย 

Yes. Salesforce Voice is the updated name for Service Cloud Voice. Some related migration solutions have also been renamed, including Partner Contact Center.ย 

A rollback may be possible during cutover if the existing Open CTI setup remains installed and operational. Salesforce’s migration guidance describes moving representatives back to the previous call center in approximately 15โ€“30 minutes.ย 

Salesforce’s example migration plan takes approximately eight weeks per contact center. The actual timeline depends on the number of integrations, phone numbers, customizations, and testing requirements.ย 

salesforce development services
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.