> 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/workflows/routing-steps.md). # Routing steps Choose the routing step that fits the decision you need. Routing selects a person; scheduling offers times for a meeting. ## Assign from Queue Use **Assign from Queue** when the queue is already known. Choose the **Queue**, then connect: * **Assigned**: use the selected member for a CRM owner update or the scheduler's **Earlier assignee**. * **Unassigned**: handle a paused, empty, or otherwise unusable pool. * **Error**: handle a failed assignment operation. The queue's profile and membership decide the rotation. Configure them in **Queues**, rather than copying member lists into the workflow. This step does not require a meeting. Use a profile that routes **Records** for record assignments. ## Apply Rulebook Use **Apply Rulebook** when lead data should choose the owner or queue. Select a published **Rulebook**. Put the form, CRM, or enrichment steps that supply its declared inputs before it. Connect **Resolved** to the intended next step and **Else** to your unqualified, unresolved, or unavailable path. Review the outcome and reason if these cases need different follow-up. A rulebook that routes to a queue also assigns its member. Do not assign from that queue again afterward. The optional **Fallback queue** handles an unresolved route. A rule deliberately selecting **No one** still takes Else. ## Find Queue Use **Find Queue** when the correct queue is described by data, such as an identifier stored in the CRM. Configure the lookup using the supported queue attributes, then use its found queue in a compatible assignment or scheduler field. Connect **No match** to a fallback. Prefer a stable identifier over a display name if admins may rename the queue. ## Choose when the member is selected **Assign first** when the record needs an owner before booking, or when the prospect should see one selected person's times. **Schedule directly from a queue** when you want times across available members. Set the routing profile to **Any available member** and let the scheduler select the host for the booked time. An earlier assignment fixes the member. A later scheduler cannot turn that fixed owner into a flexible pool merely by changing a profile. See [Show Scheduler](/workflows/show-scheduler.md) and [Routing profiles](/routing/profiles.md). --- # 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/workflows/routing-steps.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 `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.