> 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

Define who the main contact is, who the operations contacts are, and which emails receive the invoices.

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 will you get?**
>
> The organization's contacts up to date: its main contact, its operations contacts, and the emails where invoices arrive.

### Before you begin

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

### Primary contact

In the tab **Main**, choose in the selector **Primary contact** the organization's main contact and click **Save**. Their card is shown below (name, email, phone, and language) for reference.

![Main Contacts Tab](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-c61faeccc63e41203d5d5d6cce7a6563bfa4db6f%2FContacto.png?alt=media)

### Operations Contacts

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

![Operations contacts list](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-d547130bf50ff11b658f89ddf35e0c7ad8400182%2FContacto-Operaciones.png?alt=media)

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

* **Name** and **Surnames**.
* **Email**.
* **Phone** (with its country code).
* **Manage tickets via WhatsApp** — enable it if you want that contact to manage tickets via WhatsApp.

Click **Save** to add it.

![Creating an operations contact](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-ee3c6dd21096b0b43a9de153bf7b2b1a9d2a957b%2FA%C3%B1adir_Contacto_Operaziones.png?alt=media)

### Billing contacts

In the tab **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](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-c3b7e4d77ac5bacc33efcdc332d55e734162eee4%2FA%C3%B1adir_contacto_para_facturas.png?alt=media)

### Conclusion

Now you know how to maintain an organization's contacts: the main one as a 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.](https://docs.plenit.com/docs-en/platform/organizations/detalles/contacts.md)
* Configure how customer service is presented in [How to customize the user portal and the administration panel.](https://docs.plenit.com/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 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/how-to/how-to-manage-organization-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.
