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

# Sales workflow guides

Build a complete lead journey with the steps Distro already provides. Each recipe explains the input, routing decision, follow-up and checks to run before publication.

Start with [Demo request to booked meeting](/guides/demo-requests.md).

## Start here

<table data-card-size="large" 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>Demo requests</strong></td><td>Turn a qualified request into a booked meeting.</td><td><a href="/guides/demo-requests.md">Demo request to booked meeting</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FEXoO5bJigqAN1OiIcMR7%2Fdistro3-calendar.webp?alt=media">distro3-calendar.webp</a></td></tr><tr><td><strong>Territory routing</strong></td><td>Route by geography, company size and ownership.</td><td><a href="/guides/territory-routing.md">Route by territory and company size</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FRf4wWYnYaY6WcoHGL6Fi%2Fdistro3-ownership.webp?alt=media">distro3-ownership.webp</a></td></tr><tr><td><strong>Unbooked follow-up</strong></td><td>Follow up after a scheduler closes without a booking.</td><td><a href="/guides/unbooked-follow-up.md">Follow up with a lead who did not book</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FTR9C4HoeCkRotNctgHtF%2Fdistro3-messages.webp?alt=media">distro3-messages.webp</a></td></tr><tr><td><strong>Website intent</strong></td><td>Turn relevant visitor activity into an owner alert.</td><td><a href="/guides/website-intent.md">Turn website intent into an owner alert</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FBEoplt233SPp8pp36XOz%2Fdistro3-tracker.webp?alt=media">distro3-tracker.webp</a></td></tr></tbody></table>

## All guides

* [Demo request to booked meeting](/guides/demo-requests.md)
* [Route by territory and company size](/guides/territory-routing.md)
* [Follow up with a lead who did not book](/guides/unbooked-follow-up.md)
* [Follow up after a no-show](/guides/no-show-follow-up.md)
* [Assign a new CRM lead to the right rep](/guides/crm-assignment.md)
* [Turn website intent into an owner alert](/guides/website-intent.md)
* [Qualify a company with web research](/guides/research-qualification.md)
* [Fill missing data and write it back to the CRM](/guides/enrich-and-writeback.md)
* [Split-test two lead journeys](/guides/split-test.md)
* [Send a prospect an outbound booking link](/guides/outbound-booking.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/guides.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 `build a script that syncs our docs to a CMS` 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.