> 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/about-email-forwarding.md).

# About email forwarding

This page explains why you forward guest emails to Guestway, and when your own email domain is the better choice.

## Why forwarding is needed

Many guests do not write through a booking channel. They use the contact form of your direct booking website, or they send an email to an address such as *<reservations@yourcompany.com>*. Guestway can only show the emails that reach it. Forwarding sends a copy of each email to your Guestway address, so these guests land in the same inbox as the conversations from the channels, WhatsApp and SMS.

Forwarding is the quickest way to get there. You keep the address that guests already know, and nothing changes for them.

## Forwarding or your own domain

There are two ways to bring guest emails into Guestway, and each has a cost.

With **forwarding**, the setup takes a few minutes. But when your team replies from Guestway, the email is sent from your Guestway address, such as *<yourcompany@in.gstw.io>*, and not from your original address.

With **your own email domain**, you send and receive directly from a subdomain such as *guests.yourcompany.com*, for example *<hello@guests.yourcompany.com>*. No forwarding is needed, and the address looks more professional. In return, you must add and verify the domain at your domain provider. A new domain also has no sending history yet, so some emails may land in spam until its reputation builds. And the address is a little longer because of the subdomain.

Forwarding suits most teams that want to start fast. Your own domain is worth the extra setup when the sender address matters to your guests.

## Which channels use it

Forwarding is for everything that arrives as an email: website inquiries, direct bookings and guests who write to your own address. Booking.com also delivers its guest messages by email when your PMS is Apaleo or Mews. See [How to connect Booking.com](https://docs.guestway.io/integrations/online-travel-agencies-ota/booking.com.md).

## Related

* [How to forward emails to Guestway](https://docs.guestway.io/inbox-and-messaging/inbox/how-to-forward-emails-to-guestway.md)
* [How to add a custom email domain](https://docs.guestway.io/inbox-and-messaging/domains/how-to-add-a-custom-email-domain.md)
* [Inbox](https://docs.guestway.io/inbox-and-messaging/inbox.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/inbox/about-email-forwarding.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.
