> 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/inbox.md).

# Inbox

The Inbox settings hold your Guestway email addresses, the senders you block and the message mediums your team can use.

## General

The inbox settings are in **Settings** → **Inbox**.

| Field                         | What it does                                                                                                                                                                      | Limits                                                                                                                                                                                                             |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Guest inbox email**         | Your Guestway address, for example *<yourcompany@in.gstw.io>*. Every email sent to it appears in the inbox. The copy icon copies it.                                              | Read-only.                                                                                                                                                                                                         |
| **Custom guest inbox emails** | More addresses on your own domain, for example *<info@guests.yourcompany.com>*. Enter a prefix, select a domain and click **Add**. Every email sent to them appears in the inbox. | Only fully verified email domains. See [Domains](https://docs.guestway.io/inbox-and-messaging/domains.md). The address must also be linked to a [branding](https://docs.guestway.io/guest-experience/branding.md). |

When you delete a custom address, new messages to it no longer appear in the inbox.

## Blocked Emails

Emails from a blocked address are dropped before they reach the [Unified AI inbox](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox.md).

| Field                            | What it does                                    | Limits                   |
| -------------------------------- | ----------------------------------------------- | ------------------------ |
| **Enter email address to block** | The address to block. **Add** or Enter adds it. | Must be a valid address. |

A sender can also be blocked from a conversation without a reservation, with **Block email address**. The address then shows in this list. The trash icon removes an address from the list.

## Blocked Domains

Emails from any address of a blocked domain are dropped before they reach the inbox, for example from promotional senders or notification addresses.

| Field                           | What it does                                                  | Limits                       |
| ------------------------------- | ------------------------------------------------------------- | ---------------------------- |
| **Enter email domain to block** | The domain to block, without the @. **Add** or Enter adds it. | Must be a valid domain name. |

The trash icon removes a domain from the list.

## Allowed Message Mediums

This card sets which message mediums your team can use in the reply bar of the inbox. A medium that is off is hidden for that type of conversation.

| Section                                              | What it covers                                                                       |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **PMS conversations**                                | One section for each connected PMS: the conversations linked to that PMS.            |
| **Other conversations**: **New guest conversations** | Guests without a PMS reservation, such as unknown senders and website chat contacts. |

The mediums are **Channel/OTA Chat**, **WhatsApp**, **SMS**, **Email**, **Instagram**, **Messenger**, **Guest Portal** and **Website Chat**. A medium with more than one provider or account has one toggle for each. **Guest Portal** and **Website Chat** are set once for the organization.

## Related

* [How to forward emails to Guestway](https://docs.guestway.io/inbox-and-messaging/inbox/how-to-forward-emails-to-guestway.md)
* [About email forwarding](https://docs.guestway.io/inbox-and-messaging/inbox/about-email-forwarding.md)
* [Domains](https://docs.guestway.io/inbox-and-messaging/domains.md)
* [Unified AI inbox](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox.md#message-mediums)


---

# 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/inbox.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.
