Genesys Cloud and Service Cloud Voice: how they fit together
Service Cloud Voice is not an alternative to Genesys Cloud. It is Salesforce's integration layer for telephony, and Genesys Cloud can be the telephony underneath it. The real decision is which of four ways to run Genesys with Salesforce fits your operation, and whether to consolidate later.
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.
Genesys Cloud is a contact center platform with its own routing, IVR, agent desktop, workforce engagement and analytics. With Salesforce it can run three ways: as the partner telephony under Service Cloud Voice, as a standalone platform connected through the Genesys Cloud for Salesforce CTI adapter, or not at all, replaced by Amazon Connect under Service Cloud Voice or by Agentforce Contact Center, Salesforce's newer native option.
Four ways to run Genesys Cloud with Salesforce
| Option | Where agents work | What you keep | Best when |
|---|---|---|---|
| Genesys as partner telephony under Service Cloud Voice | Service Console, with the Genesys softphone embedded | Genesys routing, IVR, recording, workforce engagement | Agents live in Salesforce, Genesys does more than route calls, and the contract has time left |
| Genesys standalone with the CTI adapter | Genesys desktop or a CTI widget in Salesforce, with screen pop | Everything Genesys, lighter Salesforce integration | Salesforce is one of several systems the contact center serves |
| Replace Genesys with Amazon Connect under Service Cloud Voice | Service Console only | Salesforce, plus Amazon Connect flows | Genesys is mostly a phone switch for a Salesforce team and the renewal is near |
| Agentforce Contact Center | Service Console only | Salesforce, native telephony and Agentforce Voice agents | You want one vendor and the phone channel built around AI agents from the start |
The first two keep Genesys. The second two retire it. Partner telephony is usually the right first step for a team already on Genesys, because agents move into one console without a telephony migration, and Agentforce Voice agents can go on the phone line through it.
How I frame the decision
- Where do agents spend the day? If it is Salesforce, the desktop should be the Service Console, which means partner telephony or a native option, not the CTI adapter alone.
- How much of Genesys is actually used? Workforce engagement, complex multi-site routing and outsourcer management argue for keeping it underneath. A phone switch with a recorder does not.
- When does the contract renew? Partner telephony buys time to decide. A renewal within a year makes consolidation worth modeling now.
- What is the plan for the IVR? In any option where Service Cloud Voice is in place, the menu tree can be replaced by an Agentforce Voice agent that takes the call, answers, decides, takes action and resolves it, handing off only what needs a person. That is where the value is, and it works with Genesys underneath.
What changes in each option
With partner telephony, the agent desktop changes and the telephony does not, so the work is console design, presence and routing alignment, transcript streaming, reporting across both systems, and training. Consolidating onto Amazon Connect or Agentforce Contact Center is a full CCaaS migration: IVR redesign, number porting, recording retention, parity for workforce and quality processes, in waves by queue.
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 you are considering, with your own call types:
- An identified customer calls about an open case. Where does the agent land, and how many clicks to the case?
- A call and a chat arrive for the same skill. Which system decides who gets what, and can one supervisor see both?
- Set an agent to a break in one system. Does the other system know?
- Turn on an Agentforce Voice agent for one routine intent. How is it grounded, and how does it hand off into the console?
- Pull the after-call summary, the transcript and the recording. Where does each live, and who can report on them?
Frequently asked questions
Is Service Cloud Voice an alternative to Genesys Cloud?
No. Service Cloud Voice is Salesforce's integration layer for telephony. Genesys Cloud can be the telephony underneath it through partner telephony, so the choice is how to run Genesys with Salesforce, not whether to pick one or the other.
What is the difference between the Genesys CTI adapter and partner telephony?
The CTI adapter connects a standalone Genesys Cloud to Salesforce for screen pop and click-to-dial; agents may still work in the Genesys desktop. Partner telephony puts Genesys underneath Service Cloud Voice, so agents work in the Service Console, calls become Voice Call records, and transcripts and presence flow into Salesforce.
Can Agentforce Voice agents work with Genesys underneath?
Yes. With Genesys as partner telephony under Service Cloud Voice, I expose Agentforce Voice agents on the phone channel. The agent takes the call, uses the customer's Salesforce context, answers, decides and acts, resolving most service calls without a human, and hands off to an agent in the console with the transcript when needed.
When does consolidating onto Amazon Connect or Agentforce Contact Center make sense?
When Genesys is mostly a phone switch for a team that already works in Salesforce, when the renewal is close, or when you want one vendor and the phone channel built around AI agents. I model it with contract dates and volumes rather than list prices.
How long does each option take?
Partner telephony typically stands up in six to twelve weeks because the telephony stays put. Consolidating onto Amazon Connect or Agentforce Contact Center is a migration measured in three to six months for a single site, paced by porting and reporting parity.
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