> 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/contact-card.md).

# Contact Card

After selecting a contact in either the search or contact groups, the contact information will appear in this panel. Alternatively, you can click on or hover over most avatars and the contact card will appear as a popup. There are three tabs in this panel: Details, Schedule (Exchange Calendar), and Organization Structure.

{% tabs %}
{% tab title="Contact Details" %}
The Contact Details tab displays the selected contact's Teams status message, department, mobile number, time zone, and other relevant information.

Contact notes for internal contacts and PSTN numbers can be saved and viewed for the contact on the details tab. See [Notes](/daily-usage/call-details.md)
{% endtab %}

{% tab title="Calendar" %}
The selected contact's calendar appointments will appear on this tab. Appointments for the next five business days will appear on the list.
{% endtab %}

{% tab title="Organization Structure" %}
The selected contact's organization structure will appear on this tab. Heading like Manager, Shares same manager, and Direct Reports can be expanded to show the relevant contact information.
{% endtab %}
{% endtabs %}


---

# 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/contact-card.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.