> 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/routing/outbound-routing/share-links.md).

# Outbound links

Choose a dedicated link for one known prospect, a reusable link for multiple recipients, or Magic Slots when you want to suggest specific times. Your admin chooses which capabilities are enabled on the router.

| Option                      | Who it is for                                               | What the recipient does                                            |
| --------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ |
| **Dedicated prospect link** | One named prospect and one booking                          | Completes permitted missing details, chooses a time, and books.    |
| **Reusable outbound link**  | Different prospects using the same booker-owned entry point | Supplies their own identity and starts a separate private session. |
| **Magic Slots**             | One prospect choosing among 2–5 proposed times              | Selects an offered time; availability is checked again.            |

### Share a dedicated prospect link

{% stepper %}
{% step %}

#### Prepare the handoff

Open a [sales handoff](/routing/outbound-routing/book-a-meeting.md), confirm the prospect's identity, and complete the required booker-provided details. Dedicated links must be enabled on the router.
{% endstep %}

{% step %}

#### Create and copy the link

From prospect details, choose **Share link**, then **Create booking link**. If you are viewing the calendar, use **Back** to return to prospect details first.

Review the intended recipient, copy the generated link, and check its expiry. **Preview booking page** opens the recipient experience.

The link carries only permitted handoff context. The recipient may still need to complete required prospect-owned fields before routing or booking.
{% endstep %}

{% step %}

#### Share with the intended recipient

Use the link for that prospect. It expires and is limited to one booking. It does not reserve an assignee or a time.

Under **Link options**, use **Replace link** if you need another link for the same handoff; the previous link is revoked. **Revoke link** stops the current link from being used. Changing the handoff also revokes its dedicated links.
{% endstep %}
{% endstepper %}

### Use a reusable link

Reusable links are created through the **Chrome extension**, not the retired dashboard link builder. After your admin enables the option and activates the router, use the extension's outbound-link flow for an active router you are allowed to use, then copy the resulting booker-owned link.

Each recipient provides their own identity and gets a separate session. Do not substitute a dedicated prospect link when you need a reusable entry point.

Admins can inspect existing booker-owned links in the router's **Booking & sharing** configuration. Revoking or rotating a link affects the places it has already been shared; replace those placements when its address changes.

If the extension does not offer the router, check the workspace, active status, allowed-booker access, reusable-link setting, and whether the pinned form can be completed by a prospect.

### Expiry and availability

| Behavior              | Dedicated link                           | Reusable link                                     | Magic Slots                                |
| --------------------- | ---------------------------------------- | ------------------------------------------------- | ------------------------------------------ |
| Prospect identity     | Already associated with a named prospect | Entered separately by each recipient              | Associated with the source handoff         |
| Configurable expiry   | 1–30 days, capped by session expiry      | Managed by the reusable-link lifecycle and access | 1–14 days, capped by source session expiry |
| Reserves time or host | No                                       | No                                                | No                                         |

In **Booking & sharing**, **Prepared links → Allow Share availability** enables dedicated links. The seller's separate **Share availability** action means [Magic Slots](/routing/outbound-routing/magic-slots.md).

If a link is expired, revoked, consumed, or otherwise unavailable, return to the appropriate handoff or extension flow to create a valid replacement. Do not forward another prospect's dedicated link.

### If creation needs attention

If the share panel asks for more information or shows a CRM error, choose **Edit prospect details**. Complete the required answers, confirm the prospect's identity, or retry the CRM lookup, then create the link again. An error message is not a created link.

Dedicated links appear in this handoff's share panel. Create reusable outbound links through the extension flow described above.


---

# 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/routing/outbound-routing/share-links.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 `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.