video1.0<iframe src="https://www.loom.com/embed/3616434d9396433f8a592078b24c781f" frameborder="0" width="1152" height="864" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>8641152Loomhttps://www.loom.com8641152https://cdn.loom.com/sessions/thumbnails/3616434d9396433f8a592078b24c781f-014aa2a6decdffb1.gif172.629This Loom explains how the system routes a high-priority lead from Slack to HubSpot while preventing duplicate company records. The presenter shows that reps can act in real time via Slack, but HubSpot also reflects the opportunity score so teams can still follow up if they miss the Slack message. The key decision was handling the same company triggering multiple times by checking the company domain first to either create or update the existing record. After testing by intentionally running the process twice, the webhook execution resulted in no new duplicate records and kept HubSpot data current.