> 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/profiles.md).

# Routing profiles

A routing profile controls how a queue rotates work, offers scheduler times, skips unavailable people, and refunds turns.

**Open Queues → Routing profiles.** Create a profile before creating a queue, or edit an existing profile to change the behavior of the queues that use it.

## Create a profile

Enter a **Profile name** and an optional description. Under **Routes**, select **Records**, **Meetings**, or both.

* **Records** covers lead and CRM-owner assignments made through workflows.
* **Meetings** covers meetings booked through a queue-hosted event or Show Scheduler.

A profile must support the kind of work your workflow sends to the queue.

## Choose scheduler times

| Setting                  | What the prospect sees                                                                                             |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| **Pre-picked member**    | Distro selects one host first, then shows that person's available times.                                           |
| **Any available member** | Distro shows times where an active eligible member is free, then selects the host for the time the prospect books. |

These settings replace the old strict versus flexible distribution choice.

## Choose the rotation

| Rotation               | How it chooses                                                                                                        |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Even rotation**      | Favors the lowest counted assignments relative to weight.                                                             |
| **Most open calendar** | Favors the member with more free time around the chosen slot. Requires Meetings and uses Any available member.        |
| **Longest idle**       | Favors the person whose last assignment was longest ago; people never assigned go first. Member weights do not apply. |

Choose a **Tiebreaker** for equal scores. Review **Reset counts** if counts should restart monthly or quarterly instead of continuing indefinitely.

Turn on **Use member weights** when members should receive different proportions. A weight of 2 receives about twice the work of a weight of 1 among equally eligible members over time.

## Review availability and refunds

Choose whether to skip members who are out of office, about to be out of office, or busy at decision time. The busy-now option applies to meeting bookings. Working hours and meeting buffers still apply when offering meeting times.

Under **Turn refunds**, choose whether cancelled, reassigned, or no-show meetings give the member a turn back. Reassignment refunds apply to the member who lost the meeting.

## Save and review the impact

Select **Create profile** or **Save profile**. Saving changes publishes a new profile version for the queues that use it. Review **Used by** before changing a shared profile.

Changing a profile does not rewrite past assignments. Use [queue calibration](/routing/queues.md) when you need an explicit adjustment to future rotation.


---

# 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/profiles.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.