# Ownership Rules

Ownership Rules help you automatically match incoming prospects with existing records in your CRM system. This allows you to:

* Maintain data consistency by matching prospects with existing contacts/leads/companies
* Route prospects to the right owner based on existing relationships

## Creating an Ownership Rule

{% stepper %}
{% step %}
Navigate to the **Form Routers** tab in the sidebar

<figure><img src="/files/QQpmDOs8vlxPdLIci04Y" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select "Ownership Rule"
{% endstep %}

{% step %}
Click "+ New Ownership Rule"
{% endstep %}

{% step %}
Select how to check for ownership in the modal

<figure><img src="/files/zB8Ukg87SFHu12Tmxnyq" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Setting Up Your Ownership Rule

### Types of Matching

{% tabs %}
{% tab title="Exact Matching" %}
**Exact Matching**: The prospect's email must exactly match an existing record in your CRM

{% hint style="info" %}
Example: <john.smith@example.com> will only match with <john.smith@example.com>
{% endhint %}
{% endtab %}

{% tab title="Fuzzy Matching" %}
**Fuzzy Matching**: The prospect's email domain can match with other records sharing the same domain

{% hint style="info" %}
Example: <john.smith@example.com> can match with <jane.doe@example.com> because they share the example.com domain
{% endhint %}
{% endtab %}
{% endtabs %}

<figure><img src="/files/27hP0Tx77NEE2BXJ9t1k" alt=""><figcaption></figcaption></figure>

### Adding Conditions

Additional conditions allow you to refine when an Ownership Rule should be applied. While the primary ownership condition checks for contact/company ownership, additional conditions let you evaluate specific CRM field values before assigning the meeting.

#### Example Scenarios

<details>

<summary>Scenario 1: Enterprise Contacts Only</summary>

```
Group Logic: AND
Conditions:
- Company Size > 1000
- Industry != "Small Business"
```

</details>

<details>

<summary>Scenario 2: High-Priority or VIP Contacts</summary>

```
Group Logic: OR
Conditions:
- Lead Status = "Hot"
- Customer Tier = "Enterprise"
- Priority Level = "High"
```

</details>

<figure><img src="/files/o5xrG1w56uBus2wtoX97" alt=""><figcaption></figcaption></figure>

#### Condition

Each condition consists of three parts:

1. **Field** - The CRM field you want to check
2. **Operator** - How you want to compare the field value
3. **Value** - What you're comparing against

<figure><img src="/files/kHXSOvdE90Q9dzFykjYk" alt=""><figcaption></figcaption></figure>

#### Condition Groups

* Conditions can be organized into groups
* Each group can use either:
  * **AND logic** - All conditions in the group must be true
  * **OR logic** - Any condition in the group can be true

<figure><img src="/files/79qSmr1eVzVEOXm6Dktx" alt=""><figcaption></figcaption></figure>

### Assigning Meeting

When a prospect matches with an existing record in your CRM as well as with your conditions, you have two options for assigning the meeting:

{% tabs %}
{% tab title="Existing Owner " %}
**Assign to Existing Owner (Default)**: the meeting will be assigned to the current owner of the matched record in your CRM

{% hint style="info" %}
For example, if John Smith owns the matching contact in HubSpot, the meeting will be assigned to John Smith
{% endhint %}

If you choose to assign to the existing owner, you'll need to select which owner field to use from your CRM. This is particularly useful when records have multiple owner fields or when working with custom owner properties.
{% endtab %}

{% tab title="Specific User" %}
**Assign to Specific User**: you can manually select a team member to receive all meetings from this rule.

{% hint style="info" %}
This overrides the CRM ownership and ensures meetings always go to your chosen team member
{% endhint %}
{% endtab %}
{% endtabs %}

<figure><img src="/files/3VwjcPgS6LnDWkJAthna" alt=""><figcaption></figcaption></figure>

### Update CRM Owner

When an Ownership Rule is triggered, you can automatically update the record owner in your CRM (HubSpot or Salesforce). This ensures that the ownership in your CRM stays synchronized with your routing assignments.

{% hint style="danger" %}
The ownership update happens when the Ownership Rule matches (during form submission), not when the meeting is actually booked.
{% endhint %}

{% tabs %}
{% tab title="HubSpot" %}
For HubSpot, the system will find your Contact using either their HubSpot ID or email address, then update the owner property to match your routing assignment. All updates are monitored to ensure proper synchronization between your routing assignments and HubSpot ownership.
{% endtab %}

{% tab title="Salesforce" %}
For Salesforce, the system will locate your **Lead** or **Contact** using either their Salesforce ID or email address, then update the owner field accordingly. All updates are tracked to ensure successful synchronization between your routing assignments and Salesforce ownership.
{% endtab %}
{% endtabs %}

<figure><img src="/files/nWBprUGOka3wqbvwyLy9" alt=""><figcaption></figcaption></figure>

### Advanced Meeting Options

Advanced meeting options allow you to customize additional settings for meetings that are booked through this rule. These settings help you ensure consistency and save time by automating guest additions and meeting type selection.

{% hint style="danger" %}
Be aware that Distro will not check the availability of the additional guests
{% endhint %}

**Override default meeting settings: l**ets you use different meeting settings than what's configured in your router.

<figure><img src="/files/ZfNeQg4mCzcPgmx38nZ0" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://help.distro.so/routing-rules/ownership-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.