Salesforce Open CTI Retirement: Plan Your Telephony Strategy

Salesforce has officially announced the end-of-life for its Open CTI JavaScript framework, with the retirement date set for February 28, 2028. Open CTI has served as the foundation for softphone integrations within Salesforce since 2012. It's important to note that Open CTI is already unavailable for new Agentforce Service orgs. While the deadline may seem distant, organizations relying on embedded telephony functionalities, such as click-to-dial, screen pops, call logging, and in-console calling via an Open CTI adapter, must begin planning their transition immediately.

This decision impacts more than just the telephony system; it requires a comprehensive review of your Salesforce architecture, licensing model, and provider strategy.

Why Salesforce Teams Should Care

For many organizations, Open CTI has been integral to daily workflows for years. Migrating away can have significant ripple effects:

• Embedded Softphone Behavior: Core functionality within Salesforce.
• Click-to-Dial and Inbound Screen Pops: Key for agent efficiency.
• Task or Activity Logging: Crucial for CRM data integrity.
• Service and Sales Agent Workflows: Direct impact on user productivity.
• Supervisor Visibility: Oversight of calls and CRM activity.
• Custom Telephony-Tied Workflows: Any automation or logic dependent on telephony events.

The primary question is no longer if you use Open CTI, but rather what your post-Open CTI Salesforce telephony strategy will be.

Key Paths for Teams to Evaluate

1. Map Your Open CTI Dependency

Regardless of immediate migration plans, start by identifying:

• Where Open CTI is currently implemented.
• Which teams depend on these functionalities.
• Which business processes will be impacted if Open CTI is removed.

Consider these questions:

• Which telephony provider powers your current adapter?
• How are calls currently logged?
• What logic governs existing screen pops?
• Do sales and service users share the same Open CTI setup, or do their needs differ?

The 2028 date is a hard deadline, not a starting point. Budgeting, roadmap planning, vendor evaluations, integration development, testing, and deployment all require significant lead time.

2. Evaluate Salesforce Voice

Salesforce has designated Salesforce Voice as its strategic direction for telephony integration. This includes options like:

• Amazon Connect integration.
• Bring Your Own Telephony (BYOT) partner models.
• A native voice option integrated with Agentforce Contact Center.

Salesforce Voice offers potential benefits such as a more native Salesforce experience, closer alignment with Omni-Channel and Agentforce, and features like real-time transcription within the Salesforce UI. However, this is not a straightforward replacement. Moving to Salesforce Voice can affect:

• Routing ownership.
• Agent workflows.
• Reporting capabilities.
• Overall channel strategy.
• Licensing requirements.

This transition should be viewed as a strategic shift in your operating model, not merely a softphone system upgrade.

3. Consider a Decoupled API-Based Model

Some telephony providers may not adopt the Salesforce Voice path. Instead, they might offer telephony experiences through:

• Custom Lightning Components.
• Browser extensions.
• External interfaces.

Call data would then be synchronized into Salesforce via APIs and events. This approach can be attractive for reducing dependence on Salesforce Voice licensing and offering providers more flexibility in user experience design. However, it introduces trade-offs:

• Logging Behavior: May differ from native Salesforce Voice.
• Screen Interaction: Potentially less integrated.
• Supervisor Workflows: May require adjustments.
• Reporting: Could be impacted.
• Agent Experience: May not be as seamless as a native solution.

Common Pitfalls to Avoid

1. Assuming Provider Portability

Do not assume your current telephony provider can seamlessly transition you to the next model. A provider with a robust Open CTI adapter might lack a mature Salesforce Voice offering, or only support it in limited capacities. Some may push for a decoupled model that significantly alters the user experience.

2. Underestimating Costs

Open CTI itself did not typically incur separate Salesforce licensing fees. Migrating to Salesforce Voice can introduce new Salesforce costs on top of your existing telephony and CRM expenses. Additional features like AI, analytics, quality management, workforce tools, and premium support can substantially increase the total cost of ownership.

3. Treating it as a Technical Swap

This transition is an architectural decision, not just a technical swap. It influences:

• Where call routing logic resides.
• How voice and digital channels interoperate.
• Presence management strategies.
• Data ingestion into Salesforce.
• Integration of future AI capabilities.

An Open CTI to Salesforce Voice migration is a significant undertaking and should be managed accordingly. In some instances, the retirement of Open CTI may reveal that your current telephony setup has already outgrown your Salesforce architecture.

Navigating Provider Selection

If your current provider is not a suitable long-term partner, evaluating new options can be complex. The primary challenge is often inadequate preparation.

• Lack of Clear Requirements: Without defined requirements, vendors will fill in the gaps with their own narratives. While all providers claim Salesforce integration, the depth and specific workflow support can vary dramatically.
• Misleading Demos: Without a structured evaluation framework, demos often focus on the ideal scenario. Critical, Salesforce-specific workflows and licensing details can remain ambiguous until late in the process.

Lead with requirements, followed by architectural considerations, and then conduct demos.

Why a Salesforce-Focused Advisor Can Help

While most communication vendors are experts in their platforms, they may lack deep Salesforce architecture experience. Independent advisory firms specializing in Salesforce integrations can offer expertise in:

• Defining specific requirements.
• Assessing viable post-Open CTI paths.
• Vetting providers against Salesforce-specific needs.
• Pressure-testing demos.
• Objectively comparing options.
• Negotiating with market context.

Act Before the Deadline Forces the Decision

While the Open CTI retirement is set for February 28, 2028, proactive assessment is crucial. Early evaluation of your current state, provider suitability, licensing implications, and future-state options will provide greater control over the outcome.

Key Takeaways

• Open CTI Retirement: The JavaScript framework for softphone integrations retires on February 28, 2028.
• Impact: Affects click-to-dial, screen pops, call logging, and agent workflows.
• Strategic Decision: Requires an architectural and provider strategy review, not just a technical update.
• Migration Paths: Evaluate moving to Salesforce Voice or adopting a decoupled API-based model.
• Preparation is Key: Map dependencies, define requirements, and avoid common pitfalls like assuming provider portability or underestimating costs.
• Start Now: The 2028 deadline necessitates immediate planning, budgeting, and vendor evaluation.