Skip to main content

Overview

The platform enables teams to:
  • Send and receive emails using company domain addresses
  • 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

Requirements

Email domain connection

Allowed:
  • Multiple emails from the same domain
  • Company domain-based addresses only
Limitations:
  • One domain per workspace maximum
  • Up to 10 emails per domain
  • Public email providers (@gmail.com, @yahoo.com, @icloud.com, @hotmail.com) are not supported
These limits apply when connecting an email domain. To connect an individual Gmail or Google Workspace account directly, use Gmail OAuth. This method does not require email forwarding or DNS records.
If you receive Booking.com guest messages by email, use an email domain connection and forward those messages to your Conduit inbound address. Do not use a connected Gmail mailbox 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 below.

Setup Process

Choose the setup method that matches your email provider:

Gmail or Google Workspace

Connect the account directly with OAuth:
  1. Connect Gmail with OAuth
This option is not supported for Booking.com guest messages. If the mailbox receiving Booking.com messages is hosted by Google Workspace, use the email domain connection below and configure forwarding instead.

Email domain connection

Use email forwarding and domain authentication with any provider, including Google Workspace:
  1. Receiving Emails in Conduit
  2. Sending Emails from Conduit

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.postmark.app.
  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

1

Connect your PMS

Connect the PMS that contains your Booking.com reservations. Conduit uses its reservation data to match each incoming message to the correct guest conversation.
2

Connect your company email domain

Go to Settings > Connected Channels > 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.
3

Forward messages to Conduit

Copy the workspace inbound address ending in @inbound.postmark.app, then configure your email provider to forward messages from the company address to it. If you use Google Workspace, create an admin routing rule instead of relying on the connected Gmail mailbox.
4

Select the Booking.com email

Go to Settings > Connections > Booking.com and select the same company email address. Make sure Booking.com sends guest message notifications to this address.
5

Verify the connection

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 Gmail OAuth: permission to manage channels in Conduit and access to the Google account being connected
  • For an email domain: a Conduit workspace inbound address (ends with @inbound.postmark.app), admin access to DNS settings, and admin access to the email provider

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.

Email Title Format

When you start sending emails from Conduit, the title of the email in the recipient’s inbox will be: “Your Name + From [Workspace Name]”
For receiving email copies in company inboxes, contact support@conduit.ai for custom solutions.