> For the complete documentation index, see [llms.txt](https://ac.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ac.docs.landis.cloud/appendix/call-as-teams-queue-setup.md).

# Call as Teams Queue Setup

This feature is in preview. See [Feature States](/appendix/feature-states.md)

{% hint style="warning" %}
Prerequisites: 

1. Verify the user is able to initiate calls as the Teams queue in the Teams client.  For more info see: <https://learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue?tabs=general-info#assign-a-calling-id-optional>

2. Additional permissions are required to enable call as queue. See [Permissions](https://ac.docs.landis.cloud/appendix/pages/MXfcsBnbFZNffCP8ReLj#calldelegation.readwrite)
   {% endhint %}

3. In the Teams admin center, edit the Teams queue and locate the section labeled Assign calling ID. Select the resource account and click Copy object ID button. Paste the object ID(s) in the custom setting below. One or multiple object IDs can be listed.

```json
[
    {
        "key": "additionalDelegators",
        "description": "Array of additional delegators to add to the contact list. Array of strings of IDs",
        "value": [
            "Resource Account Object ID"
        ]
    }
]
```

2. In Landis Attendant Console, select Settings | Advanced | Copy and paste the custom setting in the Custom Settings text box. See example custom setting below:

<figure><img src="https://3897683970-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeAMhH-VlLBjxTpiKK3%2Fuploads%2FvQuDjkCECDcAOJ3RyNIW%2Fimage.png?alt=media&amp;token=393aad09-f945-42e3-95cc-cd30703e1df6" alt="" width="563"><figcaption></figcaption></figure>

3. Restart attendant console and now the resource accounts should appear in the "call as" dropdown list.


---

# 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://ac.docs.landis.cloud/appendix/call-as-teams-queue-setup.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.