> 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/search-for-contacts.md). # Search for Contacts Contacts can be searched by entering a search term in the search field at the top center of Landis Attendant Console. The search results will be shown as [contacts](/daily-usage/contacts.md) on the contact search panel. #### Additional Search fields Additional search fields can be specified by selecting the filter button to the right of the search field. A panel will appear below the search field with multiple fields. Text can be entered in any of the fields and select apply. The filter button will show a \* when a filter is being applied. To remove the search filter, select the filter button and select Clear. {% hint style="info" %} Persistent filter options can be added here: [Configure Filter Items Lists](/settings/advanced.md#configure-filters-item-lists) {% endhint %} {% hint style="info" %} Search terms can be specified in the filter panel without a search term in the primary search field. For example "Sales" in the department field will return all contacts with the department as sales. {% endhint %} --- # 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/search-for-contacts.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.