> For the complete documentation index, see [llms.txt](https://help.roolz.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.roolz.net/en/contacts-and-people-search/my-contacts.md).

# My contacts

Imagine Roolz both as a social network and a messenger for the trucking industry. The platform allows its users to maintain both corporate as well as personal database of counterparties and customers.

### What you can and can't do with contacts

* You can add users to your personal contacts, just like in the phonebook.
* If you are a member of a company, you can see both your personal contacts as well as those of your colleagues in the contact list, i.e. company contacts. You can quickly find and contact the right person in the company.
* You can also remove users from your contacts. To do this, open the user's profile. Next to the "Message" button, you will see the "Delete from contacts" icon.
* If a user has blocked you (blacklisted you), you won't be able to add them to your contacts.
* You can't change another user's first name, last name or other data.
* You cannot add company contacts to the blacklist.
* When you block a user, both you and the user cannot add each other to contacts or send messages in a chat.

{% hint style="info" %}
You can add users to your contacts without sending an approval request.
{% 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://help.roolz.net/en/contacts-and-people-search/my-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.
