The desktop companion application is a Windows backup client for Dynamics 365 Contact Center voice sessions, helping service representatives maintain active customer calls when the browser workspace freezes, reloads, or experiences connectivity problems.
The desktop companion application provides a Windows fallback for Dynamics 365 Contact Center voice conversations when the Copilot Service workspace web experience becomes unreliable. It is designed for customer service representatives who need to keep handling active calls during browser freezes, reloads, network latency, or related web-app disruption. Once installed and connected through the supported browser extension, the app can show the current environment, sign-in information, and ongoing calls. Representatives can move call handling into the desktop window while continuing their broader workflow in the browser. This arrangement reduces dependence on a single browser session without replacing the normal Dynamics 365 workspace.
Deployment uses a Microsoft-provided x64 MSI and requires the Microsoft Visual C++ Redistributable dependency identified by the official WinGet package metadata. Administrators can install the package interactively or through msiexec, then enable the Microsoft browser extension in Chrome or Edge and restart the browser. The Desktop companion application works alongside the web workspace so representatives can shift voice controls to the native client during web-side trouble. Settings expose microphone and speaker selection, language choice, test-call checks, and app version details. Microsoft also documents diagnostic-data controls, support-file generation, and a registry policy that can prevent representatives from manually updating the client.
The biggest benefit of the desktop companion application is call continuity when browser-side problems would otherwise interrupt a customer conversation. Representatives can keep essential voice handling available in a native Windows client, which reduces the need to abandon an active interaction while the web workspace recovers. Built-in mute, unmute, end-call, hold switching, audio-device selection, and test-call tools keep common recovery actions close to the agent instead of scattering them across troubleshooting steps. Browser-extension launch support also makes the fallback easier to reach from the normal workspace. For administrators, Microsoft provides diagnostic-data controls, support-file generation, and a registry setting that can limit manual updates, giving organizations more operational control over managed desktops. Because the app complements rather than replaces Copilot Service workspace, teams can preserve their established Dynamics 365 workflow while adding a dedicated path for voice resilience and selected screen-recording scenarios.
The desktop companion application can take over essential voice handling when the Copilot Service workspace freezes, reloads, or suffers network latency. Representatives can open the native client, keep an ongoing customer call visible, and continue key call actions while the browser recovers, reducing the risk that a web-side problem ends an active conversation.
During an active voice session, the desktop companion application provides controls to mute, unmute, and end the call without depending on the browser communication panel. Microsoft also supports switching between an active call and a call on hold, giving representatives practical control over the conversation when the web interface is impaired.
Settings in the desktop companion application list available microphone and speaker devices so representatives can select the hardware used for voice conversations. Microsoft also provides a Test Call option for checking whether the chosen microphone and speaker are working, which helps isolate device problems before or during customer-service work.
The native client integrates with Microsoft-supported Chrome and Edge extensions that can launch it from the browser workflow. After the desktop app and extension are installed and the browser is restarted, representatives can use the extension as another route into the fallback experience instead of relying only on a taskbar launch.
The desktop companion application displays the environment and sign-in information associated with the current session, along with ongoing calls. A message in the web communication panel can indicate that a call is being handled by the native client, helping representatives confirm which surface currently has responsibility for voice handling.
When troubleshooting is needed, the desktop companion application can generate support files from its menu for submission to Microsoft support. Microsoft also documents required and optional diagnostic-data categories, with optional diagnostic collection disabled by default, giving administrators and support teams a defined path for gathering evidence without relying only on verbal problem descriptions.
Administrators can configure the documented DisableUserUpdates registry value to stop representatives from manually updating the desktop companion application. The same policy also prevents users from manually configuring automatic startup through the app's update options, which gives managed environments tighter control over when client changes are introduced across representative desktops.
For supported Dynamics 365 Contact Center and Customer Service scenarios, the desktop client can participate in configured screen and audio recording workflows. Microsoft states that the app must be installed and running on the representative's computer for these recording scenarios, allowing authorized organizations to review interaction handling for quality, compliance, training, and operational analysis.
It acts as a Windows fallback for voice conversations when the web workspace has problems. Representatives can keep an ongoing call visible and use essential controls in the native client while the browser session recovers.
Microsoft distributes an x64 MSI that can be run interactively or through msiexec. The Microsoft Visual C++ Redistributable is a documented dependency, and the Chrome or Edge extension should be enabled before restarting the browser.
Yes. Microsoft documents mute, unmute, end-call, and active-versus-hold switching controls. Representatives can also view ongoing calls and confirm in the web communication panel when the native client is handling a call.
Yes. Settings let representatives select available microphone and speaker devices, and the Test Call option checks whether those devices are working correctly. Language selection and application version information are available in the same settings area.
Yes. Microsoft documents required and optional diagnostic-data handling, support-file generation, and a DisableUserUpdates registry policy. Setting that policy can prevent representatives from manually updating the client and manually changing its automatic-start configuration.
Comments