How Salesforce Contact Centers Can Manage Human and AI Agents With Native CTI 

Salesforce introduced something genuinely useful this week. On June 22, 2026, it launched Agentforce Contact Center Workforce Engagement Management (WEM), giving supervisors a single dashboard to manage human reps and AI agents side by side: workforce management, quality scoring, coaching, forecasting, all built natively into Agentforce Service Command Center. For service leaders tired of jumping between disconnected systems, that’s a real fix. 

It’s also built on an assumption most orgs haven’t met yet. Quality management can’t score a call nobody recorded. Coaching can’t pull a transcript that was never generated. The dashboard is only as good as what’s flowing into it. 

That’s the part of the announcement nobody’s talking about. Let’s get into it. 

What Salesforce Actually Announced 

Salesforce introduced Agentforce Contact Center Workforce Engagement Management to help service organizations bring workforce management and quality management into the same Salesforce environment where agents, AI, customer data, and service workflows already live. 

The problem Salesforce is addressing is real. 

Many contact centers still operate with fragmented systems. AI performance may live in one platform. Human quality scores may live in another. Workforce management may sit somewhere else. Call recordings may be stored in a separate phone system. Supervisors are left switching between tools to understand staffing, service quality, customer experience, and agent performance. 

That model becomes harder to manage as AI agents become part of daily service operations. Salesforce WEM aims to give leaders a more unified view of: 

• Human agent performance 

• AI agent performance 

• Workforce management metrics 

• Schedule adherence 

• Staffing and capacity needs 

• Quality management 

• Coaching opportunities 

• Service operation trends 

This is a meaningful shift. It moves workforce engagement from a people-only process to a hybrid workforce process. Service leaders are no longer just asking, “How many reps do we need on shift?” They are also asking, “Which interactions should AI handle, where should humans step in, and how do we measure both fairly?” 

That is the right direction. But it also raises a practical question for Salesforce customers: 

Where does the underlying conversation data come from? 

The Quiet Assumption Behind Every “Unified” Contact Center Pitch 

Every contact center platform announcement makes the same implicit promise: plug this in, and visibility follows. What it doesn’t say is that visibility depends entirely on what the call layer underneath is capturing in the first place. 

Walk through what quality management actually needs to function. A supervisor scoring an interaction needs a recording or a transcript to score. Sentiment analysis needs a transcript with enough fidelity to read tone, not just words. Coaching workflows built around “real interactions, not abstract metrics” (Salesforce’s own framing) need actual interaction data, not a disposition field someone filled in after the fact. 

None of that shows up automatically. It has to be captured at the call layer, structured well enough to be useful, and tied to the right Salesforce record before any workforce engagement tool can touch it. 

For organizations running Agentforce Contact Center’s native voice on Hyperforce, that capture happens by design. For everyone else, and that’s still most Salesforce orgs with a phone system today, the capture has to come from somewhere else: a CTI integration sitting between the telephony provider and Salesforce. 

This is not a knock on what Salesforce built. It’s a reminder that workforce engagement management is a layer that sits on top of call data. It is not a replacement for the system that generates that data. 

Why CTI Is No Longer Just Click-to-Dial 

For a long time, CTI was treated as a convenience feature. Click-to-dial from Salesforce. Screen pop on inbound calls. Auto-log activities. Basic softphone controls. 

Those features still matter. In fact, the best CTI and softphone tools for Service Cloud call centers still need to make daily calling easier for agents. But the role of CTI has expanded. 

In a hybrid contact center, CTI is becoming the operational intelligence layer for voice interactions. 

It helps answer questions like: 

• What was said during the call? 

• Was the customer frustrated? 

• Did the agent follow the right process? 

• Did the AI agent escalate at the right moment? 

• Did routing send the customer to the correct queue? 

• Did the call outcome match the customer’s actual intent? 

• Which conversations should supervisors review? 

• Which patterns should influence coaching, staffing, or automation? 

These questions cannot be answered with basic call logging alone. They require call recording, AI transcription, sentiment analysis, IVR history, routing context, and CRM alignment. 

That is why evaluating the best enterprise contact center CTI for Salesforce now requires a different lens. The question is no longer, “Can this tool make calls from Salesforce?” 

The better question is: “Can this CTI stack capture the interaction data our hybrid workforce needs to improve?” 

Five Things a Hybrid Workforce Actually Needs From the Call Layer 

A Salesforce contact center managing both human and AI agents needs more than voice connectivity. It needs a call layer that can support visibility, coaching, compliance, routing, and continuous improvement. Here are the capabilities that matter most. 

1. Call Recording That Connects to the Right Salesforce Record 

Call recording is the foundation of quality management. 

Without recordings, supervisors depend on notes, dispositions, or memory. That is not enough for serious coaching, compliance review, dispute resolution, or service quality improvement. 

For call recording to be useful, it has to be connected to the CRM record the conversation belongs to. 

That could be a case, contact, account, lead, opportunity, or custom object. The key is that supervisors should not have to leave Salesforce, open a separate telephony portal, search by phone number, and guess which file is the right one. 

A Salesforce-native CTI experience should make recordings easy to find from the service record. 

This matters even more in hybrid workforces. If AI agents and human agents are both participating in customer conversations, leaders need one clear record of the customer journey. Otherwise, coaching and quality analysis become fragmented. 

2. AI Transcription That Makes Calls Searchable 

Recordings are valuable, but they are hard to analyze at scale. 

Transcripts turn calls into searchable CRM data. 

With AI call transcription and sentiment analysis for CRM, service leaders can identify patterns across hundreds or thousands of conversations. They can search for recurring complaints, missed escalation signals, product confusion, compliance language, refund requests, cancellation risks, or knowledge gaps. Transcripts also make coaching more specific. 

Instead of saying, “The call could have gone better,” a manager can point to the exact moment where the customer’s concern was missed or where the rep successfully de-escalated the conversation. 

For AI-era contact centers, transcription also supports better automation design. If many customers are calling about the same issue, that may be a candidate for an AI agent workflow, knowledge article update, IVR improvement, or proactive notification. 

3. Sentiment Analysis That Surfaces Coaching Moments 

Traditional contact center metrics do not always reveal customer emotion. 

A call can have a short handle time but still leave the customer frustrated. A case can be marked resolved even though the customer felt unheard. A rep can follow the script but miss the emotional tone of the conversation. 

Sentiment analysis helps supervisors detect those moments. Real-time call transcription and sentiment analysis can help identify: 

• Frustrated customers 

• Escalation risk 

• Negative sentiment trends 

• Successful service recovery moments 

• Calls that need supervisor review 

• Training gaps across teams 

• Repeated process friction 

Sentiment should not replace human judgment. But it can help managers prioritize which conversations deserve attention. 

That is especially useful when AI agents are part of the workflow. Service leaders need to know not only whether AI resolved the interaction, but whether the customer experience was actually positive. 

4. IVR and Routing Data That Explains the Journey 

Quality management is incomplete without routing context.

A poor service experience is not always caused by the agent who answered the call. Sometimes the customer waited too long in the queue. Sometimes the IVR sent them to the wrong team. Sometimes the customer had already repeated the issue to an AI agent before reaching a human rep. Sometimes the case priority did not match the customer’s actual urgency. 

Routing data helps explain the path behind the outcome. A strong Salesforce contact center CTI setup should capture: 

• Call direction 

• IVR path 

• Queue history 

• Wait time 

• Transfer history 

• Agent assignment 

• Disposition 

• Escalation details 

• Related CRM record 

This context helps managers separate coaching issues from process issues. If many calls are being transferred twice before resolution, the problem may be routing design. If AI agents escalate too late, the problem may be intent classification or handoff logic. If high-priority customers are landing in general queues, the issue may be CRM data or routing rules. CTI makes those patterns visible. 

5. A CTI Softphone That Supports Agent Productivity 

Hybrid workforces still depend on human agents. 

As AI handles more routine work, human reps often handle more complex conversations. That makes agent productivity more important, not less. 

A CTI softphone inside Salesforce should reduce friction during live customer interactions. Agents should be able to answer calls, view customer context, take notes, select dispositions, transfer calls, access recordings, and log activity without switching between multiple windows. 

The best CTI softphone for desktop call center productivity is not just about faster dialing. It is about keeping the agent focused on the customer. 

For service teams, that means: 

• Faster screen pops 

• Fewer manual logs 

• Better call notes 

• Cleaner activity history 

• Easier transfers 

• Faster follow-ups 

• Less context switching 

When agents handle complex calls after AI handoff, every second of context matters. 

Where 360 CTI Fits Into This Shift 

360 CTI fits naturally into this conversation because it supports the interaction layer Salesforce contact centers need as they move toward hybrid workforce models. 

While Salesforce WEM helps supervisors manage staffing, coaching, and performance visibility, 360 CTI helps bring the underlying voice data into Salesforce. That includes: 

• Call recording 

• AI transcription 

• Sentiment analysis 

• IVR 

• Call routing 

• CTI softphone 

• Call logging 

• Supervisor visibility 

• CRM-linked interaction history 

The positioning is important. 360 CTI is not competing with Salesforce WEM. 

It complements the WEM vision by helping teams capture and structure the voice interactions that workforce engagement depends on. 

For organizations using Sales Cloud or Service Cloud with existing telephony systems, 360 CTI helps keep calling workflows inside Salesforce. Instead of leaving recordings in a separate phone portal or relying on manual notes, teams can bring calls, transcripts, dispositions, and context closer to the CRM record. 

• That gives supervisors better data for coaching. 

• It gives admins cleaner activity history. 

• It gives service leaders stronger visibility into customer conversations. 

• It gives organizations a more practical path toward AI-ready service operations. 

What This Means If You’re Evaluating CTI Right Now 

For service leaders looking at the best enterprise contact center CTI for Salesforce, the bar just moved. It’s no longer enough to ask whether a CTI tool supports click-to-dial and basic call logging. The questions worth asking now: 

• Does it capture call recordings and transcripts at a quality level a supervisor would actually trust for coaching, not just a compliance checkbox? 

• Does sentiment analysis run in real time, or only as a delayed batch process after the call ends? 

• Does routing and IVR data get tied to the same record as the call outcome, so a supervisor sees the full path, not just the result? 

• Does it work whether your org ends up on Agentforce Contact Center’s native voice, a CCaaS partner, or stays exactly where it is? 

A CTI layer that answers yes to all four isn’t competing with Salesforce’s workforce engagement management. It’s what makes that workforce engagement management worth having. 

Conclusion 

Salesforce’s hybrid workforce framing is accurate. AI agents are handling more of the routine work, and human reps are increasingly handling what’s left: the complex, the emotional, the escalated. Managing both well does require a single view. 

But a dashboard is not a data source. The real work, the part that determines whether quality scoring means anything or coaching sessions are built on real interactions, happens one level down, at the point where a call gets captured, transcribed, and tied to a record. Get that layer right, and every workforce tool built on top of it, Salesforce’s or otherwise, actually works the way it’s supposed to. 

360 CTI gives Salesforce sales and service teams call recording, AI transcription, sentiment analysis, IVR, routing, and a full CTI softphone built natively inside Salesforce, so the workforce visibility your team needs has real data behind it.