> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/pipeline-and-automations/assigning-leads.md).
# Assigning Leads
How to manually or automatically assign leads.
In the pipeline, you'll want to make sure if you have multiple people on your sales team that they are properly assigned to the leads they are working. Here we'll show you how this can be done manually or automatically.
**Manually:** To manually assign a lead to someone, click on the lead in question and you'll see 'Responsible' on the right side of their profile. Simply select who should be in charge of this contact and it will assign them to the contact.
**Automatically:** We mentioned automations earlier and those are what we will use to automatically assign a user. If you need to refresh you memory on setting up an automation, [you can do so here](https://help.gleantap.com/pipeline-and-automations/automations).
To automatically assign a contact, add a new ongoing automation and under the 'Action' section, select 'Assign Lead to.'
All: If you select this option, the person you select for 'Assigned to' will receive every lead included in this automation.
Round Robin: If you select this option, you can select multiple people to be in a pool of receiving leads and it will rotate through them as new leads come in. If you are worried that the lead might already be assigned, you can select the option at the bottom to make sure the existing user gets overridden with the new selection from the round robin.
Round Robin by Day: Similar to the Round Robin option, in this you are selecting a pool of users who will be assigned the contacts as they are added. However, with this, you can do a different pool for each day of the week, since your team will likely not be working every day and often getting to the leads as quickly as possible is the goal.
---
# 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.gleantap.com/pipeline-and-automations/assigning-leads.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.
