Capabilities
A capability is something AI can do for the business, described by what it does rather than how it is built: “answer tariff questions with the source cited”, not “use RAG”. It is a means to a business outcome, not the outcome itself.
It is the top level of the taxonomy in 1.2, and it stays the same when the product underneath changes. The eight below are common examples for a telco, not a complete list; a programme will name its own.
Of these, four rest on generative AI, three on classic machine learning, one on either. That split matters more than any vendor’s list: it decides cost, explainability and how predictable the output is.
Capability and business outcome
A business outcome is the measurable change the business is paying for: lower cost to serve, faster resolution, fewer repeat contacts, less revenue lost to fraud or churn. It has a business owner, a baseline measured before any pilot, and a target agreed with finance. A capability is one candidate way of moving it.
| Capability | Business outcome | |
|---|---|---|
| Example | Answer tariff questions from company knowledge, citing the source | Average handling time for tariff calls down from 7 to 5 minutes; fewer repeat contacts |
| Answers | What can AI do here? | What has to improve, by how much, and for whom? |
| Owned by | The AI or platform team that builds and runs it | The business owner who funds it and changes the process to bank the benefit |
| Proven by | Evaluation: accuracy, cited sources, latency, cost per request | Measurement against the baseline, over at least a full budget cycle after go-live |
The direction matters: the outcome is chosen first, then the capabilities that could move it. One outcome can need several capabilities (cutting dispute handling time may take understanding documents, answering from knowledge and acting on billing), one capability can serve several outcomes, and some outcomes are better served by a process or data fix with no AI at all.
A capability working does not mean the outcome is reached. An assistant can answer correctly and handling time stay flat, because agents do not trust it, the process around it is unchanged, or the minutes saved are absorbed rather than taken out of cost. That gap is the most common reason an AI pilot that passes its technical tests fails to win production funding.
Generative or classic: why it matters
| Generative AI | Classic machine learning | |
|---|---|---|
| Output | Text, code or images; can differ for the same input | A score, a class or a forecast; the same input gives the same output |
| Explaining a result | Hard; show the sources it used | Easier; the features behind a score can be documented |
| Cost shape | Per request; grows with use | Mostly training and hosting; cheap per prediction |
| Maturity in telcos | Recent; operating practice still forming | Long established in churn, fraud and forecasting |
| Data it needs | Documents and knowledge, kept current | Labelled history, in volume |







