TTotogi BSS Magic

A billing migration that normally takes four to eight months and a 20-person project team took two weeks at a Tier-1 North American mobile operator, and annual system costs fell from $280,000 to $70,000, according to Totogi’s February 2025 announcement. That project is the clearest public proof of what Totogi BSS Magic does: it puts a telco ontology and a set of AI agents on top of the business support systems operators already run, so work that used to need consultants and long test cycles can be done by software.

BSS Magic is best for large mobile operators with tangled, multi-vendor BSS estates that want to fix order failures, process change requests and migrate systems faster without a full replacement. Buying details are mostly private: there is no price list, most customers are unnamed, and many published figures are vendor results or targets. It is sold on custom quotes, and we rate it 7.7/10 on our scale, with pricing transparency and public reviews as the main areas to build on. We have not used BSS Magic ourselves; this review is based on Totogi’s announcements, an AWS technical write-up and trade press coverage.

Operator Results Mostly Without Customer Names

Totogi publishes more operator results than most vendors in telecom AI, though most come without customer names. These are the figures we confirmed on the source pages.

For a buyer, the pattern matters more than any single number. Totogi’s results cluster around work that operators usually hand to systems integrators: mapping interfaces, writing integration code, testing and tracing why an order failed. Those are expensive, slow and repetitive, which is where a shared data model plus agents can save the most time.

One point to note is that nearly every figure comes from Totogi itself, and the January 2026 Southeast Asia numbers (more than 50% fewer tickets and a faster repair time) are stated as targets. Ask for references from operators with a similar vendor mix before treating any of them as a forecast for your network.

An Ontology of the Operator’s Business, Then Agents

BSS Magic has two layers. The first is the Totogi ontology, a semantic model of an operator’s business: orders, services, products, customers and the links between them. The second is a set of AI agents that read and act on systems through that model instead of through one-off integrations.

The Ontology Layer

Totogi builds the ontology on TM Forum’s Open Digital Architecture, 3GPP and other industry standards, then maps it to the operator’s actual systems, which can include Amdocs, Ericsson, Huawei and Salesforce products. CEO Danielle Rios describes the result as one representation of the telco, and Totogi argues that grounding agents in that model reduces hallucinations because each action has to fit known entities and relationships. The same layer is reused for later use cases, which is why Totogi claims new projects can reach production in weeks.

Order Failure Fixes and Other Documented Agents

Totogi deploys agents per use case. The ones documented in public material include:

• Order failure remediation: detects orders that fail because of corrupted data, missing configuration or broken system links, then fixes them across billing, CRM, provisioning and catalog systems.
• Change request pipeline: five agents in sequence. A business analyst agent writes formal specs from loose requirements, an architect agent defines APIs and dependencies, a developer agent writes code, a QA agent checks it for best practice and security, and a tester agent writes unit tests. QA and test results loop back to the developer agent.
• Migration mapping: generates interface integration and data transformation code, as in the billing migration where 18 interfaces were mapped automatically.
• Network assurance: links network, customer and revenue data to find cells that look healthy but carry no traffic, and groups alarms into root causes.
• Sales support: connects call capture, CRM and CPQ so sales conversations flow into quotes and orders, and, at StarHub, suggests responses and products during enterprise sales calls.
• Welcome calls: an agent in Central America runs about 3,000 customer welcome calls a month and writes results back to operator systems.

Operators Approve Mappings and Change Limits

Operators decide which use cases go first, approve how the ontology maps to their systems and set what agents may change. The change request pipeline is described as needing minimal human intervention rather than none, and code still goes through the operator’s release process. Rios has said governance is the main reason operators hesitate to let agents act, which makes approval rules a planning item from day one.

Setup in Practice

Totogi’s published projects give a sense of timing: a CPQ integration in four weeks, a European cloud BSS live in eight weeks and the billing migration in two weeks. Each started with a single use case before expanding.

Multi-Year Deals Negotiated Directly With Operators

Totogi does not publish prices for BSS Magic. Deals are negotiated directly with operators, and the company has described several as multi-year engagements.

Applying Totogi’s Reported Savings to Sample Volumes

Without a price list, the useful numbers are the savings Totogi reports. These scenarios apply its published figures; the volumes in the second and third are our own illustrative assumptions.

• A billing migration: in Totogi’s North American case, annual system costs fell from $280,000 to $70,000, a saving of $210,000 a year. Any BSS Magic fee has to come in well under that figure, plus the consultant time saved by a 90% cut in project hours, to make the project pay.
• A welcome-call program: about 3,000 calls a month at five to eight minutes each is 15,000 to 24,000 minutes, or 250 to 400 hours of human agent time a month that the Central American deployment now handles with an agent.
• A change request backlog: if an operator handles 20 change requests a month at seven days each, moving to a few hours each frees roughly 140 days of elapsed waiting a month. Engineering effort still goes into review and release.

Other costs to plan for: your own BSS and IT staff time during ontology mapping, cloud consumption on AWS, and the internal work to set approval rules. Ask Totogi how pricing changes as you add use cases on the same ontology.

