{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/e394aa8bf0a54e37a304c658064814a0\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/e394aa8bf0a54e37a304c658064814a0-6c0298ca3aade8db.gif","duration":82.866667,"title":"Keep Email Internal Threads in One Place","description":"This Loom explains how internal threads in Customer keep email context when involving non-support teams like finance. Billy shows a conversation with Jerome about a building question and adds an internal thread to send the details to finance instead of moving the exchange to Slack or separate email. He notes that finance can reply directly within the Customer thread so the entire back and forth stays in one place. The goal is to resolve customer issues faster and provide 360 degree visibility for support."}