> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/client-management/merging-duplicates.md).

# Merging Duplicate Participant Profiles

It can happen that a participant already in the system re-enters their details through the registration form on your website — creating a duplicate: two accounts with the same first and last name.

## Merging from the Tasks tab

If the system detects potential duplicates, you'll find them in ***Tasks*** under the ***Clients duplicates*** tab. Click the ***Merge duplicates*** button — a window will appear where you can compare the information for the two accounts.

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

* If you're sure it's the same person, click ***Merge duplicates***.
* If it's just a coincidence of names, use the ***Not duplicates*** option.

{% hint style="warning" %}
Marking participants as *Not duplicates* means they can no longer be merged in the system.
{% endhint %}

## System didn't detect duplicates

What if you spot duplicated accounts yourself but the system hasn't flagged them?

Compare the first and last name on each account — they must be identical. Check carefully for any typos. Correct the name on one account and the system will automatically detect them as duplicates.

## Preventing duplicates

The easiest way to avoid duplicate entries is to encourage your clients to [register in the ActiveNow app](/en/client-management/inviting-participants-to-the-client-panel.md). When participants sign up through their Client Panel, duplicates simply don't occur — keeping your data clean and organised.


---

# 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://help.activenow.io/en/client-management/merging-duplicates.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.