back_office_ops · energy · workflow

Totogi automates BSS change request processing from 7 days to hours using Amazon Bedrock multi-agent framework

Telecom BSS stacks consist of hundreds of applications from disparate vendors that are difficult and costly to integrate, relying on scarce specialized engineers. Each change request required thorough impact analysis and multiple rounds of coding, testing, and reconfiguration, while development cycles for new features often took months.

How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Change request initiated
A change request enters the multi-agent framework for fully automated processing.
Tools used
Amazon BedrockAWS Step FunctionsAWS LambdaAnthropic ClaudeRAG
Outcome

The BSS Magic multi-agent framework reduced change request processing from seven days to a few hours, and the automated testing framework achieved 76% code coverage, consistently delivering high-quality telecom-grade code with minimal human intervention.

Results
Time savedfrom seven days to a few hours
Volume76%
Source

https://aws.amazon.com/blogs/machine-learning/how-totogi-automated-change-request-processing-with-totogi-bss-magic-and-amazon-bedrock?tag=soumet-20

How we source this →

Grounding & classification
Source type: platform led case
26 fields verified against source quotes.
agentic workflowai agentcode generationmulti agent workflowragpolicy documentmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwaretelecomautomation ratecycle time reductiontime savedplatform led caseback office opsquality assuranceagentic task execution