<?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/dd6190df970c4261912262e8d22362a8&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/dd6190df970c4261912262e8d22362a8-a6bf8887475e0a12.gif</thumbnail_url><duration>3303.36</duration><title>Connect Lone Wolf Transact to Command ✅</title><description>Today I walked you through connecting Lone Wolf Transact to Keller Williams Command, and how to replace DocuSign eSignature for signatures. I shared that DocuSign will shut down on 7-14-26, and you can start using Lone Wolf now, with an office 30 day sink that will pull signed DocuSign files into our office Google Drive. From the office perspective, I only use Lone Wolf for e signatures and then turn completed documents into Command. I showed the full workflow, including creating an opportunity, syncing with the e sign provider, signing in Transact, and uploading back to Command. Action requested, please use agent.kw.com to log into Command and connect your Lone Wolf account in Settings.</description></oembed>