Sinch surveyed 2,527 enterprise decision makers across 10 countries and found 74% had already rolled back or shut down a live AI customer communications agent. The cause was almost never capability. It was missing oversight infrastructure -- audit trails, escalation paths, and human-in-the-loop checks that should have been built before go-live, not after the rollback.
I read the full report this morning and the thing that jumped out wasn't the headline number. It was that the rollback rate jumps to 81% among the most mature organizations -- the ones with the best guardrails. That sounds like a contradiction. It isn't. It's the actual lesson for anyone shipping agents in 2026.
What the Sinch report actually says
The May 13, 2026 Sinch report -- titled "The AI Production Paradox" -- surveyed 2,527 senior decision makers across financial services, healthcare, telecom, retail, technology, and professional services. 74% of those enterprises rolled back or shut down at least one live AI customer communications agent. 62% still have AI agents running in some configuration. And 98% are increasing AI investment in 2026 anyway.
The survey covered the United States, United Kingdom, Australia, Brazil, Germany, France, India, Singapore, Mexico, and Canada. Financial services and healthcare were the largest segments -- the two industries where a wrong answer from an agent has the biggest blast radius. So the rollback signal is loudest exactly where the cost of being wrong is highest. That's not a coincidence (source: Sinch via PR Newswire).
The headline number gets clicks. The real story is in the breakdown of who rolled back and why.
The paradox: mature guardrails caused MORE rollbacks, not fewer
Among enterprises with fully mature guardrails, the rollback rate hits 81% -- higher than the 74% overall average. Daniel Morris, Sinch's CPO, framed it directly: "Higher rollback rates reflect better monitoring and control, not weaker performance." Organizations with mature oversight catch failures other companies are silently shipping to customers.
If you've ever built observability into a system, this should feel familiar. The first week you turn on real logging is the week you discover everything that's been broken for months. The agents weren't suddenly worse at the 81% companies. The 81% companies could finally see what was actually happening.
I think about this every time I add tracing to one of my own automation chains. The bugs were always there. The instrumentation just made them visible enough to act on. Builders shipping enterprise agents in 2026 should expect the same arc -- if your monitoring shows zero issues, your monitoring is broken.
Why governance, not capability, is the actual constraint
The capability question is mostly settled. Claude Sonnet 4.5, GPT-5, and Gemini 2.5 can all handle multi-turn customer conversations, route tickets, summarize history, and call tools reliably enough to put in front of real customers. The Sinch data says 62% of enterprises proved this -- they got agents live in production. The failure mode showed up after deployment, not during build.
What failed was the layer underneath. Per separate 2026 research, 97% of enterprises run AI agents but only 12% have centralized control over them. 72% are in production, 60% lack formal governance. Only 23% have a formal, enterprise-wide strategy for agent identity management (source: Strata 2026 agentic identity research). Gartner's June 2025 poll of 3,400 organizations projects that more than 40% of agentic AI projects will be canceled by end of 2027, citing escalating costs, unclear business value, or inadequate risk controls (source: Gartner).
Builders skip oversight infrastructure because it doesn't ship visible product. Logging an agent's tool calls doesn't make a demo more impressive. Adding an out-of-band human approval step makes the workflow feel slower. So those things get cut. Then production hits, the agent does something nobody anticipated, and the rollback gets added to the 74%.
Want this built for your business?
Venti Scale builds AI automation systems for businesses that want results without the learning curve. One operator, AI-powered, full marketing stack.
See What We Build
The "guardrail tax" -- and why infrastructure beats investment
Sinch's report describes what they call the guardrail tax: engineering teams spending most of their time building and maintaining the safety systems their underlying communications infrastructure should be providing. Investment data backs this up. Enterprises put 76% of AI program budget into trust, security, and compliance, versus 63% into AI development itself. Safety scaffolding is now the number one line item.
The most surprising finding in the report: communications infrastructure satisfaction is a stronger predictor of successful AI deployment than either investment level or guardrail maturity. 87% of respondents rated high-performance infrastructure as essential or very important. Teams that picked the right plumbing first ship agents that stay live longer. Teams that bolt guardrails onto bad infrastructure end up in the 74% (source: Telecom Reseller coverage of Sinch report).
Translated for solo builders and small teams: if your messaging stack, ticketing system, or queue layer is a hack-together of webhook receivers and untyped JSON, every guardrail you add gets fragile. Fix the plumbing first. Then put the agent on top.
What oversight infrastructure actually looks like before go-live
The agents that survived production share a pattern. Before launch, the team had answers to four questions: what is the agent allowed to do, what gets logged, who gets paged when something goes wrong, and how do you stop it. Each one corresponds to a piece of infrastructure -- scope policy, audit trail, escalation routing, kill switch -- and missing even one creates the failure mode that lands an agent in the rollback column.
Here's the practical checklist I'd build against before any agent touches a real customer:
- Tool scope policy. The agent can call which tools, against which data, under which conditions. Default-deny. New tool access requires a config change, not a prompt change.
- Per-action audit log. Every tool call writes a structured event: timestamp, agent ID, tool name, input, output, latency, cost. Stored somewhere queryable. Not a print statement to stdout that disappears.
- Out-of-band human approval for anything that touches money, sends a message to a customer, or modifies a system of record. Sinch found 68% of enterprises rate human-in-the-loop oversight as essential. Most don't implement it.
- Per-session cost cap. A single agent loop that goes pathological can burn $50 in API calls in three minutes. Hard cap per session. Hard cap per day per customer.
- Kill switch with single-page activation. One person, one click, all agents in that scope stop accepting work. Tested at least once before go-live. If you've never tested it, it doesn't exist.
- Escalation routing. When the agent hits ambiguity, an unknown intent, or a confidence threshold, it hands off to a human queue. The queue has an SLA. The SLA is monitored.
None of this is exciting. None of it ships in a demo. All of it determines whether you stay in the 26% that didn't roll back.
What this means for the rest of 2026
The 98% of enterprises increasing AI investment in 2026 -- after watching the 74% roll back -- aren't doing it because they didn't get the memo. They're doing it because the upside still beats the operational cost. The shift is in where the budget goes. Less into capability research, more into the infrastructure that lets capability survive contact with real customers.
For independent builders and small agencies, the opportunity is the same opportunity it always is when enterprise plays catch-up: ship the boring infrastructure first. The team that has logging, scoping, approvals, and a kill switch wired up before the first agent goes live can move faster than the team that has impressive demos and nothing underneath. The 74% is what happens when impressive demos meet production.
I'd watch one more signal over the next quarter -- whether Sinch's "infrastructure satisfaction is the strongest predictor" finding holds up in other industry-specific reports. If it does, it reframes the whole pitch for builders. The work isn't proving the agent can do the task. The work is making the rest of the stack capable of holding the agent accountable when it does.
FAQ
What does it mean that 74% of enterprises rolled back AI agents?
Sinch's 2026 "AI Production Paradox" report surveyed 2,527 enterprise decision makers and found 74% had shut down or pulled back at least one live AI customer communications agent after deployment. It does not mean those companies abandoned AI -- 62% still have agents running in some configuration, and 98% are increasing AI investment in 2026.
Why did so many AI agents get rolled back if the technology works?
The capability layer is mostly fine. The failure mode was governance: missing audit trails, no out-of-band human approval, no per-action logging, no enforced tool scope. The agents made decisions nobody anticipated, and the organizations could not show what the agent did or stop it fast enough. The rollback was a control problem, not a model problem.
Why did more mature companies have HIGHER rollback rates?
Organizations with mature guardrails hit 81% rollback rates, higher than the 74% average. Sinch's CPO explained this directly: better monitoring lets teams see failures that less-mature teams are missing entirely. The rollback is the system working. The companies with the highest rollback rates are catching problems before customers escalate them, not shipping broken agents at higher rates.
What infrastructure should I build before deploying an AI agent in production?
Six pieces: a tool scope policy with default-deny, per-action structured audit logs, out-of-band human approval for sensitive actions, per-session cost caps, a tested kill switch, and escalation routing with an SLA when the agent hits ambiguity. The Sinch data found communications infrastructure satisfaction was a stronger predictor of agent success than either investment levels or guardrail maturity.
Want this built for your business?
Venti Scale builds AI automation systems for businesses that want results without the learning curve. One operator, AI-powered, full marketing stack.
See What We Build
