video1.0<iframe src="https://www.loom.com/embed/2244d1a5bb9743449cfefd51267136d8" frameborder="0" width="1152" height="864" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>8641152Loomhttps://www.loom.com8641152https://cdn.loom.com/sessions/thumbnails/2244d1a5bb9743449cfefd51267136d8-0660b9b77c7e3e1b.gif180.903This Loom explains how an agent handles multiple alerts from three meetings by identifying a single root warehouse batch issue and creating tickets and alerts from it. The agent maps the related problems to one issue, generates tickets, and sends alerts, then follows up to check whether the batch is fixed. It uses a listener that monitors statuses such as in progress or blocked and keeps prompting until resolution, with the follow-up interval set to 10 seconds during a demo. If it is not fixed by the end of the day, the team can mark it as a blocker or discuss it in the next meeting, and the process stops once the meeting transcription indicates the issue is resolved.