> 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/guides/crm-assignment.md).

# Assign a new CRM lead to the right rep

Use a CRM-created trigger for lead assignment without requiring the prospect to visit a booking page.

## Prepare

Connect HubSpot or Salesforce, map owner identities and create the intended queues and rulebook. Decide which object starts the workflow and which fields qualify it.

## Build

1. Choose the supported CRM record-created trigger and source conditions.
2. Read the supplied record and qualify it.
3. Match ownership where needed.
4. Apply the rulebook and Route to an eligible member or queue.
5. Update the CRM owner with the resolved provider identity.
6. Notify the assignee with a link to the record.

The Distro assignment and CRM write are separate results. If the write fails, inspect the assignment and destination before rerunning the whole journey.

## Avoid unintended repeat intake

When using an updated-record trigger instead, select narrow watched conditions and fields. An ownership write can itself be a record change; check that the source is not repeatedly starting the same business journey.

CRM intake uses polling and cursors, so a provider record change is not necessarily an immediate run.

## Test

Check an eligible new lead, an existing owner, an unmapped owner, a non-qualifying lead and a CRM write validation error.

Inspect the chosen member, queue assignment and final CRM owner in a controlled live test.

Coming from an old router? See [Move an Outbound Router](/migrate/outbound-router.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/guides/crm-assignment.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.