> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/using-the-app/elements/lists.md).

# Lists

### Introduction: what are Lists?

A List (Account List) is a list of companies or organisations that you want LeadBoxer to recognise and do something with: for example your existing clients, former clients, or a list of target accounts for Account Based Marketing (ABM). If you need to filter on a large number of accounts, Lists are what you need.

The LeadBoxer Lists feature allows you to:

1. Upload a list of company names and / or domain names.
2. Apply this list as a Filter and make part of your Segments (and notifications)

### How Lists work

1. Go to **List Settings** and download the sample CSV file.
2. Add your accounts (domain and/or company name; wildcards are allowed) and upload the file.
3. In the filters, open **Lists** and select your list, then save the result as a [Segment](/leadboxer/using-the-app/elements/segments.md).
4. Use that segment for [notifications](/leadboxer/using-the-app/elements/notifications.md), LeadBoards or reports.

On the List Settings page you can also download, replace or remove a list you uploaded earlier.

See the tutorial below for the details.

{% content-ref url="/pages/pc5ly9pjDdTsuMMjQ8zw" %}
[How to upload a List (ABM)](/leadboxer/guides/how-to-upload-a-list-abm.md)
{% endcontent-ref %}


---

# 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.leadboxer.com/leadboxer/using-the-app/elements/lists.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.