<?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/5cbf905383d14e889fe8777e54a5604f&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/5cbf905383d14e889fe8777e54a5604f-46d22f8a78a32ca5.gif</thumbnail_url><duration>138.3804</duration><title>Identifying Customer Back-and-Forth Interactions for Improved Support</title><description>In this video, I demonstrate how to identify customer tickets that may be caught in excessive back-and-forth communication with agents. Specifically, I&apos;m focusing on unsolved tickets that have had five or more responses, as this could indicate an issue. I’ll be adding a widget to my dashboard to track these tickets and ensure they are highlighted for visibility. Additionally, I want to set up notifications for when these situations arise, so we can take timely action. Please pay attention to this process and implement similar tracking in your own dashboards.</description></oembed>