> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/routing/queues.md).

# Create and manage a queue

A queue is the group of people who can receive the same kind of leads or meetings. Its routing profile decides how those people take turns.

**Open Queues.** Have a published [routing profile](/routing/profiles.md) and the relevant workspace members ready.

## Create the queue

1. Create a queue and enter its **Queue name**.
2. Choose a **Routing profile**.
3. Use the generated **Identifier**, or enter a stable identifier such as `inbound-sales`.
4. Add **Individual members**, **Linked teams**, or both.
5. Review weights, then select **Create queue**.

An identifier uses 3–50 lowercase letters, numbers, or dashes. Keep it stable if a workflow uses **Find Queue** to look it up.

## Choose membership

For linked teams, **All members** follows team membership changes automatically. A selected subset keeps only the people you choose.

A person included directly and through multiple teams still has one place in the queue. Their weight is shared across those entries.

Use **Queue settings** to change the roster or profile. Review unavailable membership warnings when someone leaves and rejoins the workspace.

## Set weights and status

Weights only affect rotation when the routing profile uses member weights. They range from 0 to 1000, with up to four decimal places. A weight of 0 is a last resort.

Use **Pause** on a member to stop giving them new work in this queue. Use **Activate** to include them again. **Pause queue** stops the whole queue from taking new assignments.

A **No calendar** warning means the person cannot host a queue meeting until their calendar is connected. They can still receive record assignments where the profile allows them.

## Adjust calibration

Select a member's **Calibration** value to open **Adjust calibration**.

Choose to bring them to the queue average, bring them to the highest count, or set a custom value. A negative custom value gives extra turns; a positive value delays their next turn. Set 0 to remove the adjustment.

Add a reason so other admins can understand the change. Calibration affects future rotation; it does not change recorded assignment counts.

## Review the queue

| Tab              | Use it for                                        |
| ---------------- | ------------------------------------------------- |
| **Settings**     | Members, weights, status, turns, and calibration. |
| **Usage log**    | Individual uses and assignment outcomes.          |
| **Activity log** | Configuration and operational changes.            |
| **Stats**        | Distribution across members and outcomes.         |

Queues support up to 500 eligible members. An oversized roster must be reduced before use.

See [logs and reports](/routing/logs-and-reports.md) when the distribution differs from what you expected.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/routing/queues.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 `build a script that syncs our docs to a CMS` 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.