> 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/readme.md).

# Attendant Console

Set up, use, support, and reference Attendant Console for Dialogue Cloud or Microsoft Teams.

Attendant Console is a web-based, cloud-hosted operator console for handling voice calls from a single browser-based interface.

## Choose a product track

| Track                                                                                                                | Use this track for                                                                                                                             | License note                                                                       |
| -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| [Attendant Console for Dialogue Cloud](/attendant-console/attendant-console-for-dialogue-cloud/dialogue-cloud.md)    | Customers who use Attendant Console as a supplemental operator console for an existing Dialogue Cloud environment.                             | Attendant Console for Dialogue Cloud and Dialogue Cloud UCC licenses are required. |
| [Attendant Console for Microsoft Teams](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md) | Existing customers who use Attendant Console with Microsoft Teams calling, Microsoft 365 presence, and Microsoft Teams call-routing resources. | An Attendant Console for Microsoft Teams license is required.                      |

{% hint style="warning" %}
**Attendant Console for Microsoft Teams lifecycle notice**: Attendant Console for Microsoft Teams is in End-of-Sale. Existing customers can continue to use the product and receive support. License renewal remains available until December 2026, and End-of-Renewal is scheduled for December 31, 2026.
{% endhint %}

## Follow the Dialogue Cloud journey

1. [Review the product overview and reference](/attendant-console/attendant-console-for-dialogue-cloud/dialogue-cloud.md).
2. [Set up Attendant Console for Dialogue Cloud](/attendant-console/set-up-and-administer/setup.md).
3. [Configure the admin portal](/attendant-console/set-up-and-administer/admin-portal.md).
4. [Get started with call handling](/attendant-console/use/get-started.md).
5. [Troubleshoot Attendant Console for Dialogue Cloud](/attendant-console/troubleshooting-and-support/troubleshooting.md).

## Follow the Microsoft Teams journey

1. [Review the product overview and technical reference](/attendant-console/attendant-console-for-microsoft-teams/microsoft-teams.md).
2. [Set up Attendant Console for Microsoft Teams](/attendant-console/set-up-and-administer-1/setup-and-consent.md).
3. [Create Attendant Console queues](/attendant-console/set-up-and-administer-1/create-queues.md).
4. [Get started with call handling](/attendant-console/use-1/get-started.md).
5. [Review limitations and troubleshoot issues](/attendant-console/troubleshooting-and-support-1/limitations-and-troubleshooting.md).
6. [Review compliance and support guidance](/attendant-console/compliance-and-reference/compliance-and-technical-reference.md).

## Shared components and reporting

Use [Azure Communication Services](/attendant-console/shared-components/azure-communication-services.md), [Microsoft Teams app deployment](/attendant-console/shared-components/deploy-teams-app-manifest.md), and [Desktop Integrator transition guidance](/attendant-console/shared-components/desktop-integrator-transition.md) for components shared across product tracks.

For dedicated Attendant Console reporting, start with [Attendant Console reporting](/attendant-console/reporting/reporting.md).


---

# 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/readme.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.