> 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/inbox-and-messaging/saved-replies/how-to-create-a-saved-reply.md).

# How to create a saved reply

This guide shows you how to write a saved reply once and use it in the inbox, so common questions are answered in one click.

## Create the saved reply

<figure><img src="https://content.gitbook.com/content/kBDBFX4VDrFqOnghyBKx/blobs/A27qtXfQrALFU4GkKHvO/image.png" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Open the saved replies

Go to **Properties** and open the **Saved Replies** tab, on the global level or on a listing, multi-unit or complex. Click **Create**.
{% endstep %}

{% step %}

### Name the reply

Enter a **Title**, for example *Wi-Fi code*, *Check-out time* or *Parking info*. Select the **Language**.

{% hint style="success" %}
Name the reply after the question, not the answer. *Wi-Fi code* is faster to find than *Hi, here is the Wi-Fi info you asked about*.
{% endhint %}
{% endstep %}

{% step %}

### Choose where it applies

In **Linked to**, select **Global**, **Listing**, **Complex** or **Multi-unit**. Then select the properties. Add a **Description** if your team needs to know when to use the reply.

{% hint style="success" %}
Link a reply on the highest level that fits. A reply about a building belongs on the **Complex**, not on each listing of it.
{% endhint %}
{% endstep %}

{% step %}

### Write the message

Write the **Message**. Type **@** or pick a variable in the panel on the right to insert a placeholder, for example the guest's first name or the check-in date. Click **Preview variables** to check the result.

{% hint style="success" %}
Use placeholders for everything that changes from one booking to the next. The reply stays personal, even when your team sends it many times a week.
{% endhint %}
{% endstep %}

{% step %}

### Let the AI use it

Leave **Used by AI** on if the AI may use the reply for its suggestions.
{% endstep %}

{% step %}

### Save

Click **Create**. The reply is now available to your team in every conversation of the linked properties.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
A saved reply from your PMS can only be changed in the PMS. Guestway syncs the change.
{% endhint %}

## Use it in the inbox

{% stepper %}
{% step %}

### Find the reply

In a conversation, type **/** in the message box and search for the reply. You can also click **Choose from saved replies**.
{% endstep %}

{% step %}

### Insert it

Click the reply. It goes in at your cursor, and the placeholders fill in with the details of the reservation, the listing and the guest.

{% hint style="success" %}
Change the reply a little when it matters. One sentence about something the guest wrote turns a template into a personal answer.
{% endhint %}
{% endstep %}
{% endstepper %}

## Related

* [Saved replies](https://docs.guestway.io/inbox-and-messaging/saved-replies.md): all fields and types
* [How to reply to a guest](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/how-to-reply-to-a-guest.md)
* [About how the AI answers guests](https://docs.guestway.io/ai/ai-center/about-how-the-ai-answers-guests.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/inbox-and-messaging/saved-replies/how-to-create-a-saved-reply.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.
