> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/contacts-lists/bulk-actions-tool.md).

# How to manage contacts in bulk

How to use Bulk Actions to update or manage large groups of contacts in a single operation.

Bulk Actions lets you update or manage groups of contacts in a single operation. It's available in several places where eMarketeer lists contacts, for example under Contacts, in a campaign's contacts, in component reports and in journey step lists.

To open it under **Contacts**, select the contacts you want to change with the checkboxes in the list. To select every contact in the current view, use the checkbox at the top of the list. The **Bulk actions** button then appears at the top of the list, next to **Export**. Use it when you need to apply the same change to many contacts at once.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-f5cc221c3983fcd13628840da7a89d09990b3978%2Fbulk-actions-tool-contacts-bulk-actions-button.png?alt=media" alt="Bulk actions button above the selected contacts in the contact list"></div>

## Bulk action options

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-79422ed133d97861a1b322c65aeb1d242cf76d00%2Fbulk-actions-tool-bulk-actions-dialog.png?alt=media" alt="Bulk Actions dialog listing the seven available operations, numbered 1 to 7"></div>

The Bulk Actions tool offers seven functions:

1. **Contact lists** — Adds the contacts to, or removes them from, a contact list. Choose **Add to list** or **Remove from list**, then select a list. You can create a new contact list if one does not already exist.
2. **Tags** — Adds tags to, or removes them from, all the contacts. Choose **Apply tag** or **Remove tag**, then select or create a tag.
3. **Update category** — Updates the Contact Category (Prospect, Customer, Other) of all the contacts.
4. **Update subscriptions** — Changes the opt-in/opt-out status of subscription lists for the contacts. You can update any or all subscription lists in one go.
5. **Update legal basis** — Updates the Legal Basis of all the contacts. You can update both "Store and Process" and "Marketing Sendouts" at the same time, and to different options if needed.
6. **Unsubscribe** — Unsubscribes the contacts from all future email and SMS sendouts by setting their Legal Basis for Marketing Sendouts to "Withdrawn."
7. **Permanently delete contacts** — Permanently deletes the contacts from your account along with any interactions they have been part of. Deleted contacts cannot be restored. This includes their interactions, activity, and engagement history.


---

# 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://support.emarketeer.com/guides/contacts-lists/bulk-actions-tool.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.
