> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/~/revisions/LpXrIuXoRo1tuAYMfI7z/getting-started/for-admins/step-2-explore-your-account-data.md).
# Step 2: Explore your account data
In this guide, we'll show you how to leverage the 'Lists' feature to enrich your target accounts.
**Step 1:** Navigate to **Tools > Lists** on the left navigation panel
**Step 2:** Click on **Import and Enrich**
**Step 3:** Next, Choose the List Type i.e Accounts or Developers and upload your file. Then, click on Next.
**Step 4:** Choose the column in your list that contains the company domain/website. This is mandatory for import success.
Click on Next.
**Step 5: Map the columns in your file to a field type** and turn on the import status toggle on for the columns you want to import. Then, click on Next.
**Step 6:** Add List Details like the List Name and Description.
**Step 7:** Select how you want to import your list.
**a. Import only accounts already in Reo:** Imports accounts that are already tracked in Reo. Any new accounts tracked in Reo in the future are automatically added. This option does not consume any credits.
**b. Import all accounts; Enrich those not in Reo:** Imports all accounts from your list, including those that aren't tracked on Reo. Accounts not already tracked in Reo are enriched with technographic insights. Note: This option consumes **3 credits per account** for each account not already in Reo.
Click **Save Changes** to Continue.
You will receive an **email notification** once the import is complete, and the list will be available in the **Lists panel** under "My Lists."
---
# 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://docs.reo.dev/~/revisions/LpXrIuXoRo1tuAYMfI7z/getting-started/for-admins/step-2-explore-your-account-data.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.
