Contact Centre · Five9 · Salesforce Voice

7 Ways Salesforce and Five9 Integration Transforms Call Centre Efficiency

A practical, updated guide to the Salesforce Five9 integration: the seven places it removes wasted agent time, the two ways to connect the platforms, what the February 2028 Open CTI retirement means for your adapter, and how to plan the build.

Key Takeaways

  • The Salesforce Five9 integration puts Five9's telephony, routing, dialer and AI inside the Salesforce console, so agents stop switching screens and every call lands on the right customer record automatically.
  • The seven efficiency gains are: screen pop with context, click-to-dial and campaign dialing, automatic call logging and dispositions, unified routing and presence, Flow automation off the call, AI assist and summaries, and reporting with built-in compliance controls.
  • There are two integrations: the classic Five9 Plus Adapter for Salesforce (built on Open CTI) and Five9 Fusion for Salesforce (built on Salesforce Voice with partner telephony, formerly Service Cloud Voice BYOT).
  • Salesforce will retire Open CTI on 28 February 2028, and existing Open CTI integrations stop working after that date. Teams on the classic adapter should plan their move to Salesforce Voice now.
  • Efficiency only shows up if you measure it: baseline average handle time, after-call work, first contact resolution and right-party contacts before go-live, then compare.

Every second an agent spends hunting for a customer record, retyping a phone number or writing call notes is a second the customer waits. The Salesforce Five9 integration removes most of that work by joining Five9, the cloud contact centre platform that handles calls, routing and dialing, with Salesforce, the CRM that holds the customer's history, cases and opportunities. Five9 describes the partnership as more than 15 years old, with over 1,000 joint customers and more than 160,000 agents using the two platforms together every day (Five9, September 2026).

This guide is written for operations, service and IT leaders at growing and mid-market companies, and the enterprise teams that run larger contact centres, who want to know exactly where the efficiency comes from, which integration to use, and what to plan for before the Open CTI retirement. Every product capability below comes from Five9 or Salesforce documentation, linked inline.

Section 01 · Quick Answer

What Does a Salesforce Five9 Integration Actually Do?

A Salesforce Five9 integration embeds Five9's softphone, call controls, routing and dialer inside Salesforce. Inbound calls open the matching customer record, outbound calls start with one click, and each call is logged against the right record with its disposition, so agents work in one screen and supervisors report from one source.

The rest is detail about how deeply the two platforms share data, and that depends on which integration you install. Use this as a quick fit check.

The integration pays off when your agents already live in Salesforce for cases, leads or accounts; you run Five9 for voice (or are choosing it); calls need context from the CRM to be resolved; and leadership wants handle time, outcomes and follow-ups reported in one place.

Think twice if your agents rarely touch Salesforce, call volumes are small enough that a basic dialer covers them, or your Salesforce data is too unreliable for screen pops to find the right record. Fix the data and the process first; an integration amplifies whatever is already there.

Section 02 · Options

The Two Ways to Connect Five9 and Salesforce

Five9 offers two Salesforce integrations. The Five9 Plus Adapter for Salesforce is the classic softphone built on Salesforce Open CTI and logs calls as Tasks. Five9 Fusion for Salesforce plugs Five9 into Salesforce Voice through partner telephony, logs calls on the Voice Call object, and is the path Five9 now promotes.

Salesforce and Five9 logos side by side, representing the Salesforce Five9 integration

Both connect the same two platforms. They differ in the Salesforce framework underneath, where call data is stored, and how far each will go in the future. Five9's Fusion administrator guide notes that an agent cannot run both at the same time, so the choice is one or the other per agent. Five9 describes Fusion as combining its telephony with Salesforce Voice for partner telephony inside the Agentforce Service console (Five9 Fusion data sheet).

AspectFive9 Plus Adapter for SalesforceFive9 Fusion for Salesforce
Salesforce frameworkOpen CTI softphone in Lightning Experience and the Lightning consoleSalesforce Voice with partner telephony (formerly Service Cloud Voice BYOT), inside the Omni-Channel widget
Where calls are loggedSalesforce Task records with Five9 custom fieldsThe Voice Call object, with call variables available to Flow
Screen popFive9 search rules: Salesforce ID, field match, then caller numberNative Salesforce Channel-Object Linking against Contacts, plus Screen Flow searches
OutboundClick-to-dial, Campaign-to-dialing-list sync, call previewClick-to-dial and preview dialing (the modes the Fusion guide documents)
AIFive9 Agent Assist component (added 2026), summary written to the TaskFive9 Agent Assist, or Einstein for Service fed by Five9 TranscriptStream; AI Agent summaries passed to the human agent
Salesforce licensingWorks with your Sales or Service Cloud usersRequires Salesforce Voice licences
FutureDepends on Open CTI, which retires on 28 February 2028Five9's stated path forward; built on the framework Salesforce recommends

