> 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/daily-usage/call-as-delegate-or-queue.md).

# Call as Delegate or Queue

**Prerequisite:** [Enable Call as Delegate](/getting-started.md#enable-call-as-delegate)

**Additional setup is required for call as Teams queue. See** [**Call as Teams Queue Setup**](https://ac.docs.landis.cloud/appendix/call-as-queue-setup)

Calls can be made on behalf of another user or queue by selecting the avatar | select a "call as" option from the drop down. The call as menu option will only appear if (1) the user is a delegate of another user in Teams and is given the ability make calls or (2) a Queue has been manually configured to appear. Once the setting has been changed, initiate a call as normal.

By default, the "call as" setting remains active until manually changed. However, if preferred, it can automatically switch back to calling as the signed-in user after one call. To enable this feature, navigate to settings | Advanced | enable Reset Selected Delegate to Myself after 1 Call.

There is also the ability to create a quick access shortcut to change the call as delegate setting. See [Quick Access Shortcuts](/settings/quick-access-shortcuts.md#set-call-on-behalf-of-shortcut)


---

# 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/daily-usage/call-as-delegate-or-queue.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.