{"Status":true,"Message":"","Response":{"post":{"postuid":"ec2b83d1-1209-4b98-829d-1a3e03a4ce42","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"fc6490ac-7527-4f49-b06e-46f701280e85","title":"Chat Email Channel","slug":"article/chat-email-channel","html":"\u003Cp\u003EThe email channel brings your support email into your messenger. Forward your support address (for example support@yourcompany.com) to the messenger, and every email becomes a conversation in the \u003Ca href=\u0022/article/using-the-chat-inbox\u0022\u003Einbox\u003C/a\u003E. The AI agent answers it the way it answers chats, using the same knowledge sources, rules and procedures, and your team can take over at any time. Replies go back to the customer by email, in the same email thread.\u003C/p\u003E\u003Cp\u003ECustomers keep writing to the address they already know. They never need to visit your website or open the messenger.\u003C/p\u003E\u003Ch2 id=\u0022setting_up_email\u0022\u003ESetting up email\u003C/h2\u003E\u003Cp\u003EOwners and admins set up email for each messenger.\u003C/p\u003E\u003Col\u003E\u003Cli\u003EOpen your messenger and click \u003Cb\u003EIntegrations\u003C/b\u003E in its sidebar. Email is under \u003Cb\u003EChannels\u003C/b\u003E. Click \u003Cb\u003ESet up\u003C/b\u003E (or \u003Cb\u003EManage\u003C/b\u003E once it\u0027s on).\u003C/li\u003E\u003Cli\u003EUnder \u003Cb\u003EThis messenger\u0027s address\u003C/b\u003E, click \u003Cb\u003ECopy\u003C/b\u003E. This is the address you forward your mail to. Keep it private: anything sent to it arrives in your inbox.\u003C/li\u003E\u003Cli\u003ESwitch on \u003Cb\u003EReceive email\u003C/b\u003E.\u003C/li\u003E\u003Cli\u003EChoose whether \u003Cb\u003EThe AI agent answers emails\u003C/b\u003E. With it off, every email waits for your team.\u003C/li\u003E\u003Cli\u003EUnder \u003Cb\u003EReplies are sent as\u003C/b\u003E, enter the sender name customers see, such as \u0022Acme Support\u0022. Leave it blank to use the name shown.\u003C/li\u003E\u003Cli\u003EUnder \u003Cb\u003EReplies come back to\u003C/b\u003E, enter your own support address (optional, explained below).\u003C/li\u003E\u003Cli\u003EClick \u003Cb\u003ESave\u003C/b\u003E.\u003C/li\u003E\u003Cli\u003ESet up forwarding in your mail provider (below).\u003C/li\u003E\u003Cli\u003EClick \u003Cb\u003ESend me a test email\u003C/b\u003E. Reply to the test email you receive, and your reply should arrive in the inbox.\u003C/li\u003E\u003C/ol\u003E\u003Ch3 id=\u0022forwarding_your_support_address\u0022\u003EForwarding your support address\u003C/h3\u003E\u003Cp\u003EForward a copy of every email sent to your support address to the messenger\u0027s address. How you do this depends on your mail provider:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EGoogle Workspace or Gmail:\u003C/b\u003E in Gmail\u0027s settings, open \u003Cb\u003EForwarding and POP/IMAP\u003C/b\u003E, add a forwarding address, paste the messenger\u0027s address and confirm. Google sends a confirmation email to that address. It arrives in your inbox as a conversation, with the link you click to confirm. For a Google group, you can add the messenger\u0027s address as a member instead.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EMicrosoft 365 or Outlook:\u003C/b\u003E in the Exchange admin center, open the mailbox\u0027s mail flow settings and set up forwarding, or add a mail flow rule that redirects a copy to the messenger\u0027s address.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EAny other provider:\u003C/b\u003E add a forwarding rule or alias that sends a copy of every email to the messenger\u0027s address.\u003C/li\u003E\u003C/ul\u003E\u003Ch3 id=\u0022using_your_own_address_for_replies\u0022\u003EUsing your own address for replies\u003C/h3\u003E\u003Cp\u003EWithout \u003Cb\u003EReplies come back to\u003C/b\u003E, each conversation\u0027s emails use a long reply address that Docent makes for that conversation. That works, but customers see an unfamiliar address.\u003C/p\u003E\u003Cp\u003EEnter your own support address (the one you forward to the messenger) and every email you send has it as the reply address, under your sender name. When a customer replies, the reply reaches the messenger through your forwarding and finds its conversation again from the email\u0027s headers, or from the ticket number in the subject.\u003C/p\u003E\u003Ccite class=\u0022important\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ETurning email off\u003C/span\u003E\u003Cp\u003EIf you switch off Receive email, new emails stop arriving and replies to email conversations can\u0027t be sent until you switch it back on. Existing email conversations stay in the inbox.\u003C/p\u003E\u003C/cite\u003E\u003Ch2 id=\u0022several_addresses\u0022\u003ESeveral addresses\u003C/h2\u003E\u003Cp\u003EIf you have more than one shared address, such as support@, sales@ and hello@, list each one under \u003Cb\u003EYour addresses\u003C/b\u003E and click \u003Cb\u003EAdd an address\u003C/b\u003E. For each, enter a \u003Cb\u003EName\u003C/b\u003E and \u003Cb\u003EYour address\u003C/b\u003E, then click \u003Cb\u003ESave\u003C/b\u003E. Each address gets its own \u003Cb\u003EForward it to\u003C/b\u003E address; forward that address of yours to it.\u003C/p\u003E\u003Cp\u003EEach address can have its own settings:\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003ESetting\u003C/th\u003E\u003Cth\u003EWhat it does\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003ETeam\u003C/td\u003E\u003Ctd\u003ESends new conversations from this address straight to a team, such as Sales, instead of the usual routing. See \u003Ca href=\u0022/article/chat-notifications-and-teams\u0022\u003EChat Notifications and Teams\u003C/a\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EAI agent\u003C/td\u003E\u003Ctd\u003E\u003Cb\u003EAnswers\u003C/b\u003E or \u003Cb\u003ETeam only\u003C/b\u003E, so the AI can answer support@ while your sales team handles sales@ itself. \u003Cb\u003EAs set above\u003C/b\u003E follows the main switch.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ENew emails\u003C/td\u003E\u003Ctd\u003E\u003Cb\u003EBecome tickets\u003C/b\u003E or \u003Cb\u003EConversations only\u003C/b\u003E, when ticketing is on. The default follows your Ticketing settings.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003ESent as\u003C/td\u003E\u003Ctd\u003EThe sender name for this address\u0027s replies.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EEach conversation remembers which address it came in on. Replies use that address, the inbox shows it on the conversation (\u0022Email \u00B7 to sales@\u2026\u0022), and \u003Ca href=\u0022/article/chat-procedures\u0022\u003Eprocedures\u003C/a\u003E that start on new conversations can be limited to just that address.\u003C/p\u003E\u003Cp\u003EMail forwarded to the messenger\u0027s main address still works. If its original To or Cc line names one of your listed addresses, it\u0027s filed under that address.\u003C/p\u003E\u003Ch2 id=\u0022what_the_customer_sees\u0022\u003EWhat the customer sees\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EOne thread.\u003C/b\u003E Replies from the AI agent and your team arrive as replies in the customer\u0027s own email thread. When they reply, their message joins the same conversation. A new email (not a reply) starts a new conversation, with the email\u0027s subject.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EWho gets the reply:\u003C/b\u003E the customer, plus everyone they copied on their latest email. Your own support address never gets a copy.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ETicket numbers.\u003C/b\u003E If the conversation is a ticket, replies can carry the ticket number in the subject, for example \u003Ci\u003ERe: Refund request [#1042]\u003C/i\u003E. You choose this on the \u003Ca href=\u0022/article/setting-up-ticketing\u0022\u003ETicketing\u003C/a\u003E page.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EArticles and files.\u003C/b\u003E The AI agent\u0027s answers include the articles it used as links. Files your team attaches are sent with the email.\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022verified_and_unverified_senders\u0022\u003EVerified and unverified senders\u003C/h2\u003E\u003Cp\u003EAnyone can put any address in the From line of an email. So Docent checks whether the sender\u0027s domain vouched for the email (with the standard email signatures, DKIM or SPF). Each email is marked \u003Cb\u003EVerified\u003C/b\u003E or \u003Cb\u003EUnverified\u003C/b\u003E.\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EA \u003Cb\u003Everified\u003C/b\u003E email from an address you already know joins that customer\u0027s history. If the customer belongs to an \u003Ca href=\u0022/article/chat-accounts\u0022\u003Eaccount\u003C/a\u003E, the conversation is filed under that account.\u003C/li\u003E\u003Cli\u003EAn \u003Cb\u003Eunverified\u003C/b\u003E email still becomes a conversation, but it\u0027s kept apart from any existing customer with the same address, so a forged address can\u0027t see or reach a real customer\u0027s history.\u003C/li\u003E\u003Cli\u003EImages in an unverified email are hidden until a teammate shows them.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EAn email is never treated as a signed-in customer from your website, so it can\u0027t use actions that need a signed-in customer.\u003C/p\u003E\u003Ch2 id=\u0022what_your_team_sees\u0022\u003EWhat your team sees\u003C/h2\u003E\u003Cp\u003EAn email conversation in the inbox reads like an email, not a chat:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EThe subject is the title.\u003C/b\u003E Beneath it, a line such as \u003Ci\u003E\u2709 Email to sales@\u2026 \u00B7 3 messages\u003C/i\u003E.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EEach email is a card\u003C/b\u003E, shown the way it was sent, at its full length. Your team\u0027s replies have a blue edge on the left and show whether they were sent (or why sending failed).\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EMore detail:\u003C/b\u003E click the sender\u0027s name to see the email\u0027s headers: from, to, cc, date and the security check.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EShow as text\u003C/b\u003E shows the plain text instead of the original look, and \u003Cb\u003EOpen in new tab\u003C/b\u003E opens the email on its own.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EShow images\u003C/b\u003E appears on emails from unverified senders. Their images stay hidden until you click it, so a tracking image can\u0027t tell the sender you opened the email.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EEarlier emails fold\u003C/b\u003E to one line each; click one to open it. Three or more in a row collapse into \u003Cb\u003E{n} earlier messages\u003C/b\u003E. Quoted history at the bottom of an email folds behind \u003Cb\u003E\u00B7\u00B7\u00B7\u003C/b\u003E.\u003C/li\u003E\u003C/ul\u003E\u003Ch3 id=\u0022replying\u0022\u003EReplying\u003C/h3\u003E\u003Cp\u003EType in the reply box as usual. Above it you see who the reply is from and who it goes to, and the subject it will have (\u003Ci\u003ERe: \u2026\u003C/i\u003E).\u003C/p\u003E\u003Cp\u003ETo copy someone in on one reply, type their address in the \u003Cb\u003ETo\u003C/b\u003E line (or click \u003Cb\u003ECc\u003C/b\u003E and type it there) and press Enter. They get that reply only; later replies go to them again only if the customer replies to everyone. Internal notes are never emailed.\u003C/p\u003E\u003Ch2 id=\u0022how_email_differs_from_chat\u0022\u003EHow email differs from chat\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003ENo \u0022waiting\u0022 messages.\u003C/b\u003E When the AI hands an email to your team, the customer gets no \u0022passed to the team\u0022 or \u0022our team is offline\u0022 message, and no follow-up while they wait. They simply hear back by email.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ENo rating requests\u003C/b\u003E are sent by email.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EFollow-up questions are asked in words.\u003C/b\u003E Where a chat on your website shows a form (for a question rule or a procedure), an email asks the questions in the reply instead.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ENot in the messenger.\u003C/b\u003E Email conversations don\u0027t show in the customer\u0027s messenger on your website.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EIgnored mail:\u003C/b\u003E bounces, out-of-office and other automatic replies, mailing lists, emails Docent sent itself, an email received twice, and more than 20 emails an hour from one sender.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EAttachments:\u003C/b\u003E up to 5 files per email, 10 MB each.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EEverything else works as in chat: \u003Ca href=\u0022/article/configuring-the-chat-ai-agent\u0022\u003Ethe AI agent\u003C/a\u003E, rules, procedures, team alerts and \u003Ca href=\u0022/article/translating-chat-conversations\u0022\u003Etranslation\u003C/a\u003E.\u003C/p\u003E\u003Ch2 id=\u0022tickets_from_email\u0022\u003ETickets from email\u003C/h2\u003E\u003Cp\u003EWhen \u003Ca href=\u0022/article/setting-up-ticketing\u0022\u003Eticketing\u003C/a\u003E is on, each new email thread can become a ticket straight away (this is on by default, and each address can override it). The customer can get a \u0022we\u0027ve received your request\u0022 email with the ticket number. If the customer replies to a closed ticket, their email starts a follow-up ticket. See \u003Ca href=\u0022/article/working-with-tickets\u0022\u003EWorking with Tickets\u003C/a\u003E for how your team handles them.\u003C/p\u003E\u003Ch2 id=\u0022spam_and_delete\u0022\u003ESpam and Delete\u003C/h2\u003E\u003Cp\u003EEmail conversations have two extra actions:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003ESpam\u003C/b\u003E (in the conversation\u0027s header) blocks the sender and deletes the conversation for good. Their future emails are dropped before they reach the inbox: no conversation, no alert, no reply.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EDelete this email\u2026\u003C/b\u003E (under \u003Cb\u003E\u22EF\u003C/b\u003E) deletes the conversation for good, with its messages, attachments and ticket, without blocking the sender. It can\u0027t be undone.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EBefore blocking, Spam tells you what it will block:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EUsually the sender\u0027s \u003Cb\u003Ewhole domain\u003C/b\u003E, such as \u003Ci\u003Espammy-seo.biz\u003C/i\u003E, including its subdomains.\u003C/li\u003E\u003Cli\u003EOnly their \u003Cb\u003Eexact address\u003C/b\u003E when they write from a free email provider such as gmail.com or outlook.com, or from one of your own domains, because real customers use those too.\u003C/li\u003E\u003Cli\u003EOnly the exact address when the sender wasn\u0027t verified (the From address could be forged), or when you can\u0027t change messenger settings. Ask an owner or admin to block a whole domain.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EIt also warns you if any of your verified customers have an address on that domain.\u003C/p\u003E\u003Ch3 id=\u0022managing_blocked_senders\u0022\u003EManaging blocked senders\u003C/h3\u003E\u003Cp\u003EOpen your messenger\u0027s \u003Cb\u003ESettings\u003C/b\u003E and go to the \u003Cb\u003EBlocked IPs\u003C/b\u003E tab. Under \u003Cb\u003EBlocked email senders\u003C/b\u003E you see every block, the email it came from, who blocked it and how many emails it has stopped. You can remove a block, or type a domain or address and click \u003Cb\u003EBlock\u003C/b\u003E to add one yourself. A free provider\u0027s whole domain can\u0027t be blocked. Owners and admins can manage this list.\u003C/p\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ENot available yet\u003C/span\u003E\u003Cp\u003EForwarding an email to someone else, Bcc, and viewing the original raw email aren\u0027t available yet.\u003C/p\u003E\u003C/cite\u003E","publish_status":0,"post_type":"Article","author":{},"featured_image_updating":false,"meta_description":"Learn how to integrate your support email into the messenger, enabling AI and team replies within email threads without customers leaving their inbox.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":1,"date_published":"2026-11-15T17:38:31.24","date_updated":"2026-11-15T17:38:31.91","date_created":"2026-11-15T14:15:46.97"}}}