Sources: Five9 Plus Adapter administrator guide, Five9 Fusion AppExchange listing and the Fusion administrator guide (October 2026). Confirm features against the version you install.

Section 03 · Deadline

Open CTI Retires in February 2028: What It Means for Your Five9 Adapter

Salesforce has scheduled Open CTI for retirement on 28 February 2028, and existing Open CTI implementations stop working after that date. The classic Five9 Plus Adapter runs on Open CTI, so contact centres using it need to move to Salesforce Voice with partner telephony, which for Five9 means Five9 Fusion for Salesforce.

Salesforce's guidance is to start now: inventory your Open CTI integrations, map them to Salesforce Voice features, and finish the move well before the date (Salesforce Help: Open CTI retirement). Five9 makes the same point, describing Open CTI as "the framework behind the classic Five9 adapter that more than 1,000 joint customers rely on today" and positioning Fusion as the way forward (Five9).

The move is more than a package swap. Calls stop being Tasks and become Voice Call records, so every report, dashboard, Flow and validation rule that reads call Tasks has to be rebuilt. Screen pop logic moves from Five9's search rules to Salesforce's Omni-Channel and Channel-Object Linking. Agents need Salesforce Voice licences. Treated as a project with a timeline, it is also the moment to fix the call data model properly instead of carrying old shortcuts forward.

Section 04 · Overview

The 7 Ways the Integration Improves Call Centre Efficiency

Each of the seven targets a specific kind of wasted time. The next section explains how each one works and which metric it moves.

1. Screen pop with context

The caller's record opens as the call connects, including records found from IVR input such as an account or case number.

2. Click-to-dial and campaign dialing

One click dials any Salesforce number; Salesforce Campaigns feed Five9 dialing lists.

3. Automatic logging and dispositions

Every call is written to the right record with timing, campaign and outcome, without manual notes.

4. Unified routing and presence

Five9 and Omni-Channel share agent status, so nobody is offered a case while on a call.

5. Flow automation off the call

Call data opens guided Flows and triggers follow-ups, callbacks and case updates.

6. AI assist and summaries

Live transcription, next-best-action guidance and automatic call summaries cut after-call work.

7. Reporting and compliance

Call metrics sit beside CRM outcomes, and TCPA and Do Not Call controls are enforced in the softphone.

Section 05 · Deep Dive

The 7 Ways in Depth: How Each One Saves Agent Time

1. Screen Pop That Finds the Right Record

Inbound

Moves: average handle time and first contact resolution.

Without an integration, the opening of many calls goes to asking "can I take your account number?" and searching. With the Plus Adapter, Five9 searches Salesforce in a set order: a Salesforce record ID passed with the call, then a specific field value, then the caller's number. A single match opens the record automatically (Five9 search rules).

The bigger gain comes from the IVR. A Five9 IVR script can ask the caller for an account or case number, validate it against Salesforce, and pass it to the agent's screen, so the exact case is open before the agent says hello (Five9 IVR data capture). In Fusion, screen pop uses Salesforce's native Channel-Object Linking, and Five9 call-attached variables can drive Screen Flow searches across any object.

2. Click-to-Dial and Campaign-Driven Outbound

Outbound

Moves: dials per agent hour, misdials and list hygiene.

Agents click the phone icon beside any number in Salesforce to dial through Five9, and the right Five9 campaign can be selected automatically from a field on the record (Five9 click-to-dial). That removes retyping, wrong numbers and calls reported against the wrong campaign.

For outbound teams, the Plus Adapter syncs Salesforce Campaign members to a Five9 dialing list as records are added, changed or removed, so sales and marketing build the list in Salesforce and the dialer always works from the current version (Five9 list synchronisation). In preview campaigns, the agent sees the contact's details before the call is placed, which helps on complex or high-value calls.

3. Automatic Call Logging and Dispositions

Wrap-Up

