<?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/61259d4455ff4db8a9509c3b348e6892&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/61259d4455ff4db8a9509c3b348e6892-511a4709280c0a54.gif</thumbnail_url><duration>82.491</duration><title>ArcVault Triage | Loom - 13 May 2026 | Lynn Haydar</title><description>This Loom explains a project that automatically classifies, enriches, and routes inbound customer support messages using AI. It describes a separation-of-concerns file structure with distinct components for data, prompt design, API call, routing logic, and orchestration. The prompt design specifies a clear role, compiles with allowed value constraints, and uses two few-shot examples for the toughest edge case, with temperature set to zero for consistency. Routing is handled with pure Python for deterministic, testable behavior, and the results.json output contains five fully structured records ready for a downstream team.</description></oembed>