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

# Helpdesk email settings: addresses, signatures, and display names

> Configure email addresses, display names, signatures, and previews for your Helpdesk.

Helpdesk email settings control which of your verified addresses the Chatbase Helpdesk uses for tickets, the name customers see in the **From** field, the signature on your team's replies, and who hears about delivery failures. You'll find them on your AI agent under **Settings → Helpdesk → Email**, on any plan that includes the Helpdesk.

This page only lets you pick addresses that are already verified. You add a domain, set up forwarding and add its DNS records on the AI agent's **Settings → Email** page. See [Email settings](https://chatbase.co/docs/user-guides/chatbot/email-settings.md).

## Before you start: add and verify your domain

On **Settings → Email**, click **New email** and work through the four steps: **Your email address**, **Verify automatic forwarding**, **Authenticate your domain** (add the DNS records, then click **Validate**), and link the address to the Email channel, the Helpdesk, or both. If no address is verified yet, the Helpdesk email page shows a **Configure email settings** link that takes you there.

The domain step shows three records. Copy the exact names and values from the drawer, since the values are generated for your domain:

| Record | Type | Name |
| - | - | - |
| DKIM | CNAME | `chatbase._domainkey` |
| SPF | CNAME | `outbound.chatbase` |
| DMARC | TXT | `_dmarc`, with the value `v=DMARC1; p=none` |

The SPF record is a CNAME that sets a custom sending (MAIL FROM) domain, not a `v=spf1` TXT record. At least one address on the domain must have forwarding verified before you can validate. DMARC doesn't block validation: it passes when any TXT record exists at `_dmarc`.

> [!WARNING]
>
> A sending domain can be verified on only one AI agent at a time. Verifying it on a second AI agent moves it there and removes it from the first.

## Email Configuration

The **Configuration** card lets you choose which email addresses will be used as your Helpdesk inboxes and who should be notified about deliverability issues.

### Selecting Helpdesk emails

Under **Helpdesk email address**, you can configure one or more email addresses to receive support tickets.

**1. Add an email row**

Click **Add email** to add a new email row. Each row presents a dropdown of your available email addresses.

**2. Select an email address**

Choose an email address from the dropdown. Emails from every domain are listed; ones with DNS problems appear disabled with an issue indicator. Once you pick an email in one row, that option becomes disabled in the other rows' dropdowns.

**3. Review email status**

Each selected email is checked for three things:

* **Forwarding** - Whether email forwarding is enabled
* **DKIM** - Whether DKIM authentication is configured on the domain
* **SPF** - Whether SPF records are configured on the domain

All three must pass before you can select the address. An address that fails any of them is disabled in the dropdown and shows a badge with the number of issues, such as "2 issues".

**4. Save**

Click **Save** to apply your email configuration.

> [!WARNING]
>
> Emails missing any of the three requirements (Forwarding, DKIM, SPF) display a badge showing the number of issues. Hover over it to see which checks are failing: "Forwarding is not enabled", "DKIM is not enabled" or "SPF is not enabled". Fix forwarding in your email provider and DKIM or SPF in your domain's DNS, then validate again on **Settings → Email**. DMARC isn't one of the checks.

### Which address sends a reply

When you have several Helpdesk addresses, a reply goes out from:

1. The address the ticket was received on, if it's in your Helpdesk list.
2. Otherwise, the **first** address in the list.
3. If the list is empty, the AI agent's Chatbase address, `agent@{subdomain}.{mail-domain}`.

Tickets from the Chat Bubble have no receiving address, so replies use the first listed address, or the Chatbase address. An email is only sent when the customer gave an email address.

Until a domain passes both DKIM and SPF, replies go out from the Chatbase address instead of your domain.

[Trigger](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md) emails work slightly differently: with an empty Helpdesk list, they use any verified address on the AI agent.

### Removing an email

Click the **×** next to any email row to remove it, including the last one. If no email is configured, outgoing replies fall back to the auto-generated agent address.

| Condition | Fallback |
| - | - |
| No emails selected | Uses the auto-generated agent email: `agent@{subdomain}.{mail-domain}` |

### Deliverability alert contact

Configure which team member receives an email when outgoing Helpdesk emails fail to deliver. You can pick one workspace member, or **None**.

1. Open the **Deliverability alert contact** dropdown.
2. Select a team member from your account's member list.
3. Click **Save**.

When a Helpdesk reply fails to send or later bounces, the selected contact gets a plain-text email with the subject "Chatbase Email Channel Deliverability Issue". Whether or not a contact is set:

