Running a contact center on Salesforce means agents answer calls, chats and messages inside the same console where cases and customer history live. You can get there two ways. Connect your current phone system through a CTI integration, or move voice onto Salesforce's own contact center offering. The right path depends on your telephony contract, how much call data you want in Salesforce, and how far your routing has matured.
What does a Salesforce contact center actually include?
It is a set of connected pieces, not one product: telephony, routing, an agent console, knowledge, supervisor views and reporting. Salesforce supplies most of them; the phone layer can come from Salesforce or from a vendor you already pay.
The service record sits in the middle. Every call, chat or message should end up attached to a case, contact or account, so the next agent sees what happened. When voice lives outside Salesforce, that attachment is the hardest part to get right.
Service Cloud was rebranded Agentforce Service in 2025 and Salesforce has since returned to the Service Cloud name, now sold in Core, Advanced and Max editions. The voice products have been renamed several times too. Ask your Salesforce account team which bundle you would actually buy before you budget.
What are the Salesforce voice options today?
There are three broad routes: Salesforce's native contact center offering, Salesforce Voice (formerly Service Cloud Voice) tied to Amazon Connect, and partner telephony that plugs a contact center vendor into the console. Names and packaging shift often, so treat this section as a map rather than a price sheet.
- Agentforce Contact Center. Salesforce announced it in March 2026 as native voice combined with digital channels, CRM data and AI agents. Now marketed as Service Cloud Contact Center, it is sold as an add-on to Service Cloud Core, Advanced or Max editions, generally available in the U.S. and Canada at launch; Salesforce's Winter '27 release announcement (August 2026) says it is now available in more than 30 countries, with the release generally available from October 12, 2026. Check whether your region is covered.
- Salesforce Voice with Amazon Connect (formerly Service Cloud Voice). Amazon Connect supplies the phone network and call handling while the agent works in the Salesforce console. AWS also announced a related Salesforce Contact Center with Amazon Connect offering in 2025.
- Salesforce Voice with partner telephony (formerly Service Cloud Voice). A contact center vendor connects through a Salesforce-supported framework, so calls appear in the console and route through Omni-Channel.
- Bring Your Own Channel for CCaaS. A Salesforce developer framework that lets a third-party contact center vendor bring voice and digital channels into the CRM.
Each route has different licensing, setup steps and feature coverage. Ask your account team and your telephony vendor which route your contract supports today, not which one a roadmap slide shows.
Should you keep your telephony and add CTI, or move voice into Salesforce?
Keep your current phone system when the contract, carrier setup and IVR are sound and agents mainly need screen pops and call logging. Move voice into Salesforce when you want one routing engine, call transcripts on the record and supervisors working from one place.
| Factor | Keep current telephony + CTI | Move to Salesforce voice |
|---|---|---|
| Phone contract | Locked in or recently renewed | Ending soon, or the vendor is being replaced anyway |
| Routing | Phone system routes calls; Salesforce routes cases and chats | Omni-Channel can route calls alongside other work |
| Call data on the record | Activity logs, call outcome, sometimes a recording link | Transcripts and call details can attach to the record, depending on configuration |
| IVR | Stays in the telephony platform | Rebuilt in the chosen voice platform |
| Supervisor view | Split between the phone dashboard and Salesforce | More of it inside Salesforce, depending on edition |
| Change effort for agents | Low; the phone tool stays familiar | Higher; new softphone and call flow habits |
| Main risk | Two routing engines that disagree on agent availability | A cutover touching every inbound call at once |
Many teams start with CTI and revisit the question at contract renewal. That is a sensible order when the console and case design still need work.
How do CTI integrations from existing phone vendors work?
A CTI connector puts a softphone inside the Salesforce console and passes call events into Salesforce. The useful outcome is a screen pop that opens the right record, plus an automatic activity log when the call ends.
Connectors fall into a few categories. Cloud contact center platforms usually offer a managed package on AgentExchange (formerly AppExchange). Unified communications and business phone systems often ship a lighter dialer that logs calls. Older on-premise systems may need middleware or a custom adapter built on Salesforce's Open CTI framework.
Whatever the category, test four things before you sign. How is a caller matched to a contact? What happens with no match, or several? Which fields does the call log write? Does the connector respect record sharing?
That last point matters more than vendors admit. An insurance agency we worked with on Sales Cloud kept contacts private to each agent. Its CTI integration was scoped so screen pops for secure inbound calls respected that privacy model.
How should routing work across voice, chat, messaging and email?
Pick one owner for agent availability. If the phone system and Omni-Channel both think they control an agent, people get a call in the middle of a chat.
When voice runs through Salesforce, Omni-Channel can weigh calls against other work using capacity and presence statuses. With external telephony, agents often switch to a phone-only status during call shifts instead. Our Omni-Channel routing guide covers queues, skills and capacity in depth, so we will not repeat it here.
What should transcription and AI summaries do for agents?
They should cut after-call work, not add a review step. Real-time transcription and generated call summaries are available in some Salesforce voice setups, but which features you get depends on route, edition and add-ons.
Treat a summary as a draft the agent confirms before the case is saved. Check accuracy on your own calls, especially with product names, accents and crosstalk. Decide early whether transcripts are stored, for how long, and who can read them. Our guide to AI for service teams covers the wider rollout order.
How should the agent console be designed for phone work?
Design around the first ten seconds of a call. The agent needs to know who is calling, why they might be calling, and what is still open.
- Put the softphone in the utility bar so it stays visible across tabs.
- Show open cases, recent orders or policies and the last interaction on the screen-pop record.
- Use one case layout for calls with only the fields agents set during the conversation.
- Add a short call wrap-up step that captures reason, outcome and follow-up.
- Keep macros and quick text for the handful of replies agents use most.
Fewer tabs and required fields beat visual polish. Sit with agents during live calls before you finalize anything.
What do supervisors need to see during a shift?
They need live queue depth, agents by status, and calls waiting too long. Afterwards, they need trends by queue, reason code and agent.
Depending on the route, Salesforce offers an Omni-Channel supervisor view, and some voice setups add call monitoring or barge-in. Where the phone platform owns real-time data, decide which screen supervisors trust. Build service dashboards in Salesforce for the trend view, fed by consistent call reason and outcome fields.
How do you get knowledge in front of agents during a call?
Surface articles on the case automatically, rather than relying on agents to search mid-call. Map call reasons or case types to article categories so the suggested list matches what the caller needs.
Keep phone-friendly versions short: a step list an agent can read aloud. Track which articles get attached to resolved cases, and retire the ones nobody uses.
How should IVR and self-service hand off to a live agent?
The handoff should carry context so the customer never repeats themselves. Whatever the IVR or bot collected, such as account number or reason, should land on the screen-pop record.
Start with simple self-service: status checks, password resets, business hours. Keep the route to a person obvious. If an AI agent answers first, test what the human sees when it escalates, including a transcript of the exchange so far.
Where does workforce management fit?
Workforce management handles forecasting, scheduling and adherence, and Salesforce is not always where it runs. Options fall into three categories: the WFM module in your contact center platform, a standalone WFM product, or Salesforce's own workforce engagement features where your edition includes them.
Whichever you choose, it needs clean interaction history by channel and interval. That is another reason to get routing and logging right first.
Which metrics should a Salesforce contact center track?
Track handle time, first contact resolution, abandon rate and CSAT, defined the same way across channels. Set your own baselines before you change anything; industry averages say little about your callers.
- Average handle time: talk, hold and wrap-up, split by call reason rather than one blended number.
- First contact resolution: decide whether a repeat contact within a set window counts against it, and write the rule down.
- Abandon rate: separate short abandons, often misdials, from callers who gave up in the queue.
- CSAT: survey soon after the interaction and tie each response to the case and agent.
Watch them together. Pushing handle time down while repeat contacts climb usually means problems are moving, not getting solved.
What compliance rules apply to recording calls?
Recording consent laws differ by state, and some require every party on the call to consent. Design for the strictest rule that applies to your callers unless counsel tells you otherwise.
- Play a recording notice at the start of every recorded call, including transfers into recorded queues.
- Store recordings and transcripts with clear retention periods and access limited by role.
- Pause or mask recording while payment card details are spoken, where your platform supports it.
- Record which consent notice a caller heard so you can show it later.
- Review the setup with legal counsel; this guidance is design advice, not legal advice.
What mistakes do teams make when launching a Salesforce contact center?
- Picking a telephony route from a demo before checking contract terms and region availability.
- Letting two systems control agent status, which produces missed and double-assigned work.
- Logging calls without a reason code, which leaves reports unable to explain volume.
- Turning on AI summaries without checking accuracy on real calls.
- Moving every queue at once instead of piloting one team.
- Skipping recording consent design until after go-live.
What should a first release of a Salesforce contact center cover?
Phase one should give agents one console with a working screen pop, consistent call logging and the case design to support it. Leave advanced AI and full WFM for later.
- Confirm which voice route your contract and region support.
- Define call reasons, outcomes and the wrap-up fields agents complete.
- Set up screen pops and caller matching, including the no-match path.
- Decide which system owns agent availability.
- Publish the knowledge articles behind your top call reasons.
- Build baseline dashboards for handle time, abandon rate and first contact resolution.
- Pilot with one queue, then expand once the numbers are stable.
This is the same crawl-walk-run approach we used when a cybersecurity company moved support onto Service Cloud. That project started with email-to-case, queues, severity levels and escalations before adding more.
