> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/attendant-console/shared-components/desktop-integrator-transition.md).

# Desktop Integrator and ACS transition

Support existing Desktop Integrator deployments while transitioning Attendant Console call handling to ACS.

{% hint style="warning" %}
ACS is the current and preferred path for Attendant Console call handling. Desktop Integrator is transition and existing-deployment support material. The source warns that Desktop Integrator no longer functions as expected with the new Microsoft Teams client and that the Desktop Integrator option is planned for removal from preferences.
{% endhint %}

Desktop Integrator is a local Windows desktop application that bridges Attendant Console and the Microsoft Teams desktop application. It was used to reduce the number of user actions required when answering or starting calls.

## When to use this page

Use this page only when supporting an existing Desktop Integrator deployment or transitioning users from Desktop Integrator to ACS.

Do not enable Desktop Integrator when ACS is enabled for the same operator workflow.

## Requirements

* Windows 10 or Windows 11.
* Microsoft Teams desktop client.
* Local installation rights. Administrative rights may be required depending on endpoint policy.
* Attendant Console opened as a Microsoft Teams app, as a Microsoft Teams pop-out window, or in a browser window.

Desktop Integrator cannot interact with browser-based Microsoft Teams.

## Install Desktop Integrator

1. Download the Desktop Integrator setup MSI:

   `https://delivery.anywhere365.io/deployment/msteams/Anywhere365IntegratorSetup.msi`
2. Run the setup.
3. Approve the installation if administrative elevation is required.
4. After setup completes, use the displayed test page to validate that Desktop Integrator can start.

## Allow the browser protocol handler

When Desktop Integrator is used for the first time, the browser can ask whether the local protocol handler may open Desktop Integrator. Select the option that always allows the handler for this site so the bridge can start from Attendant Console.

## Enable Desktop Integrator in Attendant Console

1. In Attendant Console, open the user menu.
2. Select **Preferences**.
3. Use **Test** to validate that Desktop Integrator is installed and that the Microsoft Teams desktop client is detected.
4. Enable the Desktop Integrator option only if ACS is not selected.

## Transition to ACS

1. Notify operators that ACS will become the call-handling path.
2. In **Preferences**, clear the Desktop Integrator option.
3. Enable ACS.
4. Confirm microphone access in the browser.
5. Validate inbound queue-call handling and outbound calling.

## Uninstall Desktop Integrator

Remove Desktop Integrator from **Apps & features** in Windows Settings, or run the setup again and choose the uninstall option.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/attendant-console/shared-components/desktop-integrator-transition.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.