> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing/click-router.md).

# Click routing

Use a Click Router for a personalized link in an email, campaign, or website call to action. Distro reads the prospect's identity, checks ownership rules, and uses fallback assignment when no eligible CRM owner matches.

**Workspace admins configure Click Routers.** Have a connected CRM, mapped email and name fields, a fallback team, and a booking-form event type ready. The shared link must supply a valid prospect email and a name; a bare link is not a replacement for a qualification form.

![Pricing page CTA Click Router in dark mode, with ownership matching, fallback assignment, scheduler, and booking outcomes.](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FFjdVCvIa1hkMtwXbHFGT%2Fclick-router-canvas-dark.png?alt=media\&token=101cad6d-dce0-4ca7-8995-2eb46c451488)

*The matched-owner and fallback paths lead to the same scheduler. This example uses the Northstar Labs test workspace.*

### Configure a Click Router

{% stepper %}
{% step %}

#### Create the router

Open **Click routing → Click Routers → New Click Router**. Enter a **Click router name** and choose **Create Click Router**.

Click a canvas card to edit it. Save each panel. Use **0** or the mini map to fit the flow, and **+ / −** to zoom.
{% endstep %}

{% step %}

#### Map the prospect identity

Open **Link clicked**. Under **Required field mapping**, map **Email** and **Name** to the appropriate CRM fields. Salesforce mappings depend on the selected contact or lead setup.

Enable **Strip email suffixes** only if addresses such as `alex+campaign@example.com` should match `alex@example.com`. This normalizes an email alias; it does not remove tracking parameters from the URL. Save.
{% endstep %}

{% step %}

#### Set ownership priority and fallback

Open **Ownership Rules** and turn on **Enable ownership matching** if existing CRM relationships should take priority. Add rules and put specific matches first. Drag rows or use **Alt + arrow keys** to reorder them.

Open **Fallback Assignment**. Choose the **Fallback team**, then **All members** or **Selected members**. Selected members let you choose participants and set their assignment weights.

Choose **Strict round robin** to select a host before showing times, or **Flexible distribution** to offer times across eligible teammates and select the host for the chosen slot. Save. See [Distribution methods](https://help.distro.so/routing/form-router/distribution-method) for weights, credits, and repeat-prospect behavior.
{% endstep %}

{% step %}

#### Configure the meeting and outcome

Open **Display Scheduler** to choose the event type and review meeting settings. Only booking-form event types are offered. **Display notes to booker** lets the prospect add context.

Open **Booking confirmation** to set a **Destination URL**, or leave it blank for the default confirmation. **No availability** keeps the prospect on the scheduler; review calendars and the event type when no times appear.

Open **After booking** for CRM meeting and record actions. These run after a successful booking. Fallback owner-update settings, when available, are separate from meeting creation. Save each edited panel.
{% endstep %}

{% step %}

#### Test and publish

Choose **Test route** and use synthetic inputs for an existing CRM owner and an unmatched prospect. Check the resulting route and fallback.

The simulation does not create real submissions, CRM records, calendar events, bookings, credits, or assignment-history changes. It does not query live integrations or availability.

Choose **Publish** when the saved configuration is ready. Saving alone updates the draft; new visits keep using the active version until publication. Follow [Router versions](https://help.distro.so/routing/router-versions) for rollback and pinned links.
{% endstep %}
{% endstepper %}

![Fallback Assignment panel in dark mode showing the team, eligible members, weights, and distribution choice.](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FTka2yBEJaZueTCN2Gywn%2Fclick-fallback-dark.png?alt=media\&token=62cbc393-8a2b-4a34-99af-5c238d8b7e38)

*Ownership is checked first. Fallback provides a host when matching is disabled or no eligible owner is found.*

### Install Click Router

Open the router's **three-dot menu → Install router**. The option is unavailable until the required CRM fields are mapped. Follow [Install and test a Click Router link](https://help.distro.so/routing/click-router/install-and-test) for platform templates, personalization, and a controlled campaign test.

Copy the generated link; do not construct it from the router's display name. Renaming a router does not require deriving a different URL.

### Find the right tool

| I want to…                             | Open…                                                                             |
| -------------------------------------- | --------------------------------------------------------------------------------- |
| Copy an email-platform template        | Three-dot menu → **Install router**                                               |
| Review or roll back publication        | Three-dot menu → **Versions**                                                     |
| Review configuration changes           | Three-dot menu → **Audit**                                                        |
| Explain an individual attempt          | **Routing Logs**, or the router menu when logs exist                              |
| Inspect assignment history and credits | Three-dot menu → **Distribution history**                                         |
| Compare campaign conversion            | [Routing Insights](https://help.distro.so/reporting/reporting-1/routing-insights) |
| Review meeting outcomes                | [Booking Insights](https://help.distro.so/reporting/reporting-1/booking-insights) |

### Troubleshoot a Click Router

| Symptom                                  | Check                                                                                                                                         |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Install is disabled                      | Map both required identity fields in **Link clicked**.                                                                                        |
| A link fails before showing availability | Confirm the final URL contains a valid email and a nonempty name, with no unresolved personalization tags.                                    |
| The wrong host is offered                | Check ownership priority, eligible CRM owner, fallback team, member selection, weights, and method.                                           |
| No times appear                          | Check the effective event type, host calendars, buffers, and [Availability preview](https://help.distro.so/settings/calendar-troubleshooter). |
| A saved change is missing                | Publish the draft and check whether the link is pinned to an older version.                                                                   |


---

# 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.distro.so/routing/click-router.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.
