# How to Remove Duplicated Attendees When Importing Attendees

When performing bulk importing on the Attendee List, organizers have the option to either include or exclude the duplicated emails that already exist within the Attendee List. This feature is present when importing attendees as Registered status.

|                                            |                    |                       |
| ------------------------------------------ | ------------------ | --------------------- |
|                                            | **Invited Status** | **Registered Status** |
| Supports adding duplicate attendees?       | No                 | Yes                   |
| Attendee needs to go through registration? | Yes                | No                    |

## User Flow

### Importing Attendees as Registered Status

1. Under the Attendee List, click “Add Attendee”

   ![](/files/QdJfmdsddehYy4XGGzvb)
2. Select “Bulk importing” > Select “CSV UTF-8 File” > Download & Upload CSV file > Select ticket type (if event has no ticketing, select “No Ticket Required”) > Click “Preview Import Result”

![](/files/cMoT9WIVKN58zxu11wY4)

![](/files/KsgpBpADJOU2fiNIs6RF)

3. View the unique / duplicate emails > Click Next > Select the list to import accordingly > Click "Confirm To Import"

![](/files/x3PjpwX7vB9k3T22q8IF)

![](/files/vpi9uSnqQ4MVE0AlLjSe)

### Benefits

* Organizers will not have to manually check the duplicate emails that exist within their CSV files. Making the attendee import process smoother.

### Limitations

1. Only valid for In-person events.


---

# 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://eventx-hq.gitbook.io/knowledge-base/attendee-management/importing/how-to-remove-duplicated-attendees-when-importing-attendees.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.