> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing-rules/distribution-rules.md).
# Distribution rules
Use a distribution rule to qualify prospects and share meetings across a team. Conditions can use form answers, supported CRM fields, or configured enrichment data.
Open **Form routing → Distribution Rules → New Distribution Rule**. Work through **Basics**, **Conditions**, and **Assignment**.
## Qualify the prospect
Give the rule a descriptive name. Add a field, operator, and value for each condition. Combine conditions with **AND** when all must match, or **OR** when any may match.
For example, match a country and company-size range to an enterprise team. Provider-based conditions need the relevant [enrichment connection](/integrations/enrichment.md); a field that has no usable value may not satisfy your condition.
## Choose the team
Under **Meeting assignment**, select a **Team** and its **Round-robin participants**:
* **All members** includes the selected team's active members.
* **Selected members** lets you choose eligible teammates and adjust assignment weights.
A weight of 2 gives a teammate a larger intended share than a weight of 1. Actual totals also depend on availability, credits, and recent assignments. Review [Distribution methods](/routing/form-router/distribution-method.md) to choose strict or flexible behavior in the router.
## Sync the CRM owner
Enable the owner-update setting and select the CRM owner properties you want to write. For strict Form Router distribution, an owner update can be queued during routing. For flexible distribution, the host is selected at booking, and the owner update can be queued after that booking. Flexible distribution does not disable CRM ownership updates.
These updates require the connected CRM and valid property/member mappings. Vacation coverage does not replace the original CRM owner.
## Set meeting options
**Default guests** adds guests to the invitation without checking their availability. Use **Override meeting settings** to choose a different event type from the router default.
Save the rule, add it to the router's **Distribution priority**, and order the rules from most specific to broadest. Test representative prospects and activate the router version. Review [Distribution history](/routing-rules/distribution-rules/distribution-history.md) and [Calibration](/settings/workspace-settings/calibration.md) to understand later assignments.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.distro.so/routing-rules/distribution-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
