> 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/what-is-an-attendant-console-for-microsoft-teams.md). # What is an Attendant Console for Microsoft Teams What is a Microsoft Teams Attendant Console? A soft client attendant has the following features: * A client optimized for handling multiple voice calls efficiently and quickly, especially transferring calls * Common, everyday tasks should be efficient * Easily search contacts, easy access to a large amount of contacts & quick overview of their status * Easily see caller context * Provides ability to tailor receptionist experience, customize to fit needs A Microsoft Teams attendant console specifically, will additionally: * Easily enhance Teams calling experience without integration * Leverage unique Microsoft Teams strengths like presence, chat, bots & other Microsoft 365 components * Naturally fit into MS Teams endpoint lineup: Client, Phone, Rooms, etc. **Any questions? You can connect with us right now by clicking** [**Talk to Sales**](https://landistechnologies.com/contact-sales-ac/)**.** {% embed url="" %} --- # 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/what-is-an-attendant-console-for-microsoft-teams.md?ask=&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.