> For the complete documentation index, see [llms.txt](https://docs.zipchat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipchat.ai/channels/email-channel.md).

# Email Support & Draft Mode

Forward your support inbox to Zipchat so the AI agent answers customer emails or writes drafts. Covers forwarding, custom sending domains and draft mode.

Zipchat answers your customer support emails. You forward your support mailbox to a Zipchat address, and the agent replies or prepares drafts for your team to approve.

![Email channel settings in Zipchat](https://2043605213-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvYpZDb6HsnLHFu8ZygCS%2Fuploads%2Fgit-blob-070c7db35e017b3361e9f2c70232e5f24001d5a9%2Femail-channel-settings-2026.png?alt=media)

## Step 1: Receive emails

1. Go to **Channels** and click **Turn on** on the Email card.
2. In **Receiving emails**, copy your unique Zipchat email address.
3. Set up a forwarding rule from your support mailbox to that address.

The Email settings include forwarding guides for Shopify Email, Gmail, Microsoft Outlook and cPanel.

Zipchat only sees the emails your mailbox forwards after you set up the rule. It does not connect to your mailbox and does not read past emails or other folders.

## Step 2: Send from your own domain

By default, replies are sent from your Zipchat email address. A shared Zipchat address is faster to set up, but its emails are more likely to land in spam. For the best deliverability, connect your own domain:

1. In **Sending emails**, click **Add domain** and enter your domain.
2. Click **Verify** and add the DNS records shown. The settings include guides for Shopify, GoDaddy, Namecheap and Cloudflare.

Connecting your sending domain adds 3 CNAME records: 2 for email authentication (DKIM) and 1 for the return path. They do not change your MX records. Your current email provider (Google Workspace, Microsoft 365 or any other) keeps working as before. The settings can also suggest a DMARC record.

Your domain becomes active after both checks pass: the DNS records for sending and the forwarding of your mailbox for receiving.

## Email settings

Once the channel is connected, open **Channels → Email → Settings**. The **Overview** panel shows your address, sending domain, whether emails are active and whether draft mode is on. **Support address** shows the address to forward your mailbox to. Use **Test channel** to send a test email and **Disconnect** to turn the channel off.

### Appearance tab

* **Signature:** added to every AI reply. Bold, italic, links, images (https) and simple tables are allowed.
* **Provider branding:** choose **AI generated by Zipchat** or **Sent via Zipchat**.

![Email appearance settings in Zipchat](https://2043605213-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvYpZDb6HsnLHFu8ZygCS%2Fuploads%2FifKZvcSMKps8W1ilM9KU%2Femail-channel-appearance-2026-11.webp?alt=media)

The **AI generated by Zipchat** option tells customers that an AI wrote the reply. Check with your legal advisor which AI disclosures your business needs. See [Security & Privacy](https://docs.zipchat.ai/settings-tracking-and-security/security-and-privacy.md).

### Features tab

* **Draft mode:** approve every reply before it is sent. The agent writes each reply as a draft, and your team reviews and sends it from the Zipchat inbox. Email draft mode is separate from draft mode on other channels.

In draft mode, the agent waits about 20 seconds before it writes a draft, so several quick emails get one draft. While a draft is waiting, a new email from the same customer does not create a second draft.

## How email conversations work

* Replies stay in the same thread when the customer answers with Reply.
* The agent reads image attachments: JPG, PNG, GIF, BMP and WebP. It does not read PDFs or other files attached to emails.
* It can look up the customer's order.
* Each email thread has a fixed cap of 12 AI replies, and it cannot be changed. After 12 AI replies in the same thread, the AI stops so your team takes over. This prevents endless loops between bots.
* The agent does not reply when it is only in CC.
* The agent does not reply to emails sent by Zipchat itself, which prevents reply loops.

## Stop replies to newsletters and automatic emails

When you connect email, Zipchat turns on the **Skip conversation** skill with starting instructions for no-reply senders. Edit its instructions in [Agentic Skills](https://docs.zipchat.ai/ai-training-and-rules/agentic-skills.md) to add the emails the agent should ignore, such as newsletters, out-of-office replies or supplier messages. The agent then skips them, and they stay visible in your inbox.

## Your team's replies

Reply from the Zipchat [Inbox](https://docs.zipchat.ai/inbox-and-team-collaboration/managing-conversations.md). Take over the conversation, write your reply and attach files if needed. If attachments add up to more than 15 MB, Zipchat sends download links instead. Manual replies do not use your AI replies.

Replies you send from Gmail or Outlook outside Zipchat do not always appear in the Zipchat thread. Reply from the Zipchat inbox to keep the full conversation in one place.

If you use [Human Escalation](https://docs.zipchat.ai/ai-training-and-rules/forward-request.md) with email notifications, send them to an address that does not forward to Zipchat. Otherwise the notification comes back into your inbox as a new email.

## Other helpdesks

The email channel works with any mailbox that can forward emails. For helpdesks:

* **Zendesk:** native channel. See [Zendesk](https://docs.zipchat.ai/channels/email-channel/zendesk.md).
* **Freshdesk:** a ready-made skill creates a ticket with a summary and the full chat transcript.
* **Gorgias:** ready-made integration in beta, available on request.
* **Other helpdesks,** such as Intercom or Help Scout: connect them with a custom skill that uses the helpdesk's API. See [Agentic Skills](https://docs.zipchat.ai/ai-training-and-rules/agentic-skills.md).

## FAQ

### Why did a customer reply open a new conversation?

The customer wrote a new email instead of replying, or changed the subject in a way that dropped the reply headers.

### How many AI replies can one email thread get?

12. After 12 AI replies in the same thread, the AI stops and your team continues from the inbox. This prevents endless loops between bots.

### Can I change the 12-reply cap?

No. The cap of 12 AI replies per email thread is fixed and cannot be changed.

### Will connecting my domain affect my current email?

No. Zipchat adds 3 CNAME records and does not change your MX records. Your current email provider, such as Google Workspace or Microsoft 365, keeps working as before.

### Does the agent read PDF attachments?

No. It reads image attachments only. Add PDFs you want it to know, such as manuals, to your [Knowledge Base](https://docs.zipchat.ai/ai-training-and-rules/knowledge-base.md).

### Can my team reply from Gmail or Outlook?

Replies sent outside Zipchat do not always sync into the Zipchat thread. Reply from the Zipchat inbox to keep threads complete.

### How do I remove tracking parameters from links in emails?

Turn off **Enable UTM tracking** in **Channels → Configuration → Tracking settings**.

### Can several mailboxes forward to the same agent?

Yes. For example, both sales@ and support@ can forward to your Zipchat address.

### Need help with forwarding or DNS?

Contact <support@zipchat.ai>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zipchat.ai/channels/email-channel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