* The failed message on the ticket shows "This email was not delivered to the recipient.", with the bounce details.
* If the ticket has a [Slack ticket thread](https://chatbase.co/docs/user-guides/chatbot/help-desk/slack-ticket-threads.md), the failure is posted there too.

If too many emails bounce or are marked as spam, sending can be paused, and the **Settings → Email** page shows "Email sending is paused".

> [!NOTE]
>
> The deliverability alert contact is optional. If not set, no alert email is sent, but failures still show on the ticket.

### Validation rules

| Rule | Description |
| - | - |
| Non-empty email rows | Every added email row must have an email selected |
| No duplicates | The same email address cannot be selected in multiple rows |
| DNS requirements | Emails missing Forwarding, DKIM, or SPF are disabled and can't be selected |

***

## Display Name

The Display Name setting controls what recipients see in the **From** field of emails sent from your Helpdesk. This helps establish trust and brand recognition with your customers.

### Auto mode

**Automatically use support associate's name** uses the name of the support associate who responds to the ticket. Each outgoing email will show the actual agent's name, creating a more personal support experience.

For example, if agent "Jane Doe" responds to a ticket, the email appears as:

```text theme={null}
From: Jane Doe <support@yourdomain.com>
```

In this mode:

* Replies from the Helpdesk use the sender's profile name, whatever their role, workspace owners included. If the sender has no name set, the **From** field shows only the address.
* [Trigger](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md) emails carry no display name.
* Emails the AI agent sends on the [Email channel](https://chatbase.co/docs/user-guides/integrations/email.md) don't use this setting. They use the Email channel's own display name.

> [!NOTE]
>
> Automatic is the default and recommended for teams that want a personal touch in customer communications.

### Custom mode

**Use custom name** uses a fixed name you specify for all outgoing emails, regardless of which agent responds. This is useful for maintaining a consistent brand identity across all support communications.

For example, if you set the custom name to "Acme Support":

```text theme={null}
From: Acme Support <support@yourdomain.com>
```

When selecting custom mode, a text input appears where you enter the desired display name. The name cannot be empty.

### Changing the display name

1. Select either **Automatically use support associate's name** or **Use custom name**.
2. If you chose a custom name, enter it in the text field that appears.
3. Click **Save** to apply.

> [!NOTE]
>
> Changes to the display name take effect on all future outgoing emails. Previously sent emails are not affected.

***

## Email Signature

The Signature card lets you create a rich-text signature that is appended to the bottom of replies your team sends from the Helpdesk. Each AI agent has one signature. The card says the signature "appears at the bottom of every email your AI Agent sends", but it is only added to teammate replies.

### Creating a signature

1. Open the **Signature** card on the email settings page.
2. Use the rich-text editor to compose your signature. The toolbar offers text styles, bold, italic, underline, strikethrough, numbered and bulleted lists, links, and emoji.
3. Click **Save** to apply.

### Signature behavior

| Scenario | Signature applied? |
| - | - |
| Teammate replies from the Helpdesk | Yes |
| [Trigger](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md) emails | No |
| No signature content saved | No signature section rendered |

The signature is inserted exactly as written. It doesn't support variables such as the agent's name, so for a personal sign-off, use the automatic display name or a [macro](https://chatbase.co/docs/user-guides/chatbot/help-desk/macros.md).

### Editing or removing a signature

* **Edit:** Modify the content in the rich-text editor and click **Save**.
* **Remove:** Clear all content from the editor and click **Save**. An empty signature produces no signature block at send time.

> [!NOTE]
>
> Keep signatures concise. Long signatures can push the actual email content out of the visible area on mobile devices.

***

## Preview

The last card on the page is a live preview of an outgoing email. It shows the **From** line as recipients will see it (your display name followed by the selected Helpdesk address), a placeholder recipient, placeholder body text, your signature if you have saved one, and the **Powered by Chatbase** footer.

> [!NOTE]
>
> The preview uses placeholders when configuration is incomplete: `chatbase@mail.com` for a missing subdomain, and "Support Associate" for the automatic display name. Real emails always use your subdomain and the responding agent's name.

> [!NOTE]
>
> The **Powered by Chatbase** footer can be removed with the **Remove 'Powered By Chatbase'** add-on. See [Pricing](https://www.chatbase.co/pricing).

***

## Attachments

Teammates can attach up to 5 files per message, up to 25 MB each. In the email the customer receives, attachments appear as download links in the body, not as standard email attachments.

***

## Frequently asked questions

> [accordion] Where do I add and verify a domain for Helpdesk email?
>
> On your AI agent's **Settings → Email** page, with **New email**. The Helpdesk email page only lets you pick addresses that are already verified. See [Email settings](https://chatbase.co/docs/user-guides/chatbot/email-settings.md).

> [accordion] What happens if an address fails the DKIM or SPF check?
>
> It can't be used. The address is disabled in the Helpdesk address picker until forwarding, DKIM and SPF all pass. Until a domain passes DKIM and SPF, replies go out from your AI agent's Chatbase address.

> [accordion] Which address does the Helpdesk reply from when I have several?
>
> The address the ticket came in on, if it's in your Helpdesk list. Otherwise, the first address in the list, or the AI agent's Chatbase address if the list is empty.

> [accordion] Who gets told when a Helpdesk email bounces?
>
> The one member set as **Deliverability alert contact** gets an email. The failure also shows on the ticket and in its Slack ticket thread, if there is one.

> [accordion] How do I remove Powered by Chatbase from Helpdesk emails?
>
> Add the **Remove 'Powered By Chatbase'** add-on. See [Pricing](https://www.chatbase.co/pricing).


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