Network investment, pricing and channel performance are reviewed quarterly while customers feel problems daily. Planners connect congestion, churn and dealer performance each day, and put capacity and offers where they matter most.
A worked example for a typical Malaysian National Mobile Operator, not a description of any real company. Go through the six stages in order: paste each prompt into Claude, check the answer against how your business really works, then continue. Change the profile at the start to match yours.
Stage 1 of 6
Map how the operation really runs
Act as an operations consultant. I run a National Mobile Operator in Malaysia. Profile: A Malaysian mobile operator — millions of subscribers, prepaid and postpaid, 5G rollout, retail stores and dealer channels.
Interview me, one question at a time, to map how decisions actually get made today. Cover: the recurring meetings and reports, who decides what, which numbers people trust, and where decisions are late or made on gut feel.
Known friction: Revenue per user vs. Keeping users; Spending on towers vs. Customer experience; Reaching everywhere vs. Paying back; Winning new vs. Keeping old; Own stores vs. Partner dealers.
After 8 to 10 questions, summarise the five decisions that cost us the most when made late, in a table: decision, current owner, current delay, cost of delay.
Stage 2 of 6
Design the specialist agents
Using the decision map above, design 5 specialist AI agents for our National Mobile Operator: Plan Mix, Cell Load, Dealer, Network Watch, Coverage.
For each agent give: the one question it answers every day, the data it reads, what it may recommend, what it must never do alone, and the format of its output.
Starting points for what each should watch:
- Plan Mix: plan mix, ARPU, churn by segment, competitor offers
- Cell Load: cell congestion, traffic growth, capex priorities
- Dealer: store and dealer sales, activation quality, commissions
- Network Watch: incidents, fault trends, mean time to repair
- Coverage: returns by cluster, 5G coverage vs. take-up, spectrum use
Keep every agent narrow. If an agent covers two jobs, split it.
Stage 3 of 6
Wire up data and compliance
For the agents above, list the data feeds needed. Likely systems: Billing and CRM; Network performance counters; Fault-management system; Dealer and POS data.
Output a table per agent: field, source, how often it refreshes, data-quality risk, and what the agent should do if the feed is stale or missing. Mark every personal-data field and say how to minimise it.
Rules we operate under: MCMC and Communications and Multimedia Act requirements, quality-of-service standards, PDPA 2010 and strict handling of subscriber data. Agents see aggregated network and usage data, not message content.
End with a short list of actions that always need human sign-off.
Stage 4 of 6
Design the morning brief
Design the single daily brief that pulls the 5 agents together for the CEO, ready before the first meeting of the day.
Specify how the brief merges overlapping or conflicting recommendations, how it ranks items (impact, urgency, reversibility, confidence), and the exact fields per item: what to decide, recommended action, evidence, owner, deadline, and the cost of doing nothing.
Then write a realistic sample brief of five items. Items might resemble: Add capacity at 14 congested cells in Klang Valley before the school holidays / Test a targeted retention offer for the high-churn prepaid segment / Escalate the recurring fault pattern on the East Coast backhaul.
Stage 5 of 6
Build and automate it
Turn the design into a working automation for our National Mobile Operator.
Needs: a scheduled daily run; the 5 agents run in parallel and each saves structured JSON; a final step reads them all and sends the brief by email or chat; every run is logged with inputs, outputs and cost.
Propose the build with Claude plus a workflow tool (for example n8n or the Claude Agent SDK). Give the steps in order, what happens when a data feed fails, and a human-approval step before anything that spends money or makes a customer commitment.
Stage 6 of 6
Roll out and measure
Write a rollout plan for the National Mobile Operator agent team that starts small and earns trust.
Stage 1: one agent, advisory only, run alongside the current process. Stage 2: add the other agents. Stage 3: switch on the daily brief. Stage 4: let agents prepare low-risk actions for approval.
For each stage give duration, owners, what "ready to move on" means, and the metrics to track: time to decision, how often recommendations are accepted, hours saved, and errors caught. Close with the three biggest risks and how we contain them.
