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

# Email in Boom

> Send email as your own domain, get your customers' replies in the Boom inbox, and bring your support address, all from Settings › Email.

**Settings › Email** has two parts, in order:

1. **Send email**: emails from Boom go out as your own domain, for example
   `Acme <hola@acme.com>`.
   * **Your domain**: add it and its DNS records.
   * **Senders**: the names and addresses customers see. Unlocks once the
     domain is verified.
2. **Reply to customers from Boom**: your customers' replies land in the Boom
   inbox, where your team and the agent can answer them. Turn it on once
   sending shows **Ready** (a verified domain and a sender).
   * **Replies to your emails**: nothing to set up.
   * **Support address** (optional): emails sent to an address like
     `support@acme.com` land there too.

Each part shows where it stands on the right (**Not set up**, **In progress**,
**Ready**, or **Off** / **On**). Click a row to open it; a done row shows a
check mark and a green status. For the exact steps in Gmail, Google Workspace or Microsoft 365, see
[Connect your support address](https://docs.useboom.ai/email-support-address.md). To hand the technical
part to someone else, see [Email setup for your IT team](https://docs.useboom.ai/email-for-it.md).

> [!NOTE]
>
> Every workspace can receive email. An organization admin turns it on with
> **Turn on replies**, which unlocks once sending shows **Ready** (or right
> away if you had turned receiving off before); until then, emails from Boom go out exactly as before
> and replies go to your sending address.

## Send as your domain

Open the **Your domain** row (or click **Set up**). Everything happens in the
row:

1. Enter your domain and click **Add domain**.
2. The DNS records appear right away. Each shows what it's for (**Sending**,
   **Signing**, **Bounces** or **Policy**), its type, its **Name** and **Value**
   with **Copy** (the last one you copied stays marked **Copied**), and
   **Found** or **Not found yet**. Add them where you manage your domain (your
   registrar or DNS host).
3. Click **Check now**. Changes can take up to 24 hours to show up. The row
   shows **Waiting for DNS** until every record is found, then **Verified**.
   On domains connected on Boom's newer sending setup, records already in your
   DNS show **Found, confirming…** while they are confirmed (usually a few
   minutes), and the row turns **Verified** on its own while it is open.
4. Once verified, the row shows your domain and a link to the **Domain and
   DNS** page. The **Senders** row below it unlocks and shows your default
   sender: click **Add sender** (or **Manage**) to add the names and
   addresses customers will see.

Someone else manages your DNS? Click **Send to IT** next to **Check now**: the
instructions list the records still missing. Typed the wrong domain? **Change
domain** opens the **Domain** page, where you can remove it.

These records don't touch the email you already receive: your main mail
records stay as they are. [Email setup for your IT team](https://docs.useboom.ai/email-for-it.md)
explains each record. Open and click tracking needs one more record, on the
**Domain** page; see [Email tracking](https://docs.useboom.ai/email-tracking.md).

## Replies: nothing to set up

Under **Reply to customers from Boom**, click **Turn on replies**, then
confirm. That's it: nothing changes
in your mailbox. Turning on means replies to the emails you send come into the
Boom inbox, each email gets its own conversation, email conversations close
after 7 days of quiet, and your existing email conversations move onto the new
mailbox. To stop, an admin uses **Advanced settings › Turn off receiving**:
new emails go out without a Boom reply address, while replies to emails
already sent still arrive. **Turn on replies** brings it back with the same settings.

From then on, when a customer replies to an email you sent from Boom, the
reply shows up in the inbox, in the same conversation and thread as the email
it answers. The **Replies to your emails** row shows **Working**. Open it to see where replies go and when
the last one arrived:

| You see | What it means |
| - | - |
| Replies go to **Boom** | Every email carries its own private reply address, so a reply lands back in the right conversation. This is the default. |
| Replies go to **[support@acme.com](mailto:support@acme.com)** | You turned on **Replies go to your support address** under **Advanced settings**, and that address shows **Receiving** (see below). Replies reach your own inbox and Boom. |

A template or journey email step that sets its own Reply-To keeps it: that
address wins over both.

## Bring your support address

If customers already write to an address like `support@acme.com`, you can get
those emails in Boom too. Your mailbox keeps every email as it does today;
your email provider sends a copy to Boom.

1. On the **Support address** row, click **Connect**.

2. Enter the address your customers already write to and click **Save**.

3. Check the provider on the same line. Boom pre-selects it from your
   address's domain when it can tell; you can change it:

   | Choice | Pick it when | Needs an admin? |
   | - | - | - |
   | **Gmail** | An `@gmail.com` address | No |
   | **Google Workspace** | Your own domain on Google, like `hola@yourcompany.com` | Yes, a Google Workspace admin |
   | **Microsoft 365** | Outlook or Office 365 with your own domain | Yes, a Microsoft 365 admin |

4. Follow the two or three short steps the row shows for that provider, using
   the **Boom address** below them (it has a **Copy** button).
   [Connect your support address](https://docs.useboom.ai/email-support-address.md) has the same steps in
   full.

5. Click **Send test** (see below).

### Test it

**Send test** sends Boom's check email (titled **Boom forwarding check**) to
your support address and waits for it to come back through your rule. The
result shows right below the button:

* **Received · connected**: the status changes to **Receiving**.
* **Didn't arrive yet. Check:**, after 90 seconds, with what to check for your
  provider. A new Google Workspace routing rule or Microsoft 365 mail flow
  rule can take up to an hour to start working. Boom keeps checking, and the
  status changes on its own when the email arrives.

You can send one test a minute; the daily check counts too. Only people who
can change settings (organization admins) see the button. Once the row shows
**Receiving**, it keeps **Send test** next to **Setup steps**, which opens the
steps again.

### Hand it to your IT person

If someone else has to make the change, click **Send to IT**, next to **Send
test**. For Google Workspace and Microsoft 365 it reads **Needs an admin · send
to IT**. It's also in the **Your domain** row while your DNS records are
missing. Check the provider (it starts on the one the row shows) and you get
the instructions as plain text with a
**Copy** button: why it's needed, any DNS records still missing, the
provider's steps, your Boom address, the check email to allow, that Boom gets
no access to your mailbox, and how to undo it.

Organization admins can also fill in **Email to**. The email comes from Boom,
and replies to it go to you, so your IT person's questions reach you. Anyone
who can view settings can copy the text.

The same information is on [Email setup for your IT team](https://docs.useboom.ai/email-for-it.md).

### What the status means

The status shows on the right of the **Support address** row (under the
address on a phone):

| Status | What it means |
| - | - |
| **Connect** button, no status | No support address yet. |
| **Waiting for the first email** | The address is saved, but no copy has reached Boom yet. Boom sends a check email within the hour and changes the status once it arrives. Gmail also shows this while it waits for you to confirm. |
| **Receiving** | Emails sent to your support address show up in the inbox. |
| **Stopped** | Emails sent to your support address stopped reaching Boom. Open the row for what to check, or see [Troubleshooting](https://docs.useboom.ai/email-troubleshooting.md#im-not-receiving-email). |

There is no green status until Boom has seen a copy come through.

### The daily check email

A copy rule can stop working without anyone noticing: an admin changes a
policy, a rule is deleted, or a spam filter catches it. So when your support
address has had no email for 3 days, Boom sends a short email titled **Boom
forwarding check** to it (at most once a day). Your customers' own emails
count as proof, so a busy inbox doesn't get one. When the check comes back
through your rule, Boom knows the copy works. You can filter it out of your
inbox.

* If one check doesn't come back and replies go to your support address,
  they switch back to Boom's private reply address, so no reply is lost while
  the copy is broken.
* If two in a row don't come back, the status shows **Stopped** and your
  organization's admins get one email about it.
* When a check comes back again, everything returns to normal on its own.
* If the check never comes back in the first week (a typo in the address, or
  the rule was never created), Boom stops sending it and the status shows
  **Stopped**. Fix the rule, then save the address again to restart the
  checks.

If your rule or filter only matches some emails, make sure it also matches the
check email, or the copy never shows as working.

### No email in 7 days

If no email at all reaches Boom for 7 days, the **Support address** row (once
it shows **Receiving**, otherwise the **Replies to your emails** row) shows **No email in 7
days**, and your organization's admins get one email about it.

### Advanced settings

The **Advanced settings** link below the reply rows opens:

* **Boom address**, for example `acme-k7q2x9@reply.useboom.ai`. Use it only in
  your copy rule. Email that looks like spam is dropped, and Boom never answers
  senders it can't verify.
* **Inbox replies sent as**: the sender your team's replies go out from. It
  must be on your verified domain (see below). If it's a no-reply address, a
  short warning links to **Senders**.
* **Replies go to your support address**: off by default, so replies go to
  Boom's private reply address. Turn it on to use your support address as the
  Reply-To while it shows **Receiving**; replies then reach your inbox and
  Boom. Changing the support address turns it off again.
* **Daily check**: the check email, as above.

## Where sent emails show up

An email Boom sends for a campaign, journey or transactional message doesn't
open a conversation in your inbox views. It waits in the inbox's **Sent** view,
newest first, with the campaign's name, and a **Not delivered** mark when it
bounced. The moment the customer replies, the conversation moves into your
inbox with the original email above the reply.

You can still find every sent email from the campaign's entry in the inbox
sidebar, from search, and on the person's profile.

## Start an email from the inbox

With receiving on, the **+** at the top of the inbox sidebar offers **New
email** next to **New WhatsApp message**. Inside the **Email inbox** view it
opens a new email straight away.

1. In **To**, type a name or an email address. Pick someone from your
   contacts, or pick **Send to** to write to an address Boom doesn't have yet.
2. Add a **Subject** and your message.
3. Press **⌘ Enter** (**Ctrl Enter** on Windows), or click **Send**.

The email goes out from the address shown at the bottom (the same one your
replies use), and the conversation opens on it, assigned to you. If you
already have a conversation with that person, the email starts a new thread
in it under the new subject (or, with one conversation per email thread, a
conversation of its own). Their answer comes back to that thread, and your
next reply goes there too. Unlike a campaign email, it doesn't wait in
**Sent**: you're the one waiting for the answer.

Boom doesn't send to an address that marked your email as spam. If the person
is on your Do Not Contact list, you need to confirm before **Send** works, and
the override is recorded.

## One conversation per email thread

Boom can show each email thread as its own conversation, with its own status,
assignee and row in the inbox, instead of one conversation per customer. A
customer who writes about a billing question and, separately, about a delivery
then gets two conversations: resolving one leaves the other open. Replies always
land in the conversation of the email they answer. This is how every workspace
works as soon as replies are turned on.

The **Conversations** list in the customer panel, on the right of the inbox,
shows that person's other conversations on every channel, newest first, so a
teammate on one thread can see and open the others. With AI drafts on, the
agent also reads the last few messages of the customer's other email threads
(word for word, shortened), but
only when the email it is answering comes from a verified sender (see
[Email data and security](https://docs.useboom.ai/email-data-security.md)).

## What the agent does with email

AI drafts are a separate switch, turned on by Boom on request. With
receiving on and AI drafts off, customers' emails land in the inbox and your
team answers them; the agent stays out of email conversations.

The agent never sends an email by itself. For a customer's email it writes a
**draft** in the conversation, and someone on your team clicks **Approve**,
**Edit** or **Discard**. Approved replies go out as one email in the same
thread, with a short line saying the reply was drafted with AI assistance. You
can edit the reply, but not that line.

If the customer writes again before anyone approves, the agent writes a new
draft that has read everything so far, and the older one is greyed out as
**Replaced by a newer draft**. Only the newest draft can be sent, so a
customer never gets two answers to the same question.

The agent does not answer automatic replies (out-of-office, bounces, mailing
lists), and it does not reply to Gmail's forwarding confirmation.

If an approved reply can't be sent (for example the customer's address bounced
before), the reply shows as failed with the reason, and the draft goes back to
waiting so you can approve it again once the problem is fixed. Boom doesn't
send replies to an address that marked your email as spam. If the address
bounced before, the reply box warns you, and you decide whether to send.

## Unverified senders

Anyone can type any address into the From line of an email. Boom checks each
email's sender (SPF, DKIM and DMARC) and marks those it cannot confirm as
**Unverified sender** in the inbox. Your team can read and answer them, but
Boom doesn't act on them by itself: the agent doesn't draft a reply, and a
journey waiting for the customer's reply keeps waiting (or times out as
usual). A sender who isn't part of the thread counts as unverified too. For a
confirmed sender who isn't the conversation's own customer (for example mail
relayed through a forwarding service), the agent drafts a reply but will not
share account details and cannot use tools that read customer data.

## Attachments and spam

PDFs, images, Word, Excel and PowerPoint files, and plain text or CSV files
appear on the email in the inbox, and the text of PDFs is available to your
team. Archives, programs, HTML and SVG files are not stored; the email lists
them as skipped. Email that the receiving service flags as a virus is not
delivered to Boom.

Email it flags as spam is dropped too, unless the sender's domain proves the
email is really theirs (DMARC): then it appears in the inbox labelled
**Marked as spam** (or **Possible spam**) for your team to judge, and the agent
and journeys ignore it.

## Journeys

With receiving on, a journey's **Send email** step can be followed by
**Wait for reply** or **Manage conversation**: a customer's reply to that email
wakes the journey, just like a WhatsApp reply. A reply from an
[unverified sender](#unverified-senders) doesn't.

## Related

> [card] [Connect your support address](https://docs.useboom.ai/email-support-address.md)
>
> Step-by-step for Gmail, Google Workspace and Microsoft 365.

> [card] [Email setup for your IT team](https://docs.useboom.ai/email-for-it.md)
>
> What to add, what it changes, and how to undo it.

> [card] [Email data & security](https://docs.useboom.ai/email-data-security.md)
>
> Where email is processed, how long it's kept, and what the AI sees.

> [card] [Email troubleshooting](https://docs.useboom.ai/email-troubleshooting.md)
>
> Not receiving email, replies going somewhere else, and more.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.