> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/lead-sources-and-routing.md).

# Lead Sources & Routing

Lead Capture is the backbone of any successful real estate brokerage and agent, enabling you to efficiently gather, manage, and convert potential clients into loyal customers.

{% embed url="<https://rechatq.wistia.com/medias/hs08v1byxj>" %}

Members can connect to a variety of lead sources like Zillow, Realtor.com, Placester and more. To get started, follow the steps outlined below to locate and copy your Lead Source API Key. Once you've copied the necessary API Key, proceed to the source's website to finalize the connection.

1. Navigate to your **Profile** in the lower left corner.
2. Click **Lead Routing**.
3. Click **Connect Source**.
4. Select your source and copy your **API Key** by clicking the **Copy** icon.

Members can find additional resources for connecting to their lead sources below:

* [**Connecting Rechat to Zillow**](https://zillow.zendesk.com/hc/en-us/articles/1500004256062-App-Integrations-Setup-One-Way-Integration-Integrate-Your-Third-Party-CRM-with-Zillow)
* [**Connecting Rechat to Realtor.com**](https://support.realtor.com/s/lead-api-quick-start)
* [**Connecting Rechat to Placester**](https://support.placester.com/search/rechat)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rechat.com/whats-new/lead-sources-and-routing.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 `automate deployments from our CI pipeline` 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.