> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect email
> Bring your company email domain into your Conduit inbox
## Overview
The platform enables teams to:
* Send and receive emails using company domain addresses
* Connect individual Gmail accounts
* Centralize all email communication within a single workspace
* Support multiple email addresses from the same domain (support@, billing@, sales@)
* Integrate with Outlook, Gmail, and company email providers
## Two ways to connect
Go to **Settings > Email** under Channels. There are two independent sections.
| Section | What it is for |
| - | - |
| **Connected domains** | Connect a company email domain, such as @yourcompany.com, and add addresses under it. Requires DNS access and forwarding. |
| **Gmail accounts** | Connect an individual Gmail account directly. You authorize Conduit through Google, with no DNS records to add. |
You can use either or both. Connected domains suit shared team addresses such as support@ or help\@. Gmail accounts suit an individual mailbox you want to work from inside Conduit.
## Connecting a domain
Click **Add domain** next to Connected domains, then add a full email address on that domain. Once the domain exists, click **Configure** next to it to work through five sections:
1. **Domain**: the domain you send and receive on, plus the option to delete it
2. **Email addresses**: up to 20 addresses per domain, with a minimum of one
3. **Receiving emails**: your inbound forwarding address, ending in `@inbound.postmarkapp.com`
4. **Sending emails**: the TXT and CNAME records to add to DNS, each showing a verification status, with a **Re-verify DNS** button
5. **Workspace name**: the name recipients see alongside the sender's first name
Receiving and sending are configured separately. See [Receiving Emails in Conduit](/setup/channels/email/receiving-emails-in-conduit) and [Sending Emails from Conduit](/setup/channels/email/sending-emails-from-conduit).
## Connecting a Gmail account
Click **Add Gmail account** next to Gmail accounts and sign in through Google to authorize the connection. This path does not involve DNS records or forwarding rules. See [Connect Gmail with OAuth](/setup/channels/email/connect-gmail-with-oauth) for the full steps.
## Managing addresses
Addresses appear beneath their domain on the Email settings page. Use the **ยทยทยท** menu next to an address to **Set as default** or **Delete** it.
## Requirements
* Address limit: up to 20 email addresses per domain, with at least one required
* DNS access: connecting a domain requires the ability to edit DNS records for that domain, or someone who can
* Public providers such as @yahoo.com, @icloud.com, and @hotmail.com cannot be connected as domains. Gmail is supported through the Gmail accounts section. See [Connect Gmail with OAuth](/setup/channels/email/connect-gmail-with-oauth).
If you receive Booking.com guest messages by email, use a connected domain and forward those messages to your Conduit inbound address. Do not use a connected Gmail account for Booking.com messages. Gmail OAuth does not match Booking.com relay emails to reservations, so they may appear as separate contacts in the Unmapped inbox instead of in the guest conversation. Follow the [Booking.com setup steps](#bookingcom-guest-messages) below.
## Booking.com Guest Messages
The Booking.com email integration processes guest messages through Conduit's inbound email path, powered by Postmark. It does not process these messages through a connected Gmail mailbox.
### How Processing Works
When a guest writes through Booking.com:
1. Booking.com sends a relay email from an address ending in `@guest.booking.com` or `@mchat.booking.com` to your selected company email address.
2. Your email provider forwards the message to your Conduit inbound address, which ends in `@inbound.postmarkapp.com`.
3. Conduit reads the Booking.com confirmation code from the relay address, matches it to a reservation from your connected PMS, and adds the message to the guest's Booking.com conversation.
### Setup Steps
[Connect the PMS](/setup/pms/connect-pms) that contains your Booking.com reservations. Conduit uses its reservation data to match each incoming message to the correct guest conversation.
Go to **Settings > Email** and add the company domain address that receives your Booking.com notifications. Do not connect this address with Gmail OAuth for Booking.com processing.
Copy the workspace inbound address ending in `@inbound.postmarkapp.com`, then [configure your email provider to forward messages](/setup/channels/email/receiving-emails-in-conduit) from the company address to it. If you use Google Workspace, create an admin routing rule instead of relying on the connected Gmail mailbox.
Go to **Settings > Connections > Booking.com** and select the same company email address. Make sure Booking.com sends guest message notifications to this address.
Send a Booking.com guest message for a reservation already synced from your PMS. Confirm that it appears in the guest's Booking.com conversation, not as a separate contact in the Unmapped inbox.
## Prerequisites
Users need:
* **For a Gmail account:** permission to manage channels in Conduit and access to the Google account being connected
* **For a connected domain:** a Conduit workspace inbound address (ends with `@inbound.postmarkapp.com`), admin access to DNS settings, and admin access to the email provider (Google Workspace Admin console for Gmail)
## Email Address Recommendations
Recommended formats: help@, support@, contact@, hello@
Personal addresses like cole@ or flor@ are discouraged but may work depending on organizational needs.
## Plus-addressing Support
Conduit supports email plus-addressing (also called subaddressing). Emails sent to `support+tag@yourdomain.com` will be routed to the same inbox as `support@yourdomain.com`. The full address including the `+tag` is preserved on the message for your reference.
This is useful for tracking where inbound emails originate from, filtering, or testing.
## How the sender appears
Each user sends emails under their own first name plus your workspace name, so a recipient sees something like "Punn at Conduit". Set the workspace name under section 5 on the domain configuration page.
For receiving email copies in company inboxes, contact [support@conduit.ai](mailto:support@conduit.ai) for custom solutions.
## Frequently asked questions
Up to 20 per domain, and you need at least one. Add them by clicking **Configure** next to the domain under **Settings > Email**, then **Add email**. See [Additional email addresses](/setup/channels/email/alternate-email-addresses).
Yes. Click **Add domain** next to Connected domains. Each domain has its own DNS records, its own forwarding, and its own set of addresses.
Yes, through the **Gmail accounts** section rather than Connected domains. Click **Add Gmail account** and authorize through Google. No DNS records or forwarding rules are needed for this path.
Shared addresses work best: help@, support@, contact@, or hello\@. Personal addresses such as cole@ or flor@ may work but are discouraged, since conversations then look like they belong to one person rather than the team.
Anything sent to `support+tag@yourdomain.com` routes to the same inbox as `support@yourdomain.com`, with the full address preserved on the message. Use it to track where inbound emails came from, to filter, or to test.
The sender's first name followed by your workspace name, for example "Punn at Conduit". Change the workspace name in section 5 of the domain configuration page.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.