Totogi BSS Magic Compared With Amdocs aOS, Netcracker Agentic AI and Blue Planet

Telecom AI agents split into vendor suites from large BSS and OSS suppliers and overlay products such as Totogi that sit above several vendors.

Choose Totogi if your BSS comes from several suppliers and you want one layer above them. Choose a suite vendor such as Amdocs or Netcracker if most of your stack already comes from them. For network inventory and orchestration more than billing, Blue Planet is closer to the work. See more options in our AI agents for telecom guide, or look at Nokia Autonomous Network Fabric for network-side automation.

Tier-1 Operators With Mixed-Vendor BSS Stacks

• Tier-1 operators with multi-vendor BSS: the ontology is designed to sit above Amdocs, Ericsson, Huawei and Salesforce systems at once.
• Operators facing a billing or BSS migration: the published billing migration shows what automated interface mapping and testing can do to timelines.
• Teams drowning in change requests: the five-agent pipeline targets the slow loop of specs, code, review and testing.
• Operators with order fallout problems: order failure detection and repair is the first use case in the 2026 Southeast Asia deal.
• Companies already on AWS: the agents run on Amazon Bedrock, Step Functions and Lambda.

MVNOs and Price-List Seekers

• Small operators and MVNOs: Totogi’s published work is with Tier-1 operators, and buying is sales-led.
• Buyers who need a public price: Totogi shares pricing by quote.
• Operators standardized on one BSS vendor: that vendor’s own agents, such as Amdocs aOS, may fit more tightly.
• Teams wanting independent proof first: there are no public review-site ratings yet, and most results are vendor-reported.
• Non-telecom businesses: the ontology models telecom orders, services and networks only.

Customer Names, Targets and Outcomes to Confirm

• Vendor-reported results: nearly every figure comes from Totogi, often without the customer’s name. Ask for reference calls.
• Targets versus outcomes: the Southeast Asia figures for fewer tickets and faster repairs were stated as expected results in January 2026.
• Mapping effort: the ontology must be mapped to your systems, which needs time from people who know them.
• Governance: decide which actions agents may take on live billing and order systems, and how changes are rolled back.
• Naming: Totogi markets both BSS Magic and the Totogi Ontology; confirm which components your contract covers.

Seven New Ontology Deployments in September 2026

• On September 10, 2026, IT Brief reported that Totogi’s ontology went live in seven new deployments across five continents, with two expanding into multi-year engagements.
• On March 4, 2026, CEO Danielle Rios told RCR Wireless at MWC that nearly 10 Tier-1 operators use the ontology and described results at Zain Sudan and StarHub.
• On January 20, 2026, Totogi announced that a Tier-1 Southeast Asian operator with more than 10 million subscribers chose BSS Magic for its BSS in a multi-year deal.
• On February 19, 2025, Totogi said a Tier-1 North American operator finished a billing migration in two weeks using BSS Magic.
• In January 2025, Totogi said BSS Magic was in production ahead of MWC25, where it showed AI agents with AWS.

A Serious Look for Operators With Integration Backlogs

For a large operator with a multi-vendor BSS and a backlog of integration, migration or order-failure work, BSS Magic is worth a serious look. It scores 7.7/10 on our scale, which reflects quote-only pricing and the absence of public reviews more than doubts about the product. On autonomy and integration it is strong: agents write and test code for change requests and repair failed orders across systems from several vendors.

The published results are striking, from a two-week billing migration to a 97% cut in weekly alarm noise, but they are Totogi’s own numbers. Start with one scoped use case, measure it against your current cost and timeline, and ask for operators you can call before signing a multi-year deal.

Telecom IT Leaders’ BSS Magic Questions

How Much Does Totogi BSS Magic Cost?

Totogi does not publish prices. BSS Magic is sold on custom quotes, and the company has described several deals as multi-year engagements. Use the savings in its billing migration case, $210,000 a year in system costs, as a yardstick when weighing a quote.

Does Totogi BSS Magic Replace Amdocs or Ericsson Billing Systems?

No. It sits on top of existing BSS from vendors such as Amdocs, Ericsson, Huawei and Salesforce. It can help migrate between systems, as in the billing migration case, but the product itself is a layer above them.

Which AI Models Does BSS Magic Use?

The change request agents described in an AWS technical write-up use Anthropic Claude models through Amazon Bedrock, with AWS Step Functions and Lambda handling orchestration. The system keeps an audit trail of agent decisions and actions.

Which Operators Use Totogi?

CEO Danielle Rios has cited Zain Sudan for network fault detection and StarHub for enterprise sales support, and says nearly 10 Tier-1 operators use the ontology. Most other deployments are described by region rather than name.

Where Does Totogi BSS Magic Fit Less Well?

It is sold through scoped projects rather than self-serve, and it works once mapped to an operator’s systems. It is built for telecom, and agents act within the approval rules the operator sets, so people still review code and decide what agents may change.