Dipp AIDipp AI

Case study · Telecommunications

A telecom operator got one view of eleven agent frameworks and four providers

Nobody could say how many agents were running. The first week of cross-provider tracing found 41 in production that no one had registered.

Telecommunications operator · 22m subscribers · published August 5, 2026

Download the PDFApply for early access

41

unregistered production agents discovered in week one

100%

of agent executions traced end to end

from an estimated 28%

4 → 1

provider dashboards required to answer a spend question

22%

of agent traffic found to be duplicated across business units

Summary

Six business units at a telecom operator had each adopted their own agent framework and provider. Orcher's Observability layer traced every execution across all of them — which model, which role, what cost, what outcome — and the inventory alone changed the operator's risk posture.

Orcher components enforced

Solution: Cost discipline & intelligent routing

The situation

What was happening before Orcher.

  • Eleven agent frameworks and four model providers were in production across six business units.
  • Each provider dashboard told a partial story, and none of them knew about human roles or business outcomes.
  • The CIO could not answer a board question about how many autonomous systems were running against customer data.

What Orcher enforced

The control surface, component by component.

  • Observability instrumented the execution path rather than the frameworks, so coverage did not depend on each team adopting a library.
  • Every trace carries the directive, the role, the model, the cost and the committed outcome, joined into one timeline.
  • Unregistered agents surfaced automatically as traffic with no registered owner, and were given owners or shut off.
  • Cost Governance ceilings were applied afterwards, once the inventory was real.

The data

Measured over the engagement window.

Business unitFrameworksAgents registeredAgents foundAction taken
Consumer care31427Owners assigned
Network operations2912Owners assigned
B2B service24116 retired as duplicates
Finance1264 retired
Field services279Owners assigned
Marketing108All 8 shut off

First-week discovery results from cross-provider tracing.

Outcomes

What the organisation did next.

  • The operator retired 18 agents as duplicates or orphans within a month.
  • Board reporting on autonomous systems moved from estimate to inventory.
  • Cost ceilings became enforceable, because the traffic they applied to was finally known.
  • New agent deployments now register automatically as a side effect of running through the control plane.
“We thought we had a governance problem. We had an inventory problem wearing a governance problem's clothes.”
— Chief Information Officer, telecommunications operator (partner declined attribution by name)

Read further

The research behind this engagement.

Disclosure. Design-partner engagement, anonymised at the partner's request. Figures are measured by Orcher's own observability and ledger instrumentation over the stated period and have not been independently audited. Market figures carry their own source line.

More engagements

Other organisations that had to prove the same thing.

Run this pattern on your own workflow

Design partners deploy Orcher on one directive class, instrument it the way this study was instrumented, and keep the evidence whatever they decide afterwards.

Apply for early accessAll case studies