Dear Anywhere365 Customer & Partner,
Our apologies for the delay in the update, but due to the complex nature of this issue it has taken longer than expected.
We would like to provide you with an important status update regarding the Desktop Integrator with an statement from our Product Owner.
Current Issue:
Although we have our test tenant running on a Beta ring and by having that we get deployed early versions of Teams, we have been surprised by the changes Microsoft has made in the latest versions of the Teams client. Specifically, the custom JavaScript function "window.open" is no longer supported, and there was no active communication on that change. We were using that function to connect to the Desktop Integrator when the Attendant Console is used in Teams.
Investigation and Impact:
Before the problems with the Desktop Integrator with the current Teams client arose, we had already initiated a process to determine the impact of the new Teams Preview client on various aspects, including the operation of the Desktop Integrator. However, due to the premature status of this new client and the limited information available, we have not yet been able to conclude on the possible integration with this new client.
Development and Release Plan:
Earlier this year, we started the development of bringing ACS (Azure Communication Services) into the Attendant Console to handle calls independently of the Teams client. The situation with the Desktop Integrator has urged us to expedite the development and release of this functionality.
Expected Release:
Our aim is to have a new release of the Attendant Console for Teams ready for release on the last week of August 2023. This new release will include all the new functionality of MT2023.03 together with ACS as MT2023.04.
New Functionality with ACS:
In this first version of the Attendant Console for Teams with ACS, we will provide the following features:
• Handling incoming calls in the queue.
• Direct and Consultative (cold and warm) transfers.
• Outgoing calls from the Attendant console.
• Changing the presence of Agents to Busy on a Call when handling Attendant Console calls.
• In addition to these call-related functions, all other non-call-related functions, such as contact search, callback notes, widgets, etc., will also be available.
Behavior Changes with ACS:
With the introduction of ACS, some changes in call handling behavior should be noted:
• ACS is mainly for handling calls picked up from the queue and not personal calls. A distinction will be made between queue calls, which will be handled in the Attendant Console, and personal calls, which will be handled in the Teams client.
• The Teams client will still need to be active to participate in chats and meetings, for presence, and for personal calls.
• When an agent is set to Busy in a Call due to handling a call in the Attendant Console, this status can be overruled by setting the presence in Teams itself.
• Deploying ACS will require customers to create a connection string in their Azure tenant, which will be configured in the Admin portal of the Attendant Console. Additional consent will be needed for this configuration.
GoLive and Release Date:
The procedure and manual for the additional ACS configuration will become available on GoLive prior to the actual release. For the exact release date, please keep an eye on our status page.
We understand the effect this has on your daily operations and are aware that the timeline towards the resolution is longer than we would have expected and liked to have this complex issue resolved.
We appreciate your understanding and patience as we work to resolve this issue and bring the enhanced functionality of Attendant Console for Teams with ACS as soon as possible.
Thank you for your continued support and cooperation.
Posted Jul 24, 2023 - 09:25 UTC