Book a call

Exception-handling agent for market communication

Market communication exceptions are cleared the same day. How it works at a regional utility with 400 exceptions a week.

Agent
Done
Awaiting approvalApproval by a colleague
Log

The target values we set for this process during the assessment and track in the monthly report:

63%of exceptions resolved by the agent without anyone touching them
0missed deadlines, because the deadline sets the order of work
9 minless handling time per exception

Where it gets stuck, what we build and what usually gets in the way

Tools and platforms: Microsoft Foundry, Azure Container Apps, Microsoft Fabric, SAP IS-U, Entra ID, Power BI.

Where it gets stuck

Every week, around 400 exceptions land on a team of six. Supplier switches get stuck, metering points don't match the address, and master data looks different on each side. The errors are almost always the same; only the cases are new each time. So each one is resolved by hand. If a deadline is missed along the way, the regulator gets in touch, and the team has to explain, yet again, why.

How we build it

Before we write a single line of code, we sit down with the team and write down how an exception is resolved. There are usually about a dozen ways. That is what the agent runs on. It reads the faulty message, checks metering point, address and master data against SAP IS-U, and picks the right correction path. Anything that doesn't need a master data change it handles itself. Everything else goes to a member of the team, with a proposed fix and the time left before the deadline. The deadline decides what gets done first. Every step is logged, and the team can stop the agent at any time.

What usually gets in the way

Writing down the correction paths takes longer than building the agent. That isn't wasted time: without those paths, the agent simply wouldn't know what to do.

The question we always getAsked by a market communication team leader
Only three of our colleagues know the correction paths by heart. What happens if one of them leaves?"

That's exactly why we write them down first, together with those three. After that they live in the agent and on one page of documentation. When one of the three goes on holiday, nobody notices any more.

Shall we talk about your first process?

In a Short Assessment we sit down with your business team and IT and look at one process together. You leave with a clear target design and an effort estimate we stand behind. Free of charge.

Business card of Piero Alessio, Managing Director