Session Abstract

Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Christoph Adler

Christoph Adler is Head of Solution Consulting and Senior Solution Architect at panagenda, where he helps organizations understand what really shapes their users’ Microsoft 365 experience. His focus is digital experience monitoring: connecting endpoint, network and service data to explain why Teams, Outlook, SharePoint or Copilot feel fast for some users and slow for others. He also brings AI into the picture, connecting monitoring data to AI agents through the Model Context Protocol (MCP). Christoph has worked in enterprise IT since 2001 and joined panagenda in 2012. He regularly presents panagenda’s webinars and has spoken at conferences across Europe and the US.