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

# Contacts

Contacts are shown in both the search and contact group panels. These contacts include contact information and contact methods. Contacts are used to initiate communication with a contact or to select a contact as a transfer recipient. Default contact methods shown are chat and Call (using default method). Additional contact methods are shown by selecting the more button.

### Using Contacts

#### When a call is in a transfer mode

If a call is in a transfer mode, double clicking or selecting a voice contact method on the contact will initiate a transfer to the contact.

A new chat or email can be initiated with a contact by selecting chat or email buttons.

#### When no calls are in a transfer mode or no active calls

Selecting a contact method on the contact will initiate a new call, chat, or email to the contact. Double clicking the contact will initiate a new call to the contact.

Chat or email callback reminders are not available in this scenario.

{% hint style="info" %}
The buttons on the Contacts can be customized. See [Contacts](/settings/contacts-settings.md)
{% endhint %}

#### Callback Reminders

This feature enables you to quickly send a chat or email message to another user letting them know that the caller has requested a callback.

A chat or email callback reminder can be sent by selecting the email or chat callback reminder button when there is a current call. This will open a chat or email with the prepopulated callback message. The default callback message includes the caller name, number and call time.

{% hint style="info" %}
The chat or email callback reminder templates can be customized. See [Call Back Messages](/settings/transfer.md#call-back-messages)
{% 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/contacts.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.