<?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/6402a0eef361479a8539183c0a576eb3&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/6402a0eef361479a8539183c0a576eb3-ef2a8bfebd8cc0b6.gif</thumbnail_url><duration>180.006</duration><title>contract-signing</title><description>This Loom explains the logic for automated follow-up emails tied to opportunity stage changes based on whether a proposal is signed. It describes moving to the proposal view opportunity stage and sending a follow-up email, then waiting two days to check the status of the lead. The workflow includes if else branches that duplicate logic to handle cases when the opportunity is not found or the status is not signed. It notes the need to remove duplicated segments and instead move unsigned opportunities to the later stages to respect boundaries with leads, sending either a nurture email or a configurable follow-up email.</description></oembed>