> 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/how-to/how-to-manage-organization-contacts.md).

# How to Manage an Organization's Contacts

Each organization has its contacts, organized by type. 

From **Contacts** you decide who the main contact person is, who receives operations management, and which addresses invoices are sent to.

> #### 📘 **What are you going to get?** 
>
> The organization's contacts up to date: its main contact, its operations contacts, and the emails where invoices are sent.

### Before you begin

You need to be logged in and have permission to manage the organization. Enter it and open **Contacts**. You will see several tabs: **Main**, **Operations** and **Billing**.

### Main contact

In the **Main**tab, choose in the selector **Main contact** the organization's reference person and click **Save**. Below, their card is shown (name, email, phone, and language) as a reference.

![Main Contacts tab](/files/3a32cd8107faf4319b0cbd4912e901f67354f474)

### Operations contacts

In the **Operations** you have the list of operations contacts, with the columns **Name**, **Last names**, **Email**, **Phone** and **WhatsApp**. You can sort it, narrow it down with **Filters** and manage each contact from its actions menu.

![Operations contacts list](/files/bab8800659fb01f8052d04e397828d91a6e9f794)

To add one, click **Add** and fill out the form:

* **Name** and **Last names**.
* **Email**.
* **Phone** (with its country prefix).
* **Manage tickets by WhatsApp** — enable it if you want that contact to manage tickets by WhatsApp.

Click **Save** to add it.

![Adding an operations contact](/files/a8c543eb9e37b39e107e052e10f841a45efcd01c)

### Billing contacts

In the **Billing** you define which emails invoices are sent to. Enter an address in **Add email** and click **Add**. Each email is added to the list as a tag, and you can remove it from its delete icon. You can add as many as you need.

![Billing contacts](/files/e358da75c73a59cfbecb4c138306f86ad79bf13d)

### Conclusion

You now know how to maintain an organization's contacts: the main one as the reference, the operations ones for day-to-day use, and the billing ones so invoices reach the right person.

### Next steps

* Review the contact types in [Contacts.](/docs-en/platform/organizations/detalles/contacts.md)
* Set up how customer service is presented in [How to customize the user portal and the admin panel.](/docs-en/platform/organizations/how-to/how-to-customize-the-user-portal-and-admin-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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-manage-organization-contacts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.