# How Tiledesk manages Contacts and Leads with its CRM

Actually Leads and Contacts are synonyms. We use the term “Lead” in developer docs while we use “Contact” in the UI.

A Contact aggregates requests and metadata collected during conversation(s) with a single user (Anonymous or Authenticated, see next Section).

Example of collected metadata:

* Fullname
* Last name
* Email
* Custom metadata

In general, if the user is connected as “Anonymous” a Lead is created automatically based on the user-id (the user-id is a random generated UUID during the anonymous authentication process). All next user conversations with this UUID will be aggregated in a single Lead.

#### An example <a href="#an-example" id="an-example"></a>

When a user first starts a conversation from a browser instance (i.e. Google Chrome) he will be asked for some metadata to follow up a conversation:

<figure><img src="/files/R7BfoV4ykVvzfAdHVFSi" alt=""><figcaption></figcaption></figure>

Then the user contacts the support another time, as you can see by conversations summary:

<figure><img src="/files/rGuE7C5oCyvUBzMrjO5f" alt=""><figcaption></figcaption></figure>

Now in Contacts module you can search by email (<andrea1@gmail.com>) for the Lead:

<figure><img src="/files/CClLeJ0s0ByDkhSKYDq3" alt=""><figcaption></figcaption></figure>

As you can see there is only one Contact with that email. Now in contact detail you can see all the two requests made by this user:

<figure><img src="/files/5WSAXD4flcIe2VlXIOBW" alt=""><figcaption></figcaption></figure>

If the user, with the same email, starts a request from another browser he will be assigned a new Anonymous user-id.

So, for example, if you start a new request from Safari (we started with Chrome browser):

<figure><img src="/files/2dfXSJDVWzE5Uj7hBR2J" alt=""><figcaption></figcaption></figure>

As you can see the user is totally new (a new Anonymous user is created with a new UUID).

Now we insert the same email as in Chrome:

<figure><img src="/files/vQKFo5bvt05v7j5dOx3H" alt=""><figcaption></figcaption></figure>

If we execute the same search as before, by email:

<figure><img src="/files/c8pzIfAh239zepashIQl" alt=""><figcaption></figcaption></figure>

Now I find two Contacts, because they have a different UUID as you can see in the detail of the new Contact (Andrea Sp1):

<figure><img src="/files/YDOQz8tSyvUREqGOOQBg" alt=""><figcaption></figcaption></figure>

And this new user only made one conversation.

Actually we do not provide a feature to “merge” the two contacts into one (they are effectively the same user, recognized by their identical email, despite the two Contacts have different user-ids). This feature, with the ability to manually create and modify Contacts, is in our roadmap.


---

# Agent Instructions: 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:

```
GET https://guide.tiledesk.com/manage-your-contacts/how-tiledesk-manages-contacts-and-leads-with-its-crm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.