<?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/ef3c232f71c4436d83221f2b1b6aa000&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/ef3c232f71c4436d83221f2b1b6aa000-01b2f7f860343678.gif</thumbnail_url><duration>219.74</duration><title>[GA] Service Level Overbooking in Availability Reports</title><description>This Loom explains how service level overbookings work in the current implementation within the Availability and Occupancy Report. Users access it via the Availability tab and set limits using the Adjust Availability button, with initial support only for Start and End date ranges. The limits can be negative to remove physical rooms from being sold, and the total cap is calculated by adding or subtracting the cap to the number of free physical spaces, with the hotel stopping further reservations once the overall limit is reached. Unpicked blocks also count against the overbooking limit, and the report shows a line item indicating how many unpicked block reservations reduce availability.</description></oembed>