<?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/01e2c6d750634c7f8d3c7e2d7813e993&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/01e2c6d750634c7f8d3c7e2d7813e993-fe49af66443fc831.gif</thumbnail_url><duration>318.246</duration><title>Why I Don&apos;t Recommend the Clio NetDocs Integration</title><description>In this video, I discuss the Clio NetDocs integration and why I don&apos;t recommend using it. While I appreciate Clio and attend Clio con every year, the integration has significant flaws, such as incorrect client IDs and missing matter descriptions. I suggest that instead of enabling the integration, users should manually link matters between Clio and NetDocs, as this allows for better organization. Additionally, I mention that other companies have developed their own integrations that might be worth exploring. My main action request is to reconsider turning on the Clio NetDocs integration due to its limitations.</description></oembed>