<?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/1712c6673f384c6eb40ea92cde649eb2&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/1712c6673f384c6eb40ea92cde649eb2-84925dc050b8e7da.gif</thumbnail_url><duration>273.033333</duration><title>Creating an agent from scratch</title><description>This Loom explains how Lakeshore Community Bank builds and launches a debit card customer service agent from scratch. It starts with a blank agent named Lakeshore card services, sets the prompt to guide lost or stolen card reporting, attaches the Freeze a debit card tool, and adds Lakeshore’s card security policy as knowledge. The agent is connected to Lakeshore’s main branch phone number for calls and texts, plus a web chat widget limited to Lakeshore’s domain and API chat for the mobile app, then dispositions are defined to track outcomes. It includes evaluation using simulated customer test cases and publishes through environments to production, where version 1.0.0 is marked live and described as answering on the bank’s branch number.</description></oembed>