Moves: after-call work and data completeness.

Manual call notes are the most common source of missing activity history. The Plus Adapter logs each call as a Salesforce Task that appears in Activity History, with Five9 fields such as call type, campaign, handle time, talk and hold time, wrap time and session ID (Five9 custom fields). Fusion writes the same kind of data, such as agent ID and name plus any custom variables, to the Voice Call record.

At the end of each call the agent picks a disposition, such as Scheduled Callback, Agent to Redial or Add to DNC, and the system sets some automatically, such as No Answer or Busy (Five9 dispositions). Keep the disposition list short and mirror it in Salesforce, because dispositions are what the automation in way 5 runs on.

4. One Routing Brain and One Agent Status

Routing

Moves: occupancy, transfers and abandoned work.

When voice runs in Five9 and chats, emails and cases run in Salesforce Omni-Channel, two systems can assign work to the same agent at the same time. Federated routing solves this. Agent presence syncs in both directions, and while an agent is on a Five9 call, Salesforce stops routing them new text work, and the reverse (Five9 federated routing).

On the voice side, Five9's Intelligent Voice Routing directs each call to the most suitable AI or human agent using real-time information about the interaction (Five9 Fusion announcement). CRM data, such as customer tier or an open priority case, can be passed into routing so the right skill gets the call the first time.

5. Flow Automation That Starts From the Call

Automation

Moves: follow-up leakage and process consistency.

Five9 can open a Salesforce Lightning Flow in the context of a call, pre-filled with call data, which turns a complex call type such as a claim, a renewal or a cancellation into a guided script (Five9 Lightning Flows). In Fusion, call variables passed at the start of a call are available to downstream Flow automation.

After the call, record-triggered Flows act on the logged call and its disposition: create a follow-up case when the outcome is "needs escalation", schedule a callback task, update the opportunity stage, or send a survey. This is where the integration stops being a phone in the browser and starts removing work the agent would otherwise do by hand.

6. AI Assist, Transcription and Call Summaries

AI

Moves: after-call work, ramp time for new agents and repeat explanations.

Five9 TranscriptStream transcribes the call in real time and streams it into Salesforce, where it grounds Einstein for Service features: Next Best Actions, Reply Recommendations and Call Summaries. Organisations that prefer Five9's own AI can run Five9 AI Agent Assist instead, which gives live guidance and automated summaries inside the console (Five9). In the Plus Adapter, the Agent Assist summary is written to the call Task.

Self-service benefits too. When a Five9 AI Agent handles the first part of a call and then transfers it, the conversation summary passes into the Salesforce Voice Call record, so the customer does not repeat themselves. On Agentforce, Salesforce lists Five9 among the contact centre platforms compatible with Salesforce Voice (Salesforce, October 2025), and Five9 lists deeper Agentforce integrations on its roadmap.

7. Reporting and Compliance in One Place

Governance

Moves: supervisor time, QA coverage and compliance risk.

Once calls are records in Salesforce, call metrics can be reported next to business outcomes: cases closed, renewals saved, meetings booked. Five9 can also import report batches into Salesforce as Tasks, including dialer calls that never reached an agent. Five9 recommends using either Task logging or report imports, not both, to avoid duplicates (Five9 reports). On Fusion, Voice Call is the reporting object, and Omni-Channel statuses can be mapped to Five9 reason codes so supervisors see the same states in both systems.

For outbound compliance, the adapter can enforce TCPA Manual Touch Mode, which requires agents to dial every number by hand and disables click-to-dial and auto-dial for those campaigns, and lets permitted agents add numbers to the contact centre's internal Do Not Call list (Five9 TCPA Manual Touch Mode). These are controls, not legal advice: confirm your obligations with counsel.

Section 06 · Architecture

How an Inbound Call Flows Between Five9 and Salesforce

On an integrated inbound call, Five9 answers and routes the call, Salesforce supplies the customer context, and the outcome is written back to Salesforce. The sequence below shows the Fusion path; the Plus Adapter follows the same steps but logs a Task instead of a Voice Call.

1. The customer calls and reaches the Five9 IVR or a Five9 AI Agent.
It can capture an account or case number, or resolve simple requests in self-service.
2. Five9 routes the call to the best available agent.
Routing uses skills, real-time context and any CRM data passed into Five9; presence is shared with Omni-Channel.
3. The call arrives in the Salesforce console and the record pops.
The caller's number or IVR input finds the Contact, account or case; a Flow can open for guided handling.
4. The agent handles the call with live assistance.
TranscriptStream feeds Einstein for Service, or Five9 Agent Assist gives guidance; any AI Agent summary is already on the record.
5. The call ends and the outcome is logged.
Call data, disposition and summary are written to the Voice Call record; recordings can be played back in Salesforce.
6. Salesforce automation takes over.
Record-triggered Flows create follow-up cases, callbacks or surveys from the disposition; dashboards update.
Section 07 · Measurement

Which Call Centre Metrics Should Improve, and How to Prove It

Measure five metrics before and after go-live: average handle time, after-call work, first contact resolution, transfer rate and, for outbound teams, right-party contacts per agent hour. Take a four-week baseline from Five9 reports, then compare the same call types after launch, so the gain is proven rather than assumed.

MetricWhat moves itWhere to measure
Average handle timeScreen pop, IVR data capture, guided FlowsFive9 reports, by call type
After-call workAutomatic logging, dispositions, AI summariesFive9 wrap time; Salesforce call record fields
First contact resolutionContext on screen, skill-based routing, AI guidanceSalesforce: repeat calls or reopened cases within 7 days
Transfer rateRouting with CRM data, AI Agent handoff summariesFive9 call details
Right-party contacts per hourClick-to-dial, Campaign list sync, clean numbersFive9 campaign reports joined to Salesforce outcomes
Follow-up completionDisposition-driven FlowsSalesforce tasks and cases created vs closed on time

Compare like with like: the same queues, call types and season. A drop in handle time that comes with a rise in repeat calls is not an efficiency gain, which is why first contact resolution belongs on the same dashboard.

Section 08 · Decision

Plus Adapter or Five9 Fusion? A Decision Framework

For a new Five9 and Salesforce deployment in 2026, start on Five9 Fusion for Salesforce, because Salesforce is retiring Open CTI in February 2028. If you already run the Plus Adapter, keep it stable but schedule the move to Fusion, and check first whether your outbound dialing modes and languages are supported.

1. Are you deploying Five9 with Salesforce for the first time?
→ Start on Five9 Fusion for Salesforce. Building new on Open CTI means migrating again before 2028.
2. Are you on the Plus Adapter today?
→ Plan the migration now: inventory Task-based reports, Flows and integrations, and budget for Salesforce Voice licences.
3. Do you depend on automated outbound dialing modes from inside Salesforce?
→ Confirm with Five9 which modes your Fusion version supports; its admin guide documents preview dialing.
4. Do agents need the console in a language other than English or Spanish?
→ Check Fusion's language support before committing; the October 2026 guide lists English and Spanish for the interface.
5. Are you standardising on Agentforce and Einstein for Service?
→ Fusion is the route: TranscriptStream feeds Einstein, and Salesforce Voice is where Salesforce is investing.
Section 09 · Pitfalls

Implementation Pitfalls Most Guides Skip

These come straight from Five9 and Salesforce documentation, and each one has caught out real projects.

1. Task-based reports break on migration. Fusion logs calls on Voice Call records, not Tasks. Every report, dashboard and Flow that reads call Tasks must be rebuilt.
2. Deprecated Task fields. From Plus Adapter package v2.44, most Five9 Task custom fields are deprecated. Five9 recommends full user acceptance testing in a sandbox, and in-place downgrades are not supported.
3. No side-by-side adapters per agent. An agent cannot run the Plus Adapter and Fusion at the same time, so plan the cut-over by team, not by individual.
4. Recording retention. In Fusion, recordings play inside Salesforce but are retained by Five9 for 30 days. Decide where long-term recordings and transcripts live before go-live.
5. Duplicate call records. Logging calls as Tasks and importing Five9 report batches creates duplicates. Five9 advises choosing one.
Section 10 · Implementation

A Practical Implementation Plan

A Five9 and Salesforce integration goes best in five stages: discovery and baseline, data and call model design, sandbox build, pilot with one team, then phased rollout. Most of the risk sits in the first two stages, because screen pops, logging and automation are only as good as the records and dispositions behind them.

  1. 1

    Discovery and baseline. Map call types, queues, IVR paths and the Salesforce objects each one touches. Pull four weeks of handle time, after-call work and transfer data.

  2. 2

    Data and call model. Clean phone formats and duplicates so screen pops find one record. Agree the disposition list and the follow-up each disposition triggers.

  3. 3

    Sandbox build. Install the package, set up Salesforce Voice with partner telephony (Salesforce setup guide), configure screen pop, routing, presence mapping, Flows and reports, and test with real call scenarios.

  4. 4

    Pilot. Go live with one team for two to four weeks, watch the metrics daily, and fix friction before it spreads.

  5. 5

    Rollout and optimisation. Move the remaining teams in waves, then add AI assist, summaries and deeper automation once the basics are stable.

Section 11 · Partner

How Twopir Consulting Helps With Five9 and Salesforce

We implement, rescue, optimize, and integrate complex CRM and revenue systems. For contact centres, that means designing the Salesforce side of a Five9 deployment, from the data model and screen pop rules to routing, dispositions, Flow automation and reporting, and connecting it with the rest of your stack. See our Five9 Adapter for Salesforce services, our Salesforce Service Cloud solutions and our wider integration services.

We work with growing, mid-market, and enterprise organizations, and many of them are facing the Open CTI retirement now. Whether you are installing Five9 for the first time, moving from the Plus Adapter to Fusion, or rescuing an integration whose call data nobody trusts, we start with your call types and the outcomes you need to report, then build backwards.

Ready to Start

Plan Your Five9 and Salesforce Integration With an Architect

In a 30-minute discovery call, a Twopir Salesforce architect will review your current Five9 setup and call flows, flag what the Open CTI retirement means for you, and outline the shortest path to measurable efficiency gains.

Schedule a Discovery Call
Section 12 · Bottom Line

The Bottom Line

The Salesforce Five9 integration earns its keep by removing small, repeated losses: the search at the start of each call, the retyped number, the missing note, the follow-up that never happens. Add those up across every agent and every shift and they become the efficiency gain. With Open CTI retiring in February 2028, the build you choose now should be on Salesforce Voice.

  1. 1

    Screen pop, click-to-dial and automatic logging cut handle time and after-call work from the first day.

  2. 2

    Shared presence, Flow automation and AI summaries remove the hand-offs and follow-ups that leak time and revenue.

  3. 3

    New deployments should start on Five9 Fusion for Salesforce; Plus Adapter users should schedule their migration before 28 February 2028.

  4. 4

    Baseline your metrics before go-live, so you can prove the result.


FAQ

Frequently Asked Questions

Yes. Five9 offers two Salesforce integrations: the Five9 Plus Adapter for Salesforce, a softphone built on Salesforce Open CTI, and Five9 Fusion for Salesforce, which connects Five9 to Salesforce Voice through partner telephony. Both give agents call controls, screen pop and call logging inside Salesforce.

The Plus Adapter runs on Open CTI and logs calls as Salesforce Tasks. Fusion runs on Salesforce Voice with partner telephony, logs calls on the Voice Call object, uses Omni-Channel for screen pop and presence, and can feed Einstein for Service through Five9 TranscriptStream. Fusion requires Salesforce Voice licences, and an agent cannot use both at once.

Salesforce has scheduled Open CTI for retirement on 28 February 2028, and existing Open CTI integrations stop working after that date. Because the classic Five9 Plus Adapter is built on Open CTI, teams using it should plan a move to Five9 Fusion for Salesforce on Salesforce Voice well before the deadline.

Yes. The Plus Adapter writes each call to a Salesforce Task with Five9 fields such as call type, campaign, handle time and wrap time, plus the agent's disposition. Fusion logs call data to the Voice Call record, where recordings can be played back and call variables can drive Flow automation.

Five9 TranscriptStream streams live call transcripts into Salesforce to ground Einstein for Service features such as Next Best Actions, Reply Recommendations and Call Summaries. Salesforce lists Five9 among the contact centre platforms compatible with Salesforce Voice, and Five9 has listed deeper Agentforce integrations on its roadmap.

Five9's October 2026 Fusion guide lists Professional, Enterprise, Unlimited, Developer and Performance editions, on Sales Cloud or Service Cloud. You need Salesforce Voice licences for admins and agents, plus a Five9 domain enabled for Fusion. Confirm current requirements with Five9 and Salesforce before you budget.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We design and build Salesforce and HubSpot solutions, including contact centre integrations such as Five9, for clients in the US, UK, Australia, the UAE and Canada.