> 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/integrations/chrome-extension/single-use-links.md). # Single-use links Use a single-use link when you want one booking from a conversation without sharing your regular reusable URL. In the Chrome extension, open **Scheduling**, find a personal or group link, and choose the single-use link action. Review the meeting details. Add recipient information if useful, choose **Expires after**, then click **Create and copy link**. Use **Preview booking page** to check it before sharing. Recipient details prefill the booking form; the recipient can edit them. The link accepts one booking and stops being available after it is used or expires. Creating it does not book a meeting or reserve a time. Your original personal or group link remains reusable. If the recipient needs a new link after the first one expires, create another single-use link from the original meeting link. For an outbound handoff, use **Share link → Create booking link**. This carries the prospect's handoff context and follows the Outbound Router's settings. **Share availability** proposes times instead. See [Outbound links](/routing/outbound-routing/share-links.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 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/integrations/chrome-extension/single-use-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 `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.