> 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/outbound-booking.md). # Send a prospect an outbound booking link Use an event link when a rep wants to share meeting times or a booking page from an outbound conversation. ## Prepare The rep connects their calendar and conferencing account, sets working hours and chooses the supported event. Review whether the meeting includes required co-hosts or a queue host. ## Choose the handoff Use the browser extension or supported event-link API to create the personal/team link. Share the public URL, issue a single-use link for one invitee, or send a slot proposal using currently offered tokens. For API details, see [Event links](/developers/event-types.md) and [Single-use links and proposals](/developers/scheduling-artifacts.md). ## Understand queue selection The current event-link path resolves a queue host at link creation using recent assignment counts. The resulting link pins that member; it does not rerun the complete routing profile for every recipient's booking. If the journey needs lead-dependent ownership or territory routing, use the supported workflow/SDK journey instead of treating a static link as a full router. ## Verify Open the generated link as a guest and check hosts, duration, timezone and location. Complete a controlled booking and confirm the invitation. A proposed time is not held permanently, and a shared link is not a booked meeting. Check expiry on single-use artifacts. See [Browser extension workflows](/workflows/extension.md) and [Move a Click Router](/migrate/click-router.md) for migration decisions. --- # 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/outbound-booking.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.