Your engineers are spending their week on diagnostics they've run a hundred times.
AEX is building operational agents for fiber networks, grounded in live network data and real resolution history, with the customer holding the autonomy dial.
~85%
of operators lose a fifth or more of the engineering week to manual diagnostics
~25%
lose more than 60% of that week to the same manual work
50%
picked network troubleshooting as where AI should apply first
The real constraint is not capability. It is permission.
A majority of operators polled said they'd allow an agent to diagnose but not to act, and most of the rest wanted human approval before any change. That's the right instinct: a confidently wrong recommendation is a nuisance in a chat window and an outage on a network. So we designed for it rather than around it.
Identity-scoped Execution
No Free-form Commands
An Autonomy Ladder You Control
Full Audit Trail
Why this works when a chatbot over an API does not
Every OSS/BSS vendor will claim AI this year, and most will ship a chat window over their existing APIs. General-purpose models fail in live networks in specific, predictable ways: they lose critical detail inside long runbooks, they produce different answers to the same question, they hallucinate actions, and they have never seen the long tail of operator, OEM, and firmware combinations where real incidents live.