A shipment lands short, late or damaged, and the exception gets read against the order and that supplier's delivery history before it's scored. Buyers decide the response; the workflow only makes sure the decision happens fast and with the history already pulled.
How it runs
ambiguousscoreddecided
Trigger
Delivery exception loggedWarehouse management
Extraction
Read the exception detaildelivery note, driver note, supplier email
Lookup
Check the order and supplier historySAP
Triage
Score severityagainst known supplier patterns
Rule
Confidence check
Branch
Escalate ambiguous cases to the buyer directly
Human gate
Buyer decision
System writesensitive
Update the order statusSAP
Outbound comms
Notify the account teamMicrosoft 365 and Outlook
Outcome
Exception resolved
Trigger
Extraction
Lookup
Triage
Rule
Branch
Human gate
System write
Outbound comms
Outcome
What it could return
Expediting fees and rush freight avoided each month when a short or late shipment gets a buyer's decision within the hour instead of the day.
$29,160per year, returned
A rough estimate until this is measured on your own numbers. Every input above is yours to change.
Systems touched
Agentic skills run
Where the human sits
Hold, expedite, escalate — a buyer picks one, and the choice is what actually changes SAP.
Confidence floor 70% — anything under that holds for a person instead of guessing.
Knowledge produced
This one doesn't produce any knowledge for memory to pick up.