Three Things a Telco Team Can Start This Month Without a Procurement Cycle

Most of the AI advice aimed at operators assumes a budget cycle and a vendor. Useful eventually. Not useful to somebody who wants to show something working before the next quarterly review. So here are three that a competent internal team can start on now, using data the business already holds. ## 1. The churn signal Prepaid customers do not tell you they are leaving. They just stop recharging. Take twelve months of recharge frequency, top up size and data usage, and build a model that flags accounts whose pattern has broken. You are not trying to be clever. You are trying to see it two weeks earlier than the monthly report does. Start with one segment rather than the whole base. Measure whether the accounts you flagged actually churned. That single number tells you whether to keep going. ## 2. Care deflection Pull the last quarter of contact centre logs and cluster them by reason. Most operators find a small number of issues driving a large share of contacts, and several of those are resolvable without a human at all. Fix the top three in self service before automating anything, because automating a bad journey just makes people angry faster. ## 3. Site fault prediction Power is the biggest cause of site downtime across much of the region. Alarm history, generator runtime and fuel consumption together carry a usable signal about which sites are heading for a fault. Planned maintenance is cheaper than emergency callout, and the gap between them is the return. ## The step most operators skip Before any of the three, write down which tools are approved and which data may go into them. It takes an afternoon. Without it you get BROAI, which is people quietly using their own AI on company data because nobody told them otherwise, and no model output is worth that exposure. This is the Scan and Score phase of SWITCH, the framework I use with clients. Know the ground truth before you build anything on it. Pick one of the three. Give it an owner and a number it has to move. Come back in thirty days and either keep it or kill it. If you want this run properly inside your team, with your data and your constraints rather than a generic workshop, the [speaking and training page](/speaking) sets out the formats, or reach me directly at me@martins.com.ng or through the [work with me page](/work-with-me).