Chapter 5 of 6 · The workforce

A supervised digital workforce for telecom operations

AI agents on the DaasLabs Data Fabric Framework do the routine work end to end across network operations, fraud and revenue assurance, customer care, churn, BSS/OSS and billing, enterprise, regulatory, wholesale and the data platform. Policy decides what goes straight through, and people approve the exceptions.

Agents
–
 
Squads
–
 
In accelerator demos
–
 
Agents per owner
–
 
Fraud cases in progress
–
live · open the command centre →
Closed with feedback
–
live · outcomes feed the models

Roster figures count the agents on this page. Live figures come from the DaasLabs Telecom demo platform, not from client operations.

Fraud cases by OODA stage

Connecting
Observe, orient, decide and act agents working the SENTINEL pipeline on demo CDR data.
Watch an agent work a case · replayed from the demo platform

Loading a case…

 
  1. Fetching agent-worked cases…

Cases the fraud agents have worked

Select a case to replay it
CaseFraud typeRiskDecisionDecided byFirst evidence
Loading…
How it works

Agents do the work. People own the exceptions.

01

Agents do the work

Each agent works on governed BSS, OSS and CDR data, calls only the tools it is allowed and drafts an outcome with its evidence.

02

Policy decides

Risk tier, exposure limits and the agent's autonomy level decide: straight through, or to a person.

03

People approve exceptions

A named owner reviews, edits or rejects only the cases that need judgement: blocks, credits, claims and anything a regulator sees.

04

Everything is logged

Every signal, tool call, decision and action is kept as an audit trail; outcomes feed the models. See governance →

Agent roster

The workforce, by line of business

Every agent has a named human owner, an autonomy level set by governance, a list of tools it may use and a stated line it never crosses without a person. Agents marked in demo run inside a DaasLabs Telecom accelerator; blueprint agents are reference designs we configure to each operator's systems and controls.

Governance & controls

Autonomy is set per agent and raised only on evidence

Every agent starts at the level governance agrees with risk, privacy and the business owner, and moves up only when its override rate and evaluations support it. The bars show how many agents on this page run at each level.

Named human owner

Every agent has an accountable owner who approves, edits or rejects its exceptions. Blocks on enterprise lines, credits and partner claims always need a person.

Policy limits

Risk tier, exposure and adjustment limits decide what goes straight through; limits are configuration agreed with each operator's risk team, not code.

Allowed tools only

Agents call typed, limited, reversible actions through the Action Fabric — never free-form changes to billing, network or subscriber records.

Privacy by design

Subscriber identifiers are masked in prompts and screens; agents see only the data the case owner is entitled to, inside the operator's own tenancy.

Full audit trail

Every signal, plan, tool call, decision and action is logged with lineage back to the source record, ready for auditors and regulators.

Kill switch

One control pauses an agent, a squad or the whole workforce; work in flight returns to the human queue.

Next chapter · 6 of 6

The journey →

From connectivity provider to intelligent, AI-native operator: score your twelve capability layers, then move from a 30–45 day pilot to scale.

AI
AI Analyst

I'm the DaasLabs AI Analyst for the telecom demo platform. I can help with:

  • Revenue assurance & CDR reconciliation
  • Fraud: SIM swap, SIM box, IRSF and Wangiri
  • Churn, customer and network analytics
  • Executive briefings across the accelerators

Answers are generated from the demo data.