<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/596df6cf06c54121b8a50d3ae3a8d22f&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/596df6cf06c54121b8a50d3ae3a8d22f-1e2e90226163a931.gif</thumbnail_url><duration>299.075</duration><title>HEXALOG Exception Handling with a Control Tower - Prototype.</title><description>This Loom prototype explains how Hexalog can automate exception flow handling for shipments that get stuck. The author describes reading public sources, identifying that last mile already manages exceptions but relies on people to open multiple systems and lose 2 to 3 hours each time, and then building a control tower dashboard for scaling issues. They use a taxonomy to prioritize exceptions based on frequency and money involved versus impact if wrong, an exception module with likely root causes, evidence trails, confidence, SLA at risk, and recommendation plans with boundaries for six smaller agents. The loop includes approval, execution with verified outcomes, evaluation using eight parameters where human override rate is a fail criterion, scenario simulation, and an estimated ROI of saving 230 hours and 4.2 lakhs per 100 cases, with progressive autonomy from observe to optimize.</description></oembed>