<?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/b27537358c804411968ff79d663382d9&quot; frameborder=&quot;0&quot; width=&quot;1152&quot; height=&quot;864&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>864</height><width>1152</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>864</thumbnail_height><thumbnail_width>1152</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b27537358c804411968ff79d663382d9-00001.gif</thumbnail_url><duration>262.572</duration><title>Using conditional approvers to automate escalation </title><description>In this video, I will demonstrate how conditional approvers in Juro can automate escalation while maintaining a safe self-serve motion. This means that end users, such as sales reps, can create, populate, and send contracts for signing without involving legal, unless certain triggers are activated. I will show you how these triggers are built into the template and will happen automatically. Additionally, I will explain how negotiations outside the pre-approved clause language can trigger legal involvement, ensuring that legal is included when necessary. By using conditional approvers, we can reduce the number of legal touchpoints in a contract&apos;s lifecycle and streamline the negotiation process.</description></oembed>