> 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/connect-to-placester.md).

# Placester

Route your Placester leads into Rechat for increased lead engagement and conversion. Your Placester leads, and their data, will automatically be transferred to Rechat.

### Before you begin

You must have access to the lead-routing or integration settings for your Placester website.

This connection is completed in two parts:

1. Create the Placester lead route and copy its API URL from Rechat.
2. Add the API URL to your Placester settings.

{% embed url="<https://rechatq.wistia.com/s/0jxv88ib9he0fuu>" %}

### Create a Placester lead route in Rechat

1. Select **People** from the main navigation menu.
2. Select **Lead Routing**. Lead Routing is where you can connect lead sources and control how incoming leads are distributed.
3. Select **Add Route**.
4. Enter a name for the new route, such as **Placester Leads**.

{% hint style="info" icon="head-side-brain" %}
**Best practice:** Include the provider’s name in your route name. This makes each route easier to identify, especially when you receive leads from multiple sources.
{% endhint %}

5. Select **Connect Source** on the new route.
6. Select **Placester** from the list of available lead sources.
7. Rechat will generate a unique **API URL** for the route. Select the **Copy** icon beside the API URL.
8. A confirmation message will appear when the API URL has been copied to your clipboard.

{% hint style="info" %}
The API URL is unique to this Rechat lead route. Do not use an API URL copied from another user or route.
{% endhint %}

### Complete the connection in Placester

After copying the API URL from Rechat:

1. Sign in to Placester.
2. Open the settings used to manage lead delivery or integrations for your website.
3. Paste the **API URL** copied from Rechat into the appropriate webhook or lead-delivery field.
4. Save the connection.

If you cannot locate the correct setting, contact Placester Support for assistance adding a webhook URL for lead delivery.

### What happens next?

After the connection is completed, new leads captured through Placester will be delivered to the Placester lead route in Rechat. From there, each lead will follow the distribution rules configured for that route.

{% hint style="info" %}
Connecting Placester establishes the lead source, but the route must also include the appropriate routing rules and recipients. Review the complete route before relying on it for live leads.
{% endhint %}

### Confirm the connection

Submit a test lead through your Placester website and confirm that:

* The lead appears in Rechat.
* The lead enters the correct Placester route.
* The lead is assigned to the intended agent or team member.
* The recipient receives the expected notification.

If the test lead does not appear, confirm that the complete API URL was entered correctly in Placester and that the Rechat route is active and properly configured.


---

# 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.rechat.com/guides/crm/contacts/adding-contacts/connect-to-lead-sources/connect-to-placester.md?ask=<question>&goal=<endgoal>
```

`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.