<?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/c517195cbbee4f679782cb8cd19d8a92&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c517195cbbee4f679782cb8cd19d8a92-06cd99ebe33a94f4.gif</thumbnail_url><duration>379.88</duration><title>Introducing Processes for CSM Workflows</title><description>This Loom introduces Processes as a major improvement to Impact Pilot, addressing feedback that impact drivers were too complex and lacked clear visibility into what is next for CSMs. It shows how to create a recurring annual process for a customer segment, including defining activities from the library such as 4 check-ins per year (every 12 months), one QBR annually, and sending goodies with detection prompts and reminders 30 days before year end and 7, 14, or 14 days before specific periods if not completed. The Loom then demonstrates how processes are automatically tracked based on HubSpot activity, with completed items turning green and examples of check-ins and value communicated during a QBR being auto-completed. </description></oembed>