If you take something and you make it agentic scale, the thing that comes after it also has to be agentic scale. If you don’t, and that’s human scale, that is where the ROI goes to die.”
Joe Inzerillo, President of Enterprise and AI Technology at Salesforce, said that on stage at Dreamforce 2026. Then he went further: when you hear that 95% of companies aren’t getting value from AI, it’s because they haven’t made the entire process agentic.
Agents need agents. That’s the whole rule.
And in most Salesforce orgs, the step still running at human scale is the phone call.
What “Agents Need Agents” Actually Means
Inzerillo laid it out in “Salesforce on Salesforce: Scaling the Agentic Enterprise,” the September 15 session where Salesforce’s own leaders walked through what broke while running the company on its own agents. We covered the wider event in our full Dreamforce 2026 recap. Here, we’re following one idea from that list into the place most orgs never look.
Manufacturing figured this out decades ago. Eliyahu Goldratt’s theory of constraints says a system only produces as fast as its slowest step, so speeding up any other step just grows the pile of work waiting in front of the bottleneck.
That’s the trap. Agentic isn’t a property of a tool. It’s a property of a process. You can license five agents and still run a human-scale process, as long as one person sits between any two of them.
Salesforce’s own research points the same way. Its August 2026 study of 2,025 agentic AI leaders found agents deliver more when they’re embedded in the workflow instead of bolted onto it. Bolted on is exactly what a phone call becomes when an agent’s last action is creating a task for somebody else.
Your Agentic Enterprise in Salesforce Has the Same Gap in Service
Swap the lead for a case and the story barely changes.
A customer emails about a failed payment. Agentforce classifies the case, sets its priority, finds the right knowledge article, and drafts a reply in seconds. The customer writes back: “Can someone just call me?”
Now there’s a callback request in a queue, and it’ll wait for the next free rep, which on the Monday after a billing incident could mean tomorrow afternoon. When that rep finally dials, they often open the case cold, reread the thread, and ask the customer to explain it all again.
So this isn’t only a sales argument. Any process that ends with “someone will call you” inherits the speed of whoever makes that call.
What an Agentic Phone Call Looks Like
Most talk about Salesforce AI phone calls fixates on the voice: how natural it sounds, how quickly it answers. Honestly, that’s the easy part now. What makes a call agentic is what triggers it and where its output goes.
Start with the trigger. In an agentic process, qualification doesn’t create a task. It creates a call. 360 CTI can hand a record to an AI that makes the first call from a record-triggered Flow, so the moment a lead meets your criteria, dialing starts. The AI Voice Agent opens with what’s already on the record, asks qualifying questions, handles “not now, try me Thursday,” and either books the meeting or captures why not. The same agent picks up inbound first-touch calls, too.
Then the output. A call ending in a rep’s memory is a dead end for every agent downstream, so the conversation has to land in Salesforce as data. 360 CTI logs and summarizes every call against the right record, with the recording attached, a transcript generated, sentiment captured, and the outcome dispositioned. Your nurture agent, your forecast, and the AE who takes the meeting can all work from what the prospect actually said (not a two-word note typed at 7 p.m.).
One caveat before anyone wires this up in the US. In February 2024, the FCC ruled that calls using AI-generated voices count as “artificial” voice calls under the TCPA, which means prior express consent is generally required before you place them. The practical move: put the consent check inside the Flow’s entry criteria, so a lead without a valid consent record never triggers an AI call in the first place. Speed is useless if legal shuts it down in month two.
Salesforce ran into this wall itself. Marc Benioff has estimated that about 100 million leads went unanswered at Salesforce over roughly 25 years because there weren’t enough people to call them back, with around 400 SDRs facing millions of leads a year. The company’s answer was agentic follow-up.
Agentforce Voice, or Calling That Already Lives in Your Org
Salesforce sells its own answer here, and it’s a real product. It’s generally available and brings the Agentforce Builder model (subagents, actions, Flow-backed logic) to the phone. According to Salesforce’s admin team, it runs on top of Salesforce Voice, formerly Service Cloud Voice, with Amazon Connect or a supported CCaaS partner underneath. Prerequisites include an Agentforce for Service license and Omni-Channel, and Salesforce is explicit that it can’t be layered onto a legacy telephony setup.
For a service org already standardized on Salesforce Voice, that’s a strong fit. We’d tell any prospect the same.
360 CTI fits a different starting point: teams that already make and take calls inside Salesforce through an AppExchange app, often sales-led and outbound-heavy, who want the call step to become agentic without re-platforming the contact center or adding a separate contact-center license tier.
And it doesn’t have to be either-or.
Do Your Agents Need Agents? A Three-Question Audit
AI Calling Agent
Before you buy anything, answer three questions about your own org:
Where in your lead or case flow does the first phone call happen?
How long does a qualified lead wait before that call? Measure it. Don’t guess.
Who or what makes the call?
If the answer to the third is “a rep, when they get to it,” that step runs at human scale, and everything upstream is waiting on it. Salesforce-native calling is where the fix starts, because the call has to live where the trigger and the data already do.
Start with question two. The number’s already sitting in your org. If field history tracking is on for Lead Status, it’s the gap between the change to Qualified and the first completed Task with a subtype of Call.
The Agentic Enterprise Is Only as Fast as Its First Call
Dreamforce 2026 gave Salesforce teams new models, new interfaces, and agents that reason across the whole org. None of it changes what happens after an agent qualifies a lead and the next step is a phone call nobody has made yet.
That’s where Inzerillo’s rule actually gets tested. Not in the scoring model or the routing logic, but in the stretch between “qualified” and “hello,” when either an agent dials or a task sits behind a demo, a lunch break, and a time zone.
Closing that gap doesn’t mean taking people out of sales or service. It means moving them to the point where their judgment changes the outcome. Your reps should be talking to a prospect who already agreed to the meeting, not one who filled out a form two days ago and has since forgotten why.
Read more at...https://360cti.com/blog/agents-need-agents-why-the-phone-call-is-where-agentic-roi-goes-to-die/
Top comments (0)