> 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/attendant-console-for-dialogue-cloud/dialogue-cloud.md).

# Attendant Console for Dialogue Cloud overview

Overview of Attendant Console for Dialogue Cloud.

Attendant Console for Dialogue Cloud is a web-based, cloud-hosted operator console for Dialogue Cloud environments. It is a supplemental solution on top of a Dialogue Cloud UCC and uses Dialogue Cloud capabilities such as routing, IVR, supervisor functions, reporting, wallboards, and related features.

<figure><img src="https://4184412221-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffsyg51MeZptkjIReLgC5%2Fuploads%2Fgit-blob-3d3c35a59e171047034489a497ee2305ebfe48b4%2Fattendant-console-dialogue-cloud-main-screen.png?alt=media" alt="Attendant Console for Dialogue Cloud main screen with queue, conversation, and contact panels"><figcaption><p>Attendant Console for Dialogue Cloud operator interface.</p></figcaption></figure>

{% hint style="info" %}
Attendant Console for Dialogue Cloud requires an Attendant Console for Dialogue Cloud license and a Dialogue Cloud UCC license.
{% endhint %}

## Feature areas

### Layout and access

Operators can use Attendant Console as a standalone web interface or embedded in Microsoft Teams. The console supports configurable layouts, multi-language use, and widgets.

<figure><img src="https://4184412221-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffsyg51MeZptkjIReLgC5%2Fuploads%2Fgit-blob-5b6c1a96dec9f72c723a51bb3487f74f37bf6d90%2Fattendant-console-dialogue-cloud-features.jpg?alt=media" alt="Attendant Console for Dialogue Cloud feature overview showing call handling and contact context areas"><figcaption><p>Feature areas available in Attendant Console for Dialogue Cloud.</p></figcaption></figure>

### Call handling

Operators can handle Direct Routing calls, answer and end calls, place calls on hold, resume calls, use the dial pad, view caller details, and use blind or consultative transfer options.

{% hint style="info" %}
Internal transfers require Enterprise Voice licensed users.
{% endhint %}

### Queue and directory context

Attendant Console for Dialogue Cloud uses Dialogue Cloud routing and shares configuration with WebAgent. Directory and contact context can include Microsoft Entra ID contacts, Microsoft Teams presence, personal contacts, group contacts, favorites, contact details, contact notes, and the Microsoft 365 Agenda widget.

### Reporting context

Attendant Console has dedicated reporting content. Use existing Atlas reporting pages for generic Power BI Template and Dialogue Insights concepts:

* [Set up the Power BI Template](/platform-administration/reporting-administration/reporting/set-up-power-bi-template.md)
* [Power BI Template data reference](/product-reference/reporting-and-power-bi/power-bi-template-data-reference.md)
* [Dialogue Insights](/use/monitor-and-report/dialogue-insights.md)

## Administration tasks

{% content-ref url="/pages/yF5PapPWJ5oDjSlyF2EO" %}
[Set up Attendant Console for Dialogue Cloud](/attendant-console/set-up-and-administer/setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/qDWyBMQjPLJD9B5XnfKT" %}
[Configure the admin portal](/attendant-console/set-up-and-administer/admin-portal.md)
{% endcontent-ref %}

## Use and troubleshoot

* [Use Attendant Console for Dialogue Cloud](/attendant-console/use/get-started.md)
* [Troubleshoot Attendant Console for Dialogue Cloud](/attendant-console/troubleshooting-and-support/troubleshooting.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/attendant-console-for-dialogue-cloud/dialogue-cloud.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.