> 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/lead-board-scoring/sales-teams.md).
# Sales teams
How to create and configure sales teams so each team receives only the qualified leads most relevant to it.
Leads in eMarketeer are delivered to a sales team. Sales users in the same team share incoming qualified leads.
If your marketing activity spans multiple markets, brands, or product categories, create multiple sales teams so each one receives only the leads relevant to it.
## Create a sales team
Creating a sales team requires admin privileges.
1. Click the gear icon at the top right, choose Account Settings, then open Users & Teams.
2. Open the Sales Teams tab.
3. Click Create new team. This opens the Create sales team dialog.
4. Give the team a name in Team Name. If you already have sales users, tick the ones who should be members.
5. Click Save changes.
---
# 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/lead-board-scoring/sales-teams.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.
