> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/properties/guidebooks/how-to-share-a-guidebook-with-a-guest.md).

# How to share a guidebook with a guest

This guide shows you how to send a guest the link to a guidebook from the inbox, made for their reservation.

{% hint style="info" %}
**Before you start**

* The guidebook must be a **Guest Guidebook**. Internal documents have no link.
* The conversation must have a reservation.
  {% endhint %}

## Share from the inbox

{% stepper %}
{% step %}

### Open the guidebooks of the stay

In the inbox, open the conversation. In the details panel, open the **Listing** tab and find the **Guidebooks** card.
{% endstep %}

{% step %}

### Copy the link

Click the share icon (**Copy link**) next to the guidebook. You see *Link copied to clipboard!*

{% hint style="success" %}
Always copy the link in the conversation of the guest. The link can be made for that reservation, so do not reuse one link for other guests.
{% endhint %}
{% endstep %}

{% step %}

### Send it

Paste the link in your reply and send it.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Guests also find all guest guidebooks of their stay in the guest portal, in the periods set in **Visibility**.
{% endhint %}

## Troubleshooting

<details>

<summary>Why do I see "A reservation is required to copy this guidebook link"?</summary>

The conversation has no reservation. Link the conversation to the reservation with **Link reservation** in the details panel, then copy the link again.

</details>

<details>

<summary>Why is there no share icon?</summary>

The guidebook is an **Internal Document**, or it has no link. Change the **Document type** to **Guest Guidebook** if guests may see it.

</details>

## Related

* [Guidebooks](https://docs.guestway.io/properties/guidebooks.md#guidebooks-in-the-inbox)
* [How to create a QR code for a guidebook](https://docs.guestway.io/guest-experience/qr-codes/how-to-create-a-qr-code-for-a-guidebook.md): to print a code that guests scan in the room
* [How to reply to a guest](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/how-to-reply-to-a-guest.md)
* [Reservation details panel](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/reservation-details-panel.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://docs.guestway.io/properties/guidebooks/how-to-share-a-guidebook-with-a-guest.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.
