Service Cloud Voice, implemented by someone who has run the queue
Service Cloud Voice connects a telephony system to Salesforce, so the phone lives next to every case, chat and email. I design and build it end to end: telephony choice, routing, the agent console, transcription, Agentforce Voice agents on the phone line, and the cutover from whatever you run today.
What Service Cloud Voice / Partner Contact Center is
Service Cloud Voice is the integration of a telephony system with Salesforce. The telephony comes from Amazon Connect, bundled by Salesforce, or from a partner contact center platform such as Genesys, NICE CXone, Five9, Talkdesk or Vonage. Either way, calls are routed by Omni-Channel alongside digital work, answered from a softphone inside the Service Console, transcribed in real time, and stored as Voice Call records on the customer's timeline, so the phone stops being a separate system.
It ships in three deployment models. Service Cloud Voice with Amazon Connect bundles the telephony from Salesforce. Service Cloud Voice with Partner Telephony from Amazon Connect lets you bring an Amazon Connect instance you already own. Service Cloud Voice with Partner Telephony connects a certified partner contact center platform such as Genesys, NICE CXone, Five9, Talkdesk or Vonage through Salesforce's partner telephony framework.
Salesforce's newer native option is Agentforce Contact Center, which brings telephony and Agentforce Voice agents into Salesforce without a separate CCaaS platform. I deliver both paths: Service Cloud Voice with partner telephony, and Agentforce Contact Center. Choosing between them is the first and most consequential decision in the program, and it depends on your contracts, your carrier situation, and how much of the IVR you intend to replace with a voice agent rather than rebuild.
When it is the right move
- Agents work in Salesforce but take calls in a separate desktop, and every call means a screen-pop that sometimes works.
- Voice is the one channel missing from Omni-Channel, so supervisors can't balance calls against chats and cases.
- You want transcripts, call summaries and next-best-action driven by what is being said, not typed after the fact.
- An existing CCaaS contract is ending and you would rather consolidate on the platform your service team already lives in.
- You want the phone channel served by an AI agent that resolves calls, not a menu that routes them.
When it is the wrong move
It is not the right move if the operation is an outbound campaign floor first and service second, or if the service team is not on Salesforce yet. A blended team keeps its dialer underneath as partner telephony, which the Five9 guide covers. In the other cases I will say so in the first call.
What I deliver
- Telephony decision and architecture. Amazon Connect, partner telephony or Agentforce Contact Center; number porting plan, carrier and compliance requirements, recording and retention.
- Routing design. With Amazon Connect or Agentforce Contact Center, voice joins Omni-Channel directly, so calls, messaging and cases share one routing model. With partner telephony, the partner routes the calls and I align presence, capacity and reporting so supervisors still see one picture.
- Contact flows. Identification, authentication and routing in Amazon Connect or partner telephony flows: the entry point that hands the call to the voice agent, and the path for the calls that still need a person.
- Agent console. Softphone, screen pop to the right record, call controls, after-call work automation and quick actions that match how agents actually work.
- Transcription and AI. Real-time transcription, Einstein Conversation Insights, call summaries, and Agentforce assist for reps grounded in your knowledge base.
- Agentforce Voice agents instead of the IVR tree. This is not a smarter menu. An AI agent takes the call. Built on Agentforce and exposed on the phone line through Service Cloud Voice with partner telephony or on Agentforce Contact Center, it understands the request, pulls the customer's context from Salesforce, answers questions, makes decisions within the guardrails you set, and takes action in your systems: reschedules, updates, confirmations, requests. It resolves service calls end to end without a human, scales with volume rather than headcount, and hands off to an agent with the full transcript only when judgment or policy requires it. It is built for the bulk of service calls, not only the simple ones.
- Supervisor and reporting. Omni Supervisor, call monitoring, and the dashboards that track the KPIs we agreed on.
- Cutover. Wave plan by queue, parallel running, training, hypercare, and a measured handoff.
How the engagement runs
Typical results
| Metric | Before: on-premise | After: cloud + AI |
|---|---|---|
| Customer satisfaction | 65% | 85%+ |
| Average handle time | 9.2 min | 5.5 min |
| First-contact resolution | 58% | 75%+ |
| Systems on the agent desktop | 7+ | One console + AI |
Typical results across 30+ enterprise programs, comparing operations before transformation with cloud plus AI after. Voice programs usually move handle time first, through screen pop and after-call automation; satisfaction follows as routing and self-service improve. Every engagement sets its own targets up front.
Mistakes I see in Service Cloud Voice projects
- Rebuilding the old IVR tree one to one. New infrastructure with the same menus is a missed decade. The move is the moment to replace the tree with an Agentforce Voice agent that takes the call, decides, acts and resolves it, and routes only what truly needs a person. That is where the phone channel is heading.
- Designing routing for voice alone. With Amazon Connect or Agentforce Contact Center, put voice in the same Omni-Channel model as chats and cases. With partner telephony, line up presence and reporting across both systems, or supervisors still juggle two.
- Leaving transcription on with no plan for it. Transcripts are only valuable when summaries, next-best-action and knowledge suggestions are wired to them.
- Porting numbers late. Carrier lead times are measured in weeks and regularly slip go-lives that were otherwise ready.
Frequently asked questions
What is the difference between Service Cloud Voice with Amazon Connect and partner telephony?
With Amazon Connect, Salesforce bundles the telephony and you build call flows in Amazon Connect. With partner telephony, your existing certified CCaaS platform, such as Genesys, NICE CXone, Five9 or Talkdesk, handles the calls and connects into Service Cloud through Salesforce's partner telephony framework. The first is simpler to own; the second preserves investments you already have.
How long does a Service Cloud Voice implementation take?
A single-site deployment with straightforward routing typically runs eight to sixteen weeks from discovery to first wave go-live. Multi-site programs with complex IVRs, number porting across carriers and compliance recording take longer, and I plan them as waves by queue rather than one cutover.
Do agents still need a separate phone system?
No. The softphone lives in the Service Console. Agents accept calls, see the customer record and prior interactions, and complete after-call work in the same screen as their cases and chats.
Can Agentforce answer calls on Service Cloud Voice?
Yes. I build Agentforce Voice agents and expose them on the phone channel, through Service Cloud Voice with partner telephony or on Agentforce Contact Center. They are not a smarter IVR: the agent takes the call, understands the request, uses the customer's Salesforce context, answers questions, makes decisions within your guardrails and takes action in your systems, so most service calls are resolved without a human. It hands off to an agent with the full transcript when judgment or policy requires it. I usually stabilize routing and the console first, then move intents onto the voice agent, starting where volume is highest.
What is Agentforce Contact Center?
Salesforce's newer native contact center and telephony offering. It brings calls and Agentforce Voice agents into Salesforce without a separate CCaaS platform. I deliver it alongside Service Cloud Voice with partner telephony; which one fits depends on your existing contracts and how much you want to consolidate.
Is this a Salesforce partner engagement?
I am an independent consultant, not a reseller. I work directly for you across strategy and build, and alongside your Salesforce account team when licensing is involved.
Partner telephony with Service Cloud Voice, the platform alone, or Agentforce Contact Center
Service Cloud Voice is the integration layer, so the real choice is where the telephony lives and whether the agent experience lives in Salesforce.
Partner telephony with Service Cloud Voice (Partner Contact Center)
Your telephony platform, whether Genesys, NICE CXone, Five9, Talkdesk, Vonage or Amazon Connect, handles the calls. Salesforce handles the agent. Agents work in the Service Console, calls become records on the customer timeline, transcripts feed Agentforce, and Agentforce Voice agents go on the phone line.
Keeps your platform's routing, recording and workforce tooling. The usual first step for a team already on a contact center platform.
The telephony platform alone, without Service Cloud Voice
The contact center platform stays standalone, with at most a CTI adapter for screen pop and click-to-dial. Agents live in the platform's own desktop and Salesforce is a lookup.
Workable when Salesforce is one of many systems the contact center serves. It leaves the customer record, transcripts and Agentforce outside the agent's screen, and the phone channel outside your AI strategy.
Agentforce Contact Center
Salesforce's newer native contact center and telephony. One vendor, agents in the Service Console, and Agentforce Voice agents built into the phone channel from day one.
The path when you want to consolidate platforms and build the phone around AI agents that resolve calls rather than menus that route them.
Per-platform guides: Genesys CloudFive9NICE CXone · CCaaS migration · Agentforce
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