> 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/docs/docs_se/guider/lead-board-scoring/sales-teams.md).
# Sales-team
Hur du skapar och konfigurerar sales-team så att varje team tar emot de kvalificerade leads som är mest relevanta för det.
Leads i eMarketeer levereras till ett sales-team. Sales users i samma team delar inkommande kvalificerade leads.
Om din marknadsföringsaktivitet sträcker sig över flera marknader, varumärken eller produktkategorier, skapa flera sales-team så att varje team bara får de leads som är relevanta för det.
## Skapa ett sales-team
Att skapa ett sales-team kräver administratörsrättigheter.
1. Klicka på kugghjulsikonen uppe till höger, välj Account Settings och öppna sedan Users & Teams.
2. Öppna fliken Sales Teams.
3. Klicka på Create new team. Då öppnas dialogrutan Create sales team.
4. Ge teamet ett namn i fältet Team Name. Om du redan har sales users, bocka i de som ska vara medlemmar.
5. Klicka på 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/docs/docs_se/guider/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.
