Planned for release on September 10th, 2025.
This technical release bulletin provides an overview of the new features and enhancements for the indicated release of the Attendant Console for Microsoft Teams.
This bulletin is aimed at partners, not end-users. After the release has been deployed, Attendant Console users will see a one-time What’s new popup highlighting the most important functional changes. The What’s new information, relevant to the attendant user, will also be made accessible from the Help menu in the Attendant Console.
139509: Teams Attendant could not complete warm transfer to mobile Teams client on iOS in same Microsoft 365 tenant.
There was an issue where a warm transfer could not (fully) complete if transferring to a Teams client (C-party) on iPhone if the C-party was in the same Microsoft 365 tenant as the Attendant Console queue and B-party. We have made changes to an internal call state during transfer (inqueue) in our application and did not find this issue any more during testing.
139519: Teams Attendant call randomly went on-hold or disconnected.
In a seemingly random scenario with more then one Attendant Console users monitoring a queue, calls being answered by an operator would sometimes be put on hold or even disconnect mid-call (could happen after just seconds or several minutes). We could (sometimes) replicate this with a specific order of manually picking a call from queue before it was being hunted to an operator as a second operator becoming available during that call state. This resulted in the call registering a wrong inqueue state resulting in escaping to an overflow destination midway through the call. We have adapted our software to more rigorously set the call states during scenarios like these.