Feature request: Historical Agent Activity Timeline for Microsoft Teams Queues
Hi everyone, We're currently using the new Microsoft Teams Queues app for our IT Service Desk and are very pleased with the improvements Microsoft has introduced. One capability we feel is still missing is a historical Agent Activity Timeline. Today supervisors can only see an agent's current Opt-in/Opt-out status. There is no historical overview showing: When an agent opted in When an agent opted out Which agents were opted in at a specific moment Whether the change was made by the agent, a supervisor or automatically This makes it difficult to investigate: Missed calls Queue performance SLA deviations Staffing questions Incident investigations A simple historical timeline containing the timestamp, queue, agent and source of the status change would already provide tremendous value for supervisors and service desk managers. We've submitted this as a feature request through the Microsoft Feedback Portal: https://feedbackportal.microsoft.com/feedback/idea/2df346ee-bc89-f111-9b47-7c1e52444ef6 If you experience the same limitation, we'd really appreciate your vote. I'm also interested in hearing how other organisations deal with this today. Are you using manual checks, screenshots or another workaround? Thank you! Romain Weimer Head of ICT Operations and Support Witteveen+BosTeams Freezes ~90 seconds into a 1:1 Mac OSX
Teams video and audio starts freezing 90 seconds into a 1:1 call, and then it comes back to normal and wont happen again. This started about 3 weeks ago and it happens only during 1:1 calls wont happen when there are more then 2 people in a call. Mac OSX 26.5.1 (25F80) Teams Version 26149.1804.4788.5681
Stop Automatic Calling when Screensharing
I screenshare a lot in my position; I call the coworker (Phone/Headset) and train them on what I need them to look at. I am in a large office building, and the automatic calling of the receivers' PC is disruptive, as I do not was the whole office to hear my conversation or have people hear my trainee. I see no way to disable the team auto-call once I start to screen share or in the Options. All my coworkers feel this frustration as well. I do use the computer microphone/speaks aspect when working from home, but would disable it totally, if it would stop the auto-call. I do not want it to affect meeting invites to others, as others around the country can use their PC speak/microphone, if they want. Please advise.
How can I report an error in MS Teams documentation?
Hey all, how can I report an error that I noticed in MS teams documentation? On this site: https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-slovenia There is a LOA request that is named: "Letter of Authorization (LOA) for Slovania (all numbers) (v.1.0)". This is of course an error - it should say Slovenia, not Slovania. How do I report this to MSFT for checking and fixing the Learn docs? I cannot seem to edit or submit a PR for MS teams. Thanks! BR TimTeams for iOS (MAM only Call Identification)
In order of the implementation of O365/M365 and with it Microsoft Intune, Teams and Outlook for iOS has become the standard collaboration and mail clients on iOS devices for many customers today. This is due to the excellent user experience and the constant stream of new features implemented by Microsoft. From a security perspective, in addition to the provision on managed devices (managed by Intune), the secure use on unmanaged devices with MAM or App Protection Policies (APP) is a big argument for using Teams and Outlook for iOS. A big pain point for many users who use Teams and Outlook for iOS in an MAM-only setup (and for MDM setup with Intune too) is the missing caller identification of Exchange Online (EXO) contacts, when someone is calling via a cellular connection. Outlook for iOS supports a one-way contact export process whereby contacts from within Outlook for iOS can be exported into the personal (unmanaged) part of the native iOS Contacts app. This means a contact must first be imported into the users personal contacts directory of EXO and then exported from Outlook for iOS to the native (unmanaged) iOS Contact app in order to see who is calling. This functionality enables Caller-ID, iMessage, and FaceTime integration for users’ Outlook contacts. The exported Outlook contacts are considered unmanaged and are accessible by unmanaged, personal apps. Especially for European customers who are subject to GDPR compliance, this is a no go, as personal data and company data must not be mixed. The unintentional outflow of contact data worthy of protection to commercial platforms, such as WhatsApp or Google, and the unintentional synchronization of address books with social media apps, represents a significant GDPR risk. Although the user's personal EXO contacts can be synchronized, there is currently no option to synchronize the GAL. Furthermore, there is currently no provision in Teams and Outlook for iOS to synchronize the GAL cyclically. The user has to add a GAL contact to his personal contacts as described above and then within the Outlook for iOS app export the contact to his native iOS contacts app to be able to see who is calling. To meet the GDPR compliance, we need to prevent the contact export. So this is not a solution. The question to ask is: Why does a user need to export a GAL/personal contact to their native iOS Contact app? There are already several paid app solutions that close exactly this gap (ebf Contacts, Secure Contacts, etc.) which offer more or less the same range of functions. The app builds a container and downloads the managed address books (GAL, personal) of the user and then enables the resolution of the CallerID or identification of the caller via the so-called Apple CallKit integration. Apple has been offering the so-called CallKit integration for years. With CallKit you can integrate your calling services with other call-related apps on the system. CallKit provides the calling interface, and you handle the back-end communication with your VoIP service. For incoming and outgoing calls, CallKit displays the same interfaces as the Phone app, giving your app a more native look and feel. CallKit also responds appropriately to system-level behaviors such as Do Not Disturb. In addition to handling calls, you can provide a Call Directory app extension to provide caller ID information and a list of blocked numbers associated with your service. When a phone receives an incoming call, the system first consults the user’s contacts to find a matching phone number. If no match is found, the system then consults your app’s Call Directory extension to find a matching entry to identify the phone number. This is useful for applications that maintain a contact list for a user that’s separate from the system contacts, such as Teams and Outlook for iOS. For example, consider a user who is a colleague to Jane, but doesn’t have her phone number in their contacts. If the Teams or Outlook for iOS app has a Call Directory app extension, which downloads and adds the phone numbers of all of the user´s colleagues. When the user gets an incoming call from Jane, the system displays something like “(App Name, e.g. Outlook) Caller ID: Jane Appleseed” rather than “Unknown Caller”. The effort to integrate the Call Directory Extension is minimal and would solve many pain points from both a security and user experience perspective. Apple has documented CallKit excellently on the developer site: https://developer.apple.com/documentation/callkit With the possibility of using Apple CallKit in combination with Teams and Outlook for iOS and the contact synchronization (personal/GAL) of a managed EXO mailbox, the use of M365 in a BYOD scenario for customers Blue Collar workers will massively increase. Furthermore, the use of contact synchronization is then also possible for devices managed by Intune. This creates an outstanding user experience while increasing user adoption! This article was also published as feedback in the Outlook Forum for iOS: https://feedbackportal.microsoft.com/feedback/idea/a80414f4-9598-ed11-a81b-000d3ae32cd0 There are already other requests within the Microsoft community that I would like to link here: @PatrickF11 : Outlook for iOS + Caller Identification - Microsoft Community Hub Daniel Huttenlocher: https://feedbackportal.microsoft.com/feedback/idea/bbfc8763-da97-ed11-a81b-000d3ae32cd0Using the Small Window for Incoming Teams Calls
A recent improvement is the introduction of a small window for incoming Teams calls. It doesn’t sound like a great step forward, but switching to the small window is a surprisingly useful step. The sad thing is that many users won’t know that the option to switch exists because it’s buried in Teams settings. If you’re a busy person who takes lots of Teams calls, switching is definitely recommended. https://office365itpros.com/2026/06/30/incoming-teams-call-window/How much should Teams presence influence call routing
One thing I've noticed recently is that many Teams Phone environments still treat presence as a destination state rather than a routing input. A typical flow might look like: Caller selects an option Call is transferred User is unavailable Caller ends up in voicemail or another queue Technically the routing worked. From the caller's perspective, it often didn't. I'm curious how others are approaching this. Are you using Teams presence as part of your call-routing logic? For example: Available → transfer immediately Busy → offer an alternative path In a meeting → capture context Offline → route elsewhere Or are traditional queues and escalation paths still sufficient for most scenarios? Interested to hear what people are doing in real deployments.
external calls with call queue or resource account.
Hi. I am setting up a call queue and an auto attendant for my customer service department. I already receive the calls and they are forwarded to my agents as I have configured in the call queue. My problem comes with the outgoing calls, I don´t want the customer service users to call directly. I want them to call through the resource account. I can do this by selecting the resource account in the teams (see image) I need that the default option is always the resource account or a way to make that when they call always do it through the resource account or the same call queue. Is it possible?
Seeking Solutions for Delayed Voicemail Connection in Microsoft Auto Attendant
Hello Community, I am encountering an issue with Microsoft Auto Attendant where there is a noticeable delay (approximately 5 seconds) after the greeting message and before the call is connected to the shared voicemail box. This delay occurs right before the voicemail tone prompts the caller to leave a message, leading to confusion and a less professional experience. Here are the specifics of my setup: Auto Attendant is configured with a greeting message. Calls are intended to be forwarded to a shared voicemail box via an MS365 Group. The system is set to skip the voicemail system notification. The greeting message is an uploaded audio file, not text-to-speech. Despite the setup, there is an awkward silence after the greeting and before the voicemail tone. I have attempted to find solutions, noticing that others might have faced similar issues, yet a clear resolution or workaround seems elusive. Has anyone encountered this issue and found a way to minimize or eliminate this delay? Any suggestions or insights into settings or configuration changes that could improve this situation would be greatly appreciated. Thank you for your help!
