> 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.
* 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.activenow.io/en/client-management/merging-duplicates.md?ask=&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.
