Everything You Ever Wanted to Know About Agentforce Voice (But Were Afraid to Ask)
A practical guide to what Agentforce Voice is, how it works, and where it's delivering results in production today.
You've probably heard of Agentforce Voice, but the details might be a little fuzzy. “Is it a separate product?” “How does it connect to my existing agents?” “I already have AI chat — do I really need it for my telephony, too?”
The truth is, customers don't distinguish between channels. Whether they're typing, emailing, or calling, they expect the same level of service every time they engage with your business. With AI, those expectations have never been higher. Every interaction is an opportunity for a personalized white-glove experience. But as AI agents rapidly transform the way businesses engage with customers through text channels, telephony has emerged as a new blindspot for many organizations. As text-based interactions go AI-native, voice calls remain stuck in the past.
Much of that disparity is self-inflicted. Many enterprises approach voice AI as a separate procurement, with a new vendor, new infrastructure and second AI stack. That means two separate systems to maintain, two sets of guardrails to define and keep in sync, and a seam between them that customers feel every time they switch channels. Voice AI shouldn’t live in a silo. It should be a core capability of the agents you’ve already built, using the same reasoning engine, knowledge base and escalation paths.
That doesn’t mean voice is simply chat with a microphone. Three things make it harder :
Latency
In a phone conversation, even two seconds of silence feels like an eternity.
Verbal nuances
Voice agents have to grapple with filler words, false starts, background noise and other unique challenges.
Telephony Integration
Most enterprises have years of investment in their telephony stack that voice agents need to integrate with natively.