> 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/guides/crm/contacts/adding-contacts/connect-to-lead-sources/union-street-media.md).

# Union Street Media

Seamlessly connect your Union Street Media website with Rechat to sync leads and contact details all in one place.

#### **Integration Setup**

*Note: This setup must be completed by the account owner.*

1. Generate an Channel ID in Rechat:
   * Navigate to **People > Lead Routing > Union Street Media**
   * Click **Add Route**
   * Click **Copy Channel ID**
2. Provide the following details to your Union Street Media representative:
   * Your **Rechat Channel ID**
   * The **email address** associated with your Rechat account

Once the integration is activated on their end, any existing leads in Union Street Media will sync with Rechat.

#### **What Gets Synced?**

**New Lead Information**

Whenever a lead is created in Union Street Media, the following details sync automatically:

* **Contact Information**: First name, last name, primary and secondary email, primary and secondary phone number, and address (street, city, state, zip).

**Lead Activity from Union Street Media**

When a lead interacts with your Union Street Media website, their activity will sync to Rechat:

* **Saved Searches**
* **Favorited Properties**
* **Recently Viewed Properties**
* **Website Page Views**

This integration ensures your leads’ engagement is always up-to-date, helping you manage follow-ups and conversions more effectively within 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/guides/crm/contacts/adding-contacts/connect-to-lead-sources/union-street-media.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.