> 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/extras/leadboxer-reseller-getting-started.md).

# LeadBoxer reseller getting started

As reseller or agency you will want to add your clients to your account. the good news is that you can start doing so right away! There is no (technical) difference between a regular and a reseller account, everything you need is already in there.

Here are the steps to get going:

Note: Make sure you are logged into your account as Admin

### Adding and activating your customers:

1. Add your clients website(s) to your list of datasets in the [dataset overview](/leadboxer/using-the-app/elements/datasets.md)
2. Give you clients access to the application (optional)\
   You can do so by adding them as 'users' , giving them access to view the leads and/or customers for their own dataset(s). Make sure you do NOT set the 'Admin' [role](/leadboxer/account-and-billing/roles-and-permissions.md) your clients.
3. Once the dataset (and users) are added, you can go ahead and provide them with their unique tracking pixel for their website, and implement as many integrations as possible to get the most out of LeadBoxer. Please see the Getting Started guide and work off the list

{% content-ref url="/pages/L1BM9dYbRzHbnbhCoJIc" %}
[Getting Started](/leadboxer/getting-started.md)
{% endcontent-ref %}

### Billing

If you are ready and want to activate your account, [contact sales](https://www.leadboxer.com/demo) to setup billing. We have special pricing structure for Resellers.

Note

\- By default, some integrations cannot be setup for multiple sites from within a single account (eg Pipedrive) so please contact us if you need this.


---

# 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/extras/leadboxer-reseller-getting-started.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.