video1.0<iframe src="https://www.loom.com/embed/2ef134c811764d538c73ff2252c60e97" frameborder="0" width="1280" height="960" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>9601280Loomhttps://www.loom.com9601280https://cdn.loom.com/sessions/thumbnails/2ef134c811764d538c73ff2252c60e97-d75531ecb0959259.gif175.403This Loom explains how the team built a trustworthy deal health status by combining related features like quiet-deal alerts and on-hold tracking. The speaker shows a pipeline view where deals sorted by status surface items that have not moved in 12 days, and a separate flow for marking a deal on hold instead of guessing why it is quiet. They illustrate flow two by opening a deal, marking it on hold for a client budget cycle date such as 15 August, and then observing the status change and movement in the list. Flow three switches to Ananya’s view, where her team’s deals are visible at a glance, and notes that documents and reassigning deals remain attached to the same deal record alongside status and history.