<?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/bdf614f455da4ff7bdb0f944e1edb5a0&quot; frameborder=&quot;0&quot; width=&quot;1870&quot; height=&quot;1402&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1402</height><width>1870</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1402</thumbnail_height><thumbnail_width>1870</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bdf614f455da4ff7bdb0f944e1edb5a0-83ba405b00011522.gif</thumbnail_url><duration>180.776</duration><title>Moving Hotel Deposits for Room Changes</title><description>This Loom explains how to handle hotel rebooking when the same room type with the same price is split between different views. The hotel originally booked for six nights but the first two nights have a sea view and the remaining nights a pool view, requiring the guest to be moved, so the client opted to upgrade. The author notes the original booking included a 50 percent deposit and now needs to transfer that deposit data from the original room to the confirmed new room type within the system. They describe the current process as labor intensive and suggest improving it with an alert to move payments automatically when the hotel and room context match.</description></oembed>