Telcos: are your products AI-agent ready?
sebastianbarros.substack.com
March 26, 2026, 1:07 p.m.
Last week, I built an agent that can answer my calls, transcribe the conversation in real time, extract intent, summarize the outcome, and book a meeting directly in my calendar. It actually works. Speech-to-text runs with low latency, the model understands context, and the workflow executes end-to-end without friction. For the first time, it feels like a real replacement for missed calls and voicemail. Except for one thing: I cannot connect it natively to my mobile number. My carrier does not expose a clean interface for my AI agent to take control of an incoming call, decide what to do, and act. I can route around it using VoIP or a programmable voice provider, but that proves the point. The intelligence layer is ready, but the Telco network interface is not.The problem is that Telco products and services still rely on human interaction. AI agents will not use your app, your portal, or your retail channel. They will not tolerate friction, delays, or manual workflows. They will consume identity, voice, messaging, QoS, and billing as programmable building blocks. They will select infrastructure based on APIs, latency, reliability, and price, just as developers chose cloud over data centers. Hyperscalers and CPaaS players are already aligned to this model, but telcos are not. As agents scale into tens of millions of active workloads, they will become a major consumer of compute, APIs, and network resources. The question is not whether agents will use telecom infrastructure, but if they will use yours.