> 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/troubleshooting-and-support/troubleshooting.md).

# Attendant Console for Dialogue Cloud troubleshooting

Troubleshoot Attendant Console for Dialogue Cloud sign-in, missing queues, outbound calls, and Teams transfers.

Use this page to resolve common Attendant Console for Dialogue Cloud user issues.

## Sign-in or access fails

Attendant Console for Dialogue Cloud uses Online/SSO named authentication.

If you cannot sign in:

1. Confirm that you are using the same Microsoft credentials you use for WebAgent.
2. Confirm that you are opening the Attendant Console for Dialogue Cloud URL:

   ```
   https://dr-attendant.anywhere365.io/
   ```
3. Contact your administrator to confirm that your user account has an Attendant Console license and the required access.

## Queues are missing

If expected queues are not available in **Preferences** > **Queues**:

1. Confirm whether you need the queue under **Joined Queues** or **Monitored Queues**.
2. If you are a formal agent, select the UCC in **Joined Queues**. Formal agents are not automatically included.
3. If the queue is still missing, contact your administrator.

## Outbound calls fail

Use E.164 formatted numbers for outbound PSTN calls, for example `+31201234567`.

If outbound calls still fail:

1. Open **Preferences**.
2. Select **Conversation**.
3. Confirm that **Calling Identity** or **Caller ID for outbound calls** is set to the correct UCC or caller ID.
4. If the setting is missing or calls still fail, contact your administrator.

The UCC may require the correct Dialogue Cloud Integration skill configuration.

## Transfer to a Teams user fails

Attendant Console for Dialogue Cloud can transfer queue calls to an Enterprise Voice user or to an external E.164 formatted phone number.

If transfer to a Teams user fails, contact your administrator to confirm that the Teams user has the required license.

## Signing out does not stop Teams calls

Signing out of Attendant Console does not sign you out of Teams. Teams presence and joined queues can still recognize you as available for calls.

To stop queue calls, un-join the queue from **Preferences** > **Queues**.

## Contact notes are visible to other users

Notes and group contacts are shared at tenant level. Personal contacts are available only to the operator who created them.

If you need access changed for personal or group contacts, contact your administrator. These permissions are managed as user privileges in the administration portal.

## License questions

Attendant Console for Dialogue Cloud requires a Dialogue Cloud environment license and one license for each operator. For trial or subscription questions, contact your partner or AnywhereNow sales representative.

## Security and stored data questions

For detailed data-storage and security-policy information, ask your administrator for the current Attendant Console for Dialogue Cloud compliance guidance. Some storage options can be controlled through user privileges in the administration portal.


---

# 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/troubleshooting-and-support/troubleshooting.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.