<?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/e87023ceabfb4ec19e8b4ab8dfe74473&quot; frameborder=&quot;0&quot; width=&quot;1620&quot; height=&quot;1215&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1215</height><width>1620</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1215</thumbnail_height><thumbnail_width>1620</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e87023ceabfb4ec19e8b4ab8dfe74473-8d5ef225019e3a65.gif</thumbnail_url><duration>230.911</duration><title>CloseBot Should Check Assigned User Availability</title><description>This Loom explains why CloseBot should check availability based on the user assigned to a lead even when using round robin calendars in HighLevel. In the example, the lead is assigned to Joshua Cooper, but Joshua’s staff availability shows only on Wednesdays when the calendar is set to book with the assigned user. The presenter demonstrates that toggling from “not always book with the contacts assigned user” (which shows everyone’s availability) to “always book” (which filters to Wednesdays only) aligns scheduling with lead assignment. They also note this helps in cases like post-webinar self booking to avoid dynamically displaying each user’s individual calendar for every lead.</description></oembed>