> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/organizations/detalles/contacts.md).

# Contacts

The contact types of an organization and what each one stores.

The section **Contacts** groups the organization's people and contact addresses, organized into tabs: **Main**, **Operations** and **Billing**.

### Main

The organization's main contact. You choose it from a dropdown and confirm with **Save**. Below, a card with their details: Name, Email, Phone, and Language.

### Operations

The operations contacts, in a table with **Name**, **Surnames**, **Email**, **Phone** and **WhatsApp**, plus their actions menu. You add new ones with **Add** and narrow the list with **Filters**. When adding one, you enter First Name, Last Name, Email, and Phone, and you can enable **Manage tickets via WhatsApp**.

### Billing

The email addresses where billing is sent. You add each email in its field with **Add**; the added emails appear as tags that you can remove.

### Next steps

* Manage contacts step by step in [How to manage an organization's contacts.](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-manage-organization-contacts.md)
* Learn how the dashboard is organized in [The organization panel.](https://docs.plenit.com/docs-en/platform/organizations/concepts/the-organization-panel.md)


---

# 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://docs.plenit.com/docs-en/platform/organizations/detalles/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.
