<?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/c602d78063304127b972d069ef62c53b&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/c602d78063304127b972d069ef62c53b-b93f13cbbb72bab2.gif</thumbnail_url><duration>4798.033333</duration><title>Agentic AI for Support, Modal, Cadence</title><description>This Loom discusses how to implement agentic AI to handle support ticket escalations inside Modal, using tools like Cadence and Modal’s MCP capabilities. The team agrees a practical first step is enabling an AI to run tier one escalation work in a human in the loop flow, then iterating based on logs of what the agent needs from humans, with the goal of reducing support load and improving response time and quality. Key constraints include Modal workflow access being limited via current tokens, and the need to manage authorization and access to sub accounts via stored refresh and access tokens on a VPS using a dedicated agency admin email. The discussion also covers the current state of Modal MCP connectors, which exist but are private, and plans to share connector details for a safe demo in a test environment.</description></oembed>