Five9 and Service Cloud Voice: inbound in Salesforce, and the dialer question
Service Cloud Voice is Salesforce's integration layer for telephony, and Five9 can be the telephony underneath it. For most service teams the question is not Five9 or Salesforce. It is how much outbound you run, and whether that keeps Five9 in place or lets you consolidate.
The pieces, defined
Service Cloud Voice is the integration of a telephony system with Salesforce. It is not a competing phone system. The telephony underneath it can be Amazon Connect, bundled by Salesforce, or a partner contact center platform connected through Salesforce's partner telephony framework. Either way, agents answer in the Service Console, calls become Voice Call records on the customer's timeline, transcripts feed Agentforce, and presence is shared with digital work in Omni-Channel.
Five9 is a cloud contact center platform known for its dialer and outbound campaign tooling as well as inbound routing. With Salesforce it can run as the partner telephony under Service Cloud Voice, as a standalone platform through the Five9 Adapter for Salesforce, or be replaced by Amazon Connect under Service Cloud Voice or by Agentforce Contact Center.
Four ways to run Five9 with Salesforce
| Option | Where agents work | What you keep | Best when |
|---|---|---|---|
| Five9 as partner telephony under Service Cloud Voice | Service Console, with Five9 telephony embedded | Five9 routing, recording and the dialer | Inbound belongs in Salesforce and real campaigns still need Five9 |
| Five9 standalone with the Salesforce adapter | Five9 desktop or an adapter widget in Salesforce | Everything Five9, lighter Salesforce integration | Outbound throughput is the core job and Salesforce is the CRM behind it |
| Replace Five9 with Amazon Connect under Service Cloud Voice | Service Console only | Salesforce, plus Amazon Connect flows | Outbound is light and click-to-dial plus callbacks cover it |
| Agentforce Contact Center | Service Console only | Salesforce, native telephony and Agentforce Voice agents | Service-led team that wants one vendor and AI-first phone handling |
The dialer decides it. Service Cloud Voice handles outbound calls, click-to-dial and scheduled callbacks from the console well. Predictive and progressive campaign dialing at scale, with list management and campaign compliance, is what Five9 is built for. If you need that, Five9 stays, and partner telephony is how your inbound agents still get one console.
How I frame the decision
- Service-led team, light outbound. Consolidate: Service Cloud Voice with Amazon Connect, or Agentforce Contact Center. Agents get one console and one vendor fewer.
- Blended team with real campaigns. Five9 as partner telephony under Service Cloud Voice. The dialer stays, inbound lands in Salesforce, and you decide later whether the dialer still earns its keep.
- Outbound floor first, service second. Five9 standalone with the adapter. Service Cloud Voice is the wrong layer when the core job is campaign throughput.
- The IVR, in every option that includes Service Cloud Voice. Replace the inbound menu tree with an Agentforce Voice agent that resolves calls end to end and hands off into the console only when a person is needed.
What changes in each option
Partner telephony changes the inbound agent desktop and leaves telephony and campaigns where they are, so the work is console design, presence alignment between the dialer and Omni-Channel, transcript streaming, reporting across both systems and training. Consolidating is a CCaaS migration, and the outbound side needs its own decision first: what replaces the dialer, or whether Five9 stays for campaigns only.
What to verify in a scripted demo
Vendor capabilities change every quarter, so treat this page as a way to decide, not a feature matrix. Run the same script on each option, with your own call types, and make the outbound steps count:
- Load a real campaign list. Watch how a progressive or predictive campaign is set up, paced and paused, and what the agent sees between connects.
- An identified customer calls in during a campaign. Does the inbound call interrupt the dialer cleanly, and where does the agent land in Salesforce?
- A call and a chat arrive for the same skill. Which system decides who gets what, and can a supervisor see both in one place?
- Record a consent change and a do-not-call request mid-call. Where does it land, and how fast does the dialer honor it?
- Turn on an Agentforce Voice agent for one inbound intent. How is it grounded, and how does it hand off into the console?
Frequently asked questions
Is Service Cloud Voice an alternative to Five9?
No. Service Cloud Voice is Salesforce's integration layer for telephony, and Five9 can run underneath it as partner telephony. The choice is how to run Five9 with Salesforce, and whether outbound volume justifies keeping it.
Does Service Cloud Voice do outbound calling?
It supports outbound calls, click-to-dial and scheduled callbacks from the console. Predictive and progressive campaign dialing at scale, with list management and campaign compliance, is where a dedicated dialer like Five9 is built to be stronger.
Can Agentforce Voice agents work with Five9 underneath?
Yes. With Five9 as partner telephony under Service Cloud Voice, I expose Agentforce Voice agents on the inbound phone channel. The agent takes the call, answers, decides, takes action in your systems and resolves most service calls without a human, handing off to agents in the console when needed.
We are mostly inbound. Should we keep Five9?
Often not. If outbound is a small share of volume and agents already work in Salesforce, consolidating onto Amazon Connect under Service Cloud Voice or onto Agentforce Contact Center is usually the simpler estate. The demo script on this page shows the difference quickly.
How long does each option take?
Partner telephony typically stands up in six to twelve weeks. Consolidating is a migration of three to six months for a single site, longer if the dialer is being replaced rather than kept.
Go deeper
Let's talk for 30 minutes.
Tell me where your contact center or Salesforce is stuck. If I can help, we'll map out what's possible. If I can't, I'll tell you that too. It's free either way.
Book a call