> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom email domains

> Configure a custom email domain so outbound messages from Ravenna use your organization's domain instead of mail.ravenna.ai.

By default, Ravenna sends outbound email from `mail.ravenna.ai`. Configure a custom email domain to send from your own domain instead, improving brand recognition and email deliverability.

## Prerequisites

Before you start, confirm you have:

* Organization admin access in Ravenna
* Access to your domain's DNS management (e.g., Cloudflare, Route 53, GoDaddy)
* The domain you want to send from (e.g., `support.yourcompany.com`)

<Info>
  You can configure a subdomain (like `support.yourcompany.com`) or your root domain. Subdomains are recommended so existing email delivery is not affected.
</Info>

***

## Add a custom domain

<Steps>
  <Step title="Open email settings">
    Navigate to **Organization Settings > Email** from the settings sidebar.
  </Step>

  <Step title="Add your domain">
    Click **Add domain** and enter the domain you want to send from. Ravenna generates the DKIM DNS records you need to add.
  </Step>

  <Step title="Copy DNS records">
    Ravenna displays the DKIM records (CNAME entries) required for verification. Copy each record's name and value.
  </Step>

  <Step title="Add records to your DNS provider">
    Log in to your DNS provider and create the CNAME records shown in Ravenna. The exact steps vary by provider, but you typically navigate to DNS settings for your domain and add each record as a new CNAME entry.
  </Step>

  <Step title="Verify the domain">
    Return to Ravenna and click **Verify**. Ravenna checks that the DNS records resolve correctly. If verification fails, wait a few minutes for DNS propagation and try again.
  </Step>
</Steps>

***

## Verification status

After adding DNS records, your domain moves through these states:

| Status       | Meaning                                                                                 |
| ------------ | --------------------------------------------------------------------------------------- |
| **Pending**  | DNS records have not been verified yet. Click **Verify** to check.                      |
| **Verified** | All DNS records are correctly configured. The domain is ready to use.                   |
| **Failed**   | Verification could not confirm the DNS records. Check your DNS configuration and retry. |

<Info>
  DNS changes can take up to 48 hours to propagate, though most providers propagate within minutes. If verification fails immediately after adding records, wait and retry.
</Info>

***

## Use a verified domain

Once verified, your custom domain becomes available as the sender for email channels. Configure it in your workspace's channel settings:

1. Navigate to **Workspace Settings > Channels**
2. Select or create an email channel
3. Choose your verified domain as the outbound sender address

All outbound email from that channel (replies, notifications, and automated messages) will use your custom domain.

***

## Troubleshooting

**Verification keeps failing:**

* Confirm the CNAME records match exactly (no trailing dots unless your provider requires them)
* Check that you added records to the correct domain or subdomain
* Wait at least 15 minutes after adding records before verifying
* Use a DNS lookup tool to confirm the records are publicly resolvable

**Email delivery issues after verification:**

* Ensure your domain does not have conflicting SPF or DMARC records that reject messages from Ravenna's sending infrastructure
* Check that the domain is not on any blocklists

***

## Remove a domain

To remove a custom domain, navigate to **Organization Settings > Email**, find the domain, and click **Delete**. Channels using that domain revert to sending from `mail.ravenna.ai`.

<Warning>
  Removing a verified domain immediately affects all channels using it. Update your channel settings before removing a domain to avoid sending disruptions.
</Warning>