Telecoms boards need agent literacy for two very different estates: a very large base of customer accounts and a network that people rely on. Directors should understand the agent's certified depth and the depth each action needs, how certification earns and removes it, what the record reconstructs, and who stays accountable. They also need to know which account actions are fraud targets that must never become routine.
Why does a telecoms board govern two kinds of agent risk?
On the customer side, agents answer billing questions, change tariffs, chase arrears and handle number transfers. Volume is enormous and most of it is routine. On the network side, agents may read alarms, draft change requests and coordinate field work. Errors there affect whole areas, not single customers. Telecoms operators in the EU can also fall within NIS2, which sets cybersecurity risk management and incident reporting duties for essential and important entities.
A board that thinks only about the contact centre will under-govern the network, and the reverse.
What must directors understand?
- Depth (per agent), and the depth each action needs: 1 read, 2 draft, 3 routine work within bounds, 4 money or hard-to-undo actions, 5 coordinating other agents. A tariff change can be routine; a SIM swap is not.
- Earned authority: depth comes from certification on the operator's own cases, within the role's ceiling. The lower wins.
- Expiry: certificates lapse after 90 days, and a run that clears no depth drops an agent to depth 1 the same day, which can push large volumes back to people.
- Provenance: a fact sealed by the billing or network system outranks a caller's declared identity, and an external message cannot authorise a sensitive change.
- The record: every verdict is filed append-only, so a disputed bill, a fraud case or an outage can be reconstructed.
Which actions should never be routine?
| Action | Agent | Stays with a person |
|---|---|---|
| Billing questions and tariff changes | Executes within bounds at depth 3 | Disputes and complaints |
| Arrears reminders | Sends approved templates at depth 3 | Payment plans and vulnerability cases |
| SIM swap or number transfer | Prepares and holds, with identity checks | Releasing after verification |
| Network change requests | Drafts at depth 2 | Approval through change control |
| Coordinating field work across agents | Orchestrates at depth 5 | Safety-critical decisions |
SIM swaps and number transfers deserve a direct board question. They are a route to account takeover and, from there, to customers' bank accounts. An agent should never complete one on the strength of a caller's declared identity alone.
What does "operator" mean in training?
Telecoms companies are operators, and they employ network operators. Training providers also certify operators: the people who run AI agents day to day. A board paper that says "operators must be certified" can mean three things. Define it. An operator certification in this context means a credential for the people who review agent decisions and run the workspace, earned through an exam and supervised practice on real cases.
What should the board ask for?
A quarterly report covering agent capabilities and depth, failed certification runs, SIM swaps and transfers held and released, and approvers' credentials. The order of training is set out in who in a telecoms operator needs AI agent training first. A readiness assessment in the telecoms operator and a plan to roll out AI agent training across the operator follow. A hospital board faces a similar split between front office and critical operations. The full model is in AI literacy and certification for people who work with agents.
Where the Academy fits
Pryme Intelligence Academy's Certified Pryme Operator credential is for the people who run a live workspace every day. It requires a written exam and a two-week practicum of real review decisions with no missed red line, signed off by a Pryme assessor, and is valid for 12 months.
Questions people ask
Can an agent handle a number transfer request end to end?
It should prepare the request and run checks, but hold it for a person to release after verifying identity through a trusted channel.
Should network engineers take the same training as contact centre staff?
They share the core concepts, but their tests should be set in their own work: change requests, alarms and coordination, not billing.
How much training do directors need?
A few hours of tested literacy, plus a reconstructed fraud case and a reconstructed network incident read from the record.