Ask about anything in Docent Documentation

Type a question in your own words below. Answers are written from our published articles and cite the ones they came from.

Recently updated

    ↑↓ select · ↵ open · esc close
    Dashboard
    Edit Article Logout

    Chat Email Channel


    The email channel brings your support email into your messenger. Forward your support address (for example [email protected]) to the messenger, and every email becomes a conversation in the inbox. 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.

    Customers keep writing to the address they already know. They never need to visit your website or open the messenger.

    Setting up email

    Owners and admins set up email for each messenger.

    1. Open your messenger and click Integrations in its sidebar. Email is under Channels. Click Set up (or Manage once it's on).
    2. Under This messenger's address, click Copy. This is the address you forward your mail to. Keep it private: anything sent to it arrives in your inbox.
    3. Switch on Receive email.
    4. Choose whether The AI agent answers emails. With it off, every email waits for your team.
    5. Under Replies are sent as, enter the sender name customers see, such as "Acme Support". Leave it blank to use the name shown.
    6. Under Replies come back to, enter your own support address (optional, explained below).
    7. Click Save.
    8. Set up forwarding in your mail provider (below).
    9. Click Send me a test email. Reply to the test email you receive, and your reply should arrive in the inbox.

    Forwarding your support address

    Forward a copy of every email sent to your support address to the messenger's address. How you do this depends on your mail provider:

    • Google Workspace or Gmail: in Gmail's settings, open Forwarding and POP/IMAP, add a forwarding address, paste the messenger's 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's address as a member instead.
    • Microsoft 365 or Outlook: in the Exchange admin center, open the mailbox's mail flow settings and set up forwarding, or add a mail flow rule that redirects a copy to the messenger's address.
    • Any other provider: add a forwarding rule or alias that sends a copy of every email to the messenger's address.

    Using your own address for replies

    Without Replies come back to, each conversation's emails use a long reply address that Docent makes for that conversation. That works, but customers see an unfamiliar address.

    Enter 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's headers, or from the ticket number in the subject.

    Turning email off

    If you switch off Receive email, new emails stop arriving and replies to email conversations can't be sent until you switch it back on. Existing email conversations stay in the inbox.

    Several addresses

    If you have more than one shared address, such as support@, sales@ and hello@, list each one under Your addresses and click Add an address. For each, enter a Name and Your address, then click Save. Each address gets its own Forward it to address; forward that address of yours to it.

    Each address can have its own settings:

    SettingWhat it does
    TeamSends new conversations from this address straight to a team, such as Sales, instead of the usual routing. See Chat Notifications and Teams.
    AI agentAnswers or Team only, so the AI can answer support@ while your sales team handles sales@ itself. As set above follows the main switch.
    New emailsBecome tickets or Conversations only, when ticketing is on. The default follows your Ticketing settings.
    Sent asThe sender name for this address's replies.

    Each conversation remembers which address it came in on. Replies use that address, the inbox shows it on the conversation ("Email · to sales@…"), and procedures that start on new conversations can be limited to just that address.

    Mail forwarded to the messenger's main address still works. If its original To or Cc line names one of your listed addresses, it's filed under that address.

    What the customer sees

    • One thread. Replies from the AI agent and your team arrive as replies in the customer's 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's subject.
    • Who gets the reply: the customer, plus everyone they copied on their latest email. Your own support address never gets a copy.
    • Ticket numbers. If the conversation is a ticket, replies can carry the ticket number in the subject, for example Re: Refund request [#1042]. You choose this on the Ticketing page.
    • Articles and files. The AI agent's answers include the articles it used as links. Files your team attaches are sent with the email.

    Verified and unverified senders

    Anyone can put any address in the From line of an email. So Docent checks whether the sender's domain vouched for the email (with the standard email signatures, DKIM or SPF). Each email is marked Verified or Unverified.

    • A verified email from an address you already know joins that customer's history. If the customer belongs to an account, the conversation is filed under that account.
    • An unverified email still becomes a conversation, but it's kept apart from any existing customer with the same address, so a forged address can't see or reach a real customer's history.
    • Images in an unverified email are hidden until a teammate shows them.

    An email is never treated as a signed-in customer from your website, so it can't use actions that need a signed-in customer.

    What your team sees

    An email conversation in the inbox reads like an email, not a chat:

    • The subject is the title. Beneath it, a line such as ✉ Email to sales@… · 3 messages.
    • Each email is a card, shown the way it was sent, at its full length. Your team's replies have a blue edge on the left and show whether they were sent (or why sending failed).
    • More detail: click the sender's name to see the email's headers: from, to, cc, date and the security check.
    • Show as text shows the plain text instead of the original look, and Open in new tab opens the email on its own.
    • Show images appears on emails from unverified senders. Their images stay hidden until you click it, so a tracking image can't tell the sender you opened the email.
    • Earlier emails fold to one line each; click one to open it. Three or more in a row collapse into {n} earlier messages. Quoted history at the bottom of an email folds behind ···.

    Replying

    Type 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 (Re: …).

    To copy someone in on one reply, type their address in the To line (or click Cc 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.

    How email differs from chat

    • No "waiting" messages. When the AI hands an email to your team, the customer gets no "passed to the team" or "our team is offline" message, and no follow-up while they wait. They simply hear back by email.
    • No rating requests are sent by email.
    • Follow-up questions are asked in words. 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.
    • Not in the messenger. Email conversations don't show in the customer's messenger on your website.
    • Ignored mail: 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.
    • Attachments: up to 5 files per email, 10 MB each.

    Everything else works as in chat: the AI agent, rules, procedures, team alerts and translation.

    Tickets from email

    When ticketing 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 "we've received your request" email with the ticket number. If the customer replies to a closed ticket, their email starts a follow-up ticket. See Working with Tickets for how your team handles them.

    Spam and Delete

    Email conversations have two extra actions:

    • Spam (in the conversation's 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.
    • Delete this email… (under ⋯) deletes the conversation for good, with its messages, attachments and ticket, without blocking the sender. It can't be undone.

    Before blocking, Spam tells you what it will block:

    • Usually the sender's whole domain, such as spammy-seo.biz, including its subdomains.
    • Only their exact address 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.
    • Only the exact address when the sender wasn't verified (the From address could be forged), or when you can't change messenger settings. Ask an owner or admin to block a whole domain.

    It also warns you if any of your verified customers have an address on that domain.

    Managing blocked senders

    Open your messenger's Settings and go to the Blocked IPs tab. Under Blocked email senders 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 Block to add one yourself. A free provider's whole domain can't be blocked. Owners and admins can manage this list.

    Not available yet

    Forwarding an email to someone else, Bcc, and viewing the original raw email aren't available yet.


    How helpful was this article?

    👍 or 👎

    Related Articles

    Markdown Version