01The systems in the way
Field and back-office staff work across several disconnected vendor systems — provisioning, fault management, monitoring, device configuration and billing. Each has its own login, data model and quirks. None of the vendors has a commercial reason to build an API, and replacing the stack is not on the table.
| System | What it gives you |
|---|---|
| Vendor portal | no API |
| ERP | partial API |
| Network mgmt | closed protocol |
| Billing | screen scrape |
| Ticketing | REST API |
| Field app | offline first |
02Why the usual approaches stall
OSS consolidation programmes are multi-year and frequently overtaken by the next equipment generation. In the meantime the daily cost is a technician holding five sessions open to complete one task.
If a human can do it in a browser or a terminal, an agent can do it — at volume, with an audit trail. That is the whole basis of how we approach telecom: we treat the systems you already run as the integration surface, rather than waiting for an API that is never going to ship.
03What an agent actually does here
Worked example
An operations agent authenticates into each system, normalises the data into one model, and exposes a single interface — plus a fault engine that surfaces degradation from equipment telemetry before customers call it in.
This is a reference design drawn from the problems we are asked about most often in telecom — not a case study of delivered client work. Where we have shipped a build, we say so plainly and put you in touch with the client.
In production · TelecomRunning a multi-location FTTH operation on agents, where nothing has an API
283 production automation modules and 26 services running continuously, driving BSNL provisioning, billing, fault and voice systems. This one is our own operation, and we say so on the page.
Read the case study →04Constraints we design to
- Works against the vendor systems you already run, without replacing them
- Read-only until a specific write path is agreed and dry-run tested
- Offline-first field deployment where sites lack connectivity
- Every autonomous action is logged, replayable and reversible
Tell us which system is the problem
Describe the workflow that is done by hand today and the system that blocks it. We will come back within one working day with an initial read on feasibility — including if the honest answer is that an agent is the wrong tool.
Scope your agent →