> 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/overview.md).

# Routing overview

Routing decides who should receive a meeting. Start with where the prospect enters the conversation.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Form routing</strong></td><td>Qualify and route prospects who submit a form on your website.</td><td><a href="https://help.distro.so/routing/form-router.md">Form routing</a></td><td></td></tr><tr><td><strong>Click routing</strong></td><td>Route prospects who follow a campaign or call-to-action link.</td><td><a href="https://help.distro.so/routing/click-router.md">Click routing</a></td><td></td></tr><tr><td><strong>Outbound routers</strong></td><td>Let teammates arrange meetings for known prospects through a sales handoff.</td><td></td><td></td></tr></tbody></table>

Need a form as well as routing? [Lead forms](https://help.distro.so/routing-forms/lead-forms) let you build the questions in Distro, share a hosted page or embed the form on your website, and send qualified visitors to scheduling.

Ownership rules help you keep existing relationships with the right CRM owner. Distribution rules share meetings across eligible teammates. Fallback settings define what happens when the earlier rules don't find a host.

The event type defines the meeting experience. Team membership, permissions, calendars, and availability determine who can actually take the meeting.

For a fixed host, use a personal link. For several hosts attending together, use a group link. See Choose the right scheduling link.


---

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