> 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/scheduling/booking-links.md). # Booking links and handoffs Choose the link that matches the booking journey. ## Personal links Use **Booking links → My Personal Links** when the meeting should be with you. Preview the link, confirm the event and availability, then share it. Use a group link for a meeting that needs several named teammates. Review required attendance and overlapping availability. These links have their own booking configuration. They do not automatically run a qualification or ownership workflow. ## Public routed journeys Use a published **Lead form** when anyone should be able to start a new qualified routing journey from the same URL. The prospect supplies their details, the workflow routes them, and Show Scheduler offers the appropriate meeting. This is the simplest self-service replacement for an old reusable routed link when collecting the prospect's identity again is acceptable. See [Lead forms](/forms/lead-forms.md) and [Move a Click Router](/migrate/click-router.md). ## Seller-led handoffs Use a **Browser extension** workflow when the seller already has the prospect's details and needs to route them to another teammate. Review the prospect fields, owner, and event before booking. Add the seller as a required or optional attendee only if the meeting needs it. ## Session-specific scheduler links Show Scheduler creates a scheduling session for one workflow run. It has a 3–60 minute booking window. A raw scheduler URL is not a reusable public router link. Opening the page also needs the complete supported session handoff. Use a sharing control only when the installed surface supports that handoff. Do not assume the old prepared-link expiry, reusable-link controls, or Magic Slots configuration is carried over. If you need a long-lived public link, choose a lead form or standard booking link that fits the journey. If you need a personalized campaign with ownership routing, follow the [Click Router migration guide](/migrate/click-router.md). ## After a booking Use the meeting's verified management links or Bookings actions to reschedule or cancel. Reusing a closed scheduling session does not start a new routing journey. --- # 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/scheduling/booking-links.md?ask=&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.