> 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/unbooked-follow-up.md).

# Follow up with a lead who did not book

Use the Show Scheduler **Not booked** branch to reach qualified leads who leave without completing a meeting.

## Prepare

Connect the engagement provider, choose the sequence/cadence and map the intended sender. Decide whether existing customers, suppressed addresses and already enrolled prospects should be excluded.

## Build

1. Qualify and route the lead.
2. Show the scheduler with the appropriate event and host.
3. On **Booked**, run booking-specific CRM updates and notifications.
4. On **Not booked**, check follow-up eligibility.
5. Match or create the provider's required contact/prospect.
6. Start the chosen sequence and inspect its enrollment outcome.

Not booked follows the scheduler's configured closure/timeout behavior. It is not an instant signal every time the browser tab disappears.

## Keep the message accurate

The message can invite the lead to choose a time. It should not imply a meeting already exists. Use an appropriate booking link for the intended host and event.

## Test

Test a booking completed before closure, a scheduler that expires unbooked, an already enrolled prospect and a provider failure.

Inspect enrollment in the engagement tool during a controlled live test. Simulation uses samples and does not send a message.

See [Sequence outcomes](/workflows/sequence-outcomes.md) and the relevant [Integration guide](/integrations.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/unbooked-follow-up.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.