> 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/domains/how-to-add-a-custom-email-domain.md).

# How to add a custom email domain

This guide shows you how to send and receive guest emails from your own subdomain, such as guests.yourcompany.com.

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

* You need a domain that you own, for example *yourcompany.com*. You create a subdomain under it.
* You need access to the DNS settings of your domain provider, for example GoDaddy, Cloudflare or Namecheap.
* You have the **Admin** or **Super admin** role, or a role with **Advanced configuration** → **Domains** at **Edit**. See [Users and roles](/account-and-administration/users-and-roles.md).
  {% endhint %}

## Add your subdomain

{% stepper %}
{% step %}

### Open the domains

Go to **Settings** → **Domains** and open the **Email domains** tab.
{% endstep %}

{% step %}

### Add the subdomain

Click **Add email domain**. Enter the **Domain**, for example *guests.yourcompany.com*, and click **Create**.

{% hint style="success" %}
Use a subdomain that is only for Guestway, not your main domain. The Guestway records then do not get in the way of your company email.
{% endhint %}
{% endstep %}
{% endstepper %}

## Add the DNS records

{% stepper %}
{% step %}

### Copy the records

Open the domain. Copy each record with its copy icon: **DKIM**, **DMARC**, **MX** and **SPF**.

If someone else manages your domain, click **Send Email with verification info** and send them the records.
{% endstep %}

{% step %}

### Add them at your domain provider

In the DNS settings of your domain provider, add every record exactly as shown. Save.

Changes at your domain provider can take from a few minutes up to 24 hours.
{% endstep %}
{% endstepper %}

## Verify the domain

{% stepper %}
{% step %}

### Check the records

In **Settings** → **Domains**, click the check icon of the domain (**Check email domain verification**).
{% endstep %}

{% step %}

### Confirm the status

When every record is found, the domain shows **Verified**.

If it shows **Not Verified**, check that each record is pasted exactly, without extra spaces or missing characters. Wait, and check again.
{% endstep %}
{% endstepper %}

## Create your Guestway email address

{% stepper %}
{% step %}

### Add the address

Go to **Settings** → **Inbox**. In **Custom guest inbox emails**, enter a prefix such as *info*, *bookings* or *reservations*, select your verified domain and click **Add**.

The address looks like *<info@guests.yourcompany.com>*.

{% hint style="success" %}
Pick prefixes that match what guests want, such as *bookings@* or *reservations@*. You can add more than one prefix, for example for sales and support. All of them arrive in the same inbox.
{% endhint %}
{% endstep %}

{% step %}

### Link it to your branding

Click **Go to branding** and select the address in your branding profile. A custom address works only when it is linked to a branding. See [Branding](/guest-experience/branding.md).
{% endstep %}

{% step %}

### Update your website

On the contact or inquiry form of your direct booking website, replace your old address with the new one. From then on, every message to that address arrives in the **Inbox**.
{% endstep %}
{% endstepper %}

## Related

* [Domains](/inbox-and-messaging/domains.md#email-domains): the DNS records and statuses
* [Inbox](/inbox-and-messaging/inbox.md)
* [About email forwarding](/inbox-and-messaging/inbox/about-email-forwarding.md): forwarding or your own domain


---

# 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/domains/how-to-add-a-custom-email-domain.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.