From a delayed material to an approval-ready recovery plan.
This application family was built around a common supply chain problem: the first signal of a disruption may arrive in an inbox, while the operational effect is spread across supplier, material, production and customer records. The system uses several bounded agents to assemble that picture without giving software authority to make a commitment.
The problem was larger than a single prompt.
Purchasing requests and supplier updates entered through a shared inbox.
The consequence of a delay was not visible in one place.
Staff had to trace the exposure before they could compare recovery actions.
Any supplier, production or customer commitment still needed accountable approval.
A useful system had to fit the work and its limits.
- Keep Outlook and Excel in the workflow rather than forcing an immediate platform replacement.
- Let a manager ask a spoken question and receive a traceable operational briefing.
- Apply known routing rules before asking AI to interpret an unresolved request.
- Prepare recovery options as an editable action packet for human review.
Each agent has a separate job.
A realtime voice agent handles the spoken briefing. Routing and recovery agents collect evidence, trace impact and prepare options so a person can make the operational decision.
Routing agent
Reads incoming purchasing work, applies deterministic company rules first and sends only unresolved cases for constrained AI review.
Impact-tracing agent
Connects the supplier or material issue with relevant production and customer records, keeping the evidence attached to the briefing.
AI voice briefing agent
Lets the manager ask follow-up questions in a browser-based voice cockpit, with clear disclosure that the conversation is with AI.
Recovery agent
Compares available actions and compiles an approval-ready packet. It can prepare the choice, but it cannot make the commitment.
One traceable path from input to review.
- 01Ask the AI voice agent about a delay or exposed commitment
- 02Trace the effect through materials, production and customers
- 03Compare recovery scenarios and purchasing actions
- 04Approve, edit or reject the action packet
Technology chosen around the operating environment.
PowerShell 5.1 with Outlook and Excel COM on managed Windows computers.
OpenAI Realtime API for voice and the OpenAI Responses API for bounded reasoning tasks.
WebRTC conversation in a browser interface with written evidence and action details.
Windows DPAPI for machine-level protection of sensitive local configuration.
A browser-based voice cockpit deployed on Render, separate from the restricted desktop workflow.
Evidence for the next decision, not a promised result.
From the first disruption signal to a usable view of affected work.
How long routine and exceptional purchasing requests wait for an owner.
Time and rework required to assemble options for approval.
Actions that reach review with their evidence, assumptions and accountable owner intact.
This page describes a working application family and its control model. Client names, operating data and identifying details are intentionally omitted. No financial savings or production outcomes are claimed here.
Start with the work, the constraint and the decision owner.
We can map the process, decide which agents would help and define a first release that is small enough to evaluate.
Discuss the problem