Ask any CX leader to produce a complete list of every AI agent currently running in their contact centre environment - what it is connected to, what data it can access, and who approved its permissions. Most cannot. This issue is growing by the quarter as major enterprise platform vendors ship autonomous agents directly into customer-facing operations.
Speaking on The Verge's Decoder podcast, Okta co-founder and CEO Todd McKinnon outlined the issue:
"AI agents need to log into stuff. You need to have a system to keep track of them, define their role, define their permissions, what they can connect to and what they can do."
For an industry that has spent the past two years racing to deploy agentic AI, governance infrastructure has failed to keep pace with automation.
Why Is AI Agent Governance in the Contact Center So Difficult?
The vendor deluge has arrived faster than most IT and CX teams anticipated. Microsoft has been pushing AI agents deep into Dynamics 365 Contact Center, equipping them with the ability to autonomously handle customer interactions across voice and digital channels.
SAP is automating ticket resolution through its own AI support capabilities, operating independently on support cases at a speed and volume that no human team can supervise in real time.
Salesforce, meanwhile, has been defending AgentForce directly to investors nervous about what agentic AI means for the future of SaaS, with CEO Marc Benioff framing the technology as an expansion of the platform rather than a disruption to it.
Agents are arriving from every direction simultaneously, each with its own identity model, data connections, and permission logic. No single team in most enterprises has the full picture across all of them.
What Happens When No One Is Tracking AI Agent Permissions?
The consequences of that visibility gap are not abstract. In a contact centre context, AI agents are routinely credentialed into CRM systems, customer data platforms, ticketing infrastructure, and telephony layers. They operate on behalf of customers, with access to purchase histories, account credentials, and personal data.
When the permissions governing those connections are distributed across vendor dashboards, IT procurement records, and individual team deployments, the risk is not just operational inefficiency - it is a customer trust exposure.
McKinnon is deliberately unsentimental about what happens next:
“Stuff is going to go wrong. There are going to be issues and threats and prompt injection."
The question for CX leaders is not whether a misconfigured or compromised agent will cause harm - it is whether they will know about it quickly enough to act, and whether they have the mechanism to respond when they do.