Amazon just put enterprises on notice: the next wave of contact center AI will not be judged by how well it chats, but by how safely it can act.
In Amazon’s Q4 2025 earnings call, Andy Jassy CEO at Amazon zeroed in on autonomous agents as the main path to real AI value, and he argued that the blocker has been governance, not intelligence.
His answer was Bedrock AgentCore, positioned as the control layer that helps agents securely connect to identity, policy, tools, and monitoring, so enterprises can let them touch real backend systems.
During the call, Jassy said:
“Looking ahead, the primary way companies will get value from AI is with agents.”
For CX leaders, that is a meaningful shift. It suggests the market is moving away from ‘scripted bots’ that collapse when customers go off path, and toward governed autonomy, where agents can pursue outcomes like refunds, account changes, or complex service cases within enforceable guardrails.
The Old Model: Scripted Bots That Break When Customers Go Off Path
For years, contact center AI has been defined by constraint.
In most enterprises, automation was built like a flowchart. You mapped intents, defined branches, and hoped customers stayed on rails. That model worked for narrow, repetitive tasks, but it struggled the moment a customer’s request became messy, multi-step, or policy-heavy.
That is why many “AI in the contact center” deployments have ended up as deflection tools. They answer FAQs, collect basic details, and route interactions. They rarely resolve complex issues end to end.
Amazon Connect has lived in that reality too. It has long used AI to improve routing and self-service, and Amazon has also pushed agent productivity tools, including Amazon Q-style assistance in the broader AWS portfolio. But the ceiling has been governance, not raw model capability.
The New Model: Goals, Tools, and Authority, Not Flowcharts
The emerging agentic era replaces rigid scripts with a different contract.
Instead of telling a bot exactly how to process a refund, you give an agent a goal, the policy to follow, and the tools to act, such as APIs into billing, CRM, fulfilment, and identity. The agent “reasons” through the path, handles edge cases, and completes the work.
That is the promise, and it is also why enterprises have hesitated. When an agent can take action, ‘hallucinations’ stop being an academic risk and start being a security, compliance, and financial risk.
Jassy described that hesitation directly, and he framed it as the central hurdle between prototypes and production deployments.
Why Bedrock AgentCore Is The Missing Link for Enterprise Autonomy
On the call, Jassy argued that building agents is still harder than it should be, and he said AWS has been building services to make agents possible across models. But his sharper point was what happens next.
Once an agent exists, enterprises still need to connect it safely to the real world, and that is where most projects stall.
“Once agents are built, enterprises are apprehensive about deploying to production because these agents need to securely and scalably connect to compute, data tools, memory, identity, policy governance, performance monitoring, and other elements.”
That is the thesis behind Bedrock AgentCore. It is not positioned as another “bot builder.” It is presented as the governance and connectivity layer that makes autonomy viable inside enterprises.
Jassy did not describe AgentCore as optional plumbing. He described it as a solution to a problem “where a solution has not existed,” and he claimed it is already unlocking deployments.
“This is a new and hard problem where a solution has not existed until we launched Bedrock Agent Corp. Customers are quite excited about Agent Core, and it’s unlocking deployments.”
For CX leaders, the implication is straightforward: the differentiator is moving from scripted conversation to governed action.
Amazon Connect Sits Right on the Fault Line
Jassy name-checked Amazon Connect in a list of Amazon-built agents, describing it as an agent for “call center operations.” That matters because contact centers are exactly where autonomy creates outsized value, and outsized risk.
A governed autonomous agent can, in principle, do work that bots historically could not do safely, such as:
Reason through a complex mortgage query, check policy constraints, verify identity, gather missing documentation, and initiate next steps.
Execute cross-system actions, like changing an address, issuing a credit, or scheduling a service appointment, while staying inside policy guardrails.
Manage long-running, multi-interaction cases, preserving context across time rather than resetting every session.
That is the ‘resolution engine’ future. But it only works when the agent can be trusted with identity, permissions, policy, and monitoring, all of which AgentCore is explicitly designed to address.
AWS Is Betting That Agents Become the Enterprise UI
Amazon’s agent push in Q4 was not confined to the contact center. Jassy listed multiple agent categories, from coding to migration to call center operations, plus more autonomous ‘Frontier Agents’ that can run persistently and remember context.
“Customers are also becoming excited about agents that require less human interaction. They can be fully autonomous, run persistently for hours or days, scale out quickly, and remember context,” he said.
Even outside CX, this ‘agents as the new interface’ narrative should feel familiar to enterprise buyers. Vendors are racing to position their stacks as the control plane for autonomous work, and governance is becoming the new competitive line.
Amazon also backed this vision with scale signals. AWS revenue rose to $35.6 billion in the quarter, up 24 percent year over year, and Jassy emphasized continued aggressive investment to meet both core cloud and AI demand. AWS backlog reached $244 billion, up 40 percent year over year, reinforcing that enterprise commitments are still building.
What CX Leaders Should Do Next
If autonomous agents can ‘go off script’ then CX governance has to level up too.
The next wave of CX automation will not be won by the team with the most intents, or the prettiest conversation design. It will be won by the team that can define clear outcomes, implement enforceable policy, and instrument performance so automation is trustworthy at scale.
Three practical moves stand out:
First, treat autonomy as a risk-managed rollout, not a feature launch. Start with bounded actions, and expand authority only as monitoring and controls mature.
Second, align identity and policy to customer journeys. Authentication, permissions, and compliance can no longer live only in security teams if agents are expected to resolve cases end to end.
Third, measure resolution, not deflection. If governed autonomy is real, the KPI shifts from containment rate to outcome quality, time to resolution, and downstream cost-to-serve.
Jassy’s emphasis on Bedrock AgentCore signals that AWS sees the same thing many enterprise CX teams are feeling: models are getting smarter, but value comes from controlled action. In 2026 and beyond, the contact center will not be defined by how well a bot talks. It will be defined by how safely an agent can do the work.
Join the conversation: Join our LinkedIn community (40,000+ members): https://www.linkedin.com/groups/1951190/
Get the weekly rundown: Subscribe to our newsletter: http://cxtoday.com/sign-up
