Artificial Intelligence1 min read

How U Mobile built agentic telco operations with Amazon Bedrock AgentCore

By · Published by Everything Blog

In short

Malaysian 5G carrier U Mobile introduced the AiDaH platform to coordinate backend systems, analyze diagnostics, and suggest remediations for operational bottlenecks. Built using Amazon Bedrock AgentCore, the architecture relies on a managed runtime and built-in memory to maintain multi-turn conversational context without overhead infrastructure management. The deployment now encompasses more than 150 operational scenarios spanning six company divisions. It expanded from a small pilot into an active tool used by dozens of second-level call center and branch staff.

Key points

  • Deploying the AI platform resulted in trouble ticket reductions of up to 84.5 percent acr…: Deploying the AI platform resulted in trouble ticket reductions of up to 84.5 percent across primary service categories.
  • The architecture automates multi-step diagnostic investigations by bridging hybrid on-pre…: The architecture automates multi-step diagnostic investigations by bridging hybrid on-premises environments with cloud infrastructure.
  • Utilizing Amazon Bedrock AgentCore eliminated the requirement to maintain dedicated agent…: Utilizing Amazon Bedrock AgentCore eliminated the requirement to maintain dedicated agent infrastructure while preserving conversational context.

Sources checked by our analysis pipeline: 1

Artificial Intelligence

How U Mobile built agentic telco operations with Amazon Bedrock AgentCore

U Mobile, Malaysia’s newest 5G network provider, has always run its telco operations lean, doing more with less through continuous automation. When new AI capabilities became available, U Mobile explored how to enhance operational efficiency beyond basic productivity gains. The real opportunity was further upstream, in how operations teams diagnose and resolve problems in the first place. The same lean operating discipline shaped the foundation for AiDaH: not a one-off technology initiative, but the next step in a long-running journey to simplify operations and scale capability without adding complexity.

When a subscriber can’t purchase a data add-on, resolving it isn’t a single problem. It’s a coordination problem. A customer service agent needs to pull interface logs for error codes. The same agent must then query business support system APIs for subscriber eligibility, and cross-reference internal knowledge bases for applicable business policies. All of that happens across multiple systems, before drafting a single word of response. And when that fails, the ticket escalates to backend IT teams and…

Artificial Intelligence