1. Docs
  2. Guides

Email notifications & replies

Conversations don't end when a visitor closes the tab. TalkingDot emails visitors the replies they missed, emails teammates about messages nobody has answered, and can turn emailed replies back into chat messages.

Reply notifications for visitors

When a teammate replies and the visitor isn't there to see it, TalkingDot sends them an email after a short delay. The delay is set by the platform and is 3 minutes by default.

The email is sent only when all of these are true:

  • The visitor has left an email address, through the email card, the pre-chat form, a chatbot step, a transcript request or your site's JavaScript API.
  • They haven't read the reply in the messenger and haven't been on your site in the last minute and a half. If they're still browsing, they'll see the reply in the messenger instead.
  • They haven't unsubscribed or been blocked, and your workspace hasn't turned off visitor email notifications. These are on by default.

The email shows the unread replies (up to 20) with the teammate's name. The subject reads “New message from first name” in the visitor's language. It comes from your team name and includes a Reply button. The button opens your hosted chat page with the conversation already loaded, so the visitor can continue without finding your website again. The link works for 30 days.

Tip: Several quick replies in a row are grouped into one email. Messages the visitor reads in the meantime are left out.

Email notifications for teammates

If a visitor's message is still unanswered a couple of minutes later (2 by default, set by the platform), TalkingDot emails:

  • the assigned teammate, or, if nobody is assigned,
  • the members of the conversation's team, or, if it has no team,
  • every teammate in the workspace.

Teammates who had the dashboard open in the last two minutes, or who have already read the message, are skipped. The email quotes the new messages and links straight to the conversation. Each person chooses which emails they get (new conversations, assigned conversations and @mentions) in their notification settings. Being mentioned in an internal note sends an email after about a minute if you haven't seen it in the dashboard.

Transcripts

When transcripts are enabled in your messenger settings (the default), visitors can choose Email me a transcript in a conversation. They get a copy of the full conversation, with times shown in their own time zone. Internal notes are never included. Visitors can request up to 5 transcripts an hour. If the visitor had no email on file, the address they enter is saved to their contact.

Ticket emails

When tickets are on, customers also get an email when their ticket is opened, and when it is waiting for their reply, solved or closed. Each of the four can be turned off in Settings → Tickets.

  • Only to proven addresses. The “ticket opened” email goes only to an email address the customer has proven: a signed-in user of your site, an address they wrote to you from, or one they confirmed with a code. Status emails also go to other addresses once your team has replied in the conversation; before that, an address someone only typed into the messenger gets nothing.
  • Replies say which ticket. The reply notification for a ticket has the number and the title in the subject, like [#1042] Printer won’t connect, and the ticket’s status above the messages. Tickets that came by email keep their own subject (with “Re:”), so they stay in the same email thread.
  • No double emails. A status email waits for the reply-email delay plus half a minute. It is not sent when the status changed again in the meantime, when a reply email already showed the new status, or (for “closed”) when the customer was already told the ticket was solved.
  • No answer while waiting. When a ticket waiting on the customer is closed because they didn’t answer, the email says so, and a reply opens it again.
  • Tickets on WhatsApp, Telegram, Instagram and Facebook Messenger get no ticket emails and no automatic status messages.

Customers can answer ticket emails like any reply notification (see Replying by email), and every ticket email has an unsubscribe link.

Unsubscribe

Every reply notification ends with a Stop email notifications link. It opens a confirmation page, and once confirmed, that contact no longer gets reply notifications.

Replying by email

Replying by email needs an inbound reply domain that routes its mail to TalkingDot. It is set up on this service. When it's set up:

Visitors can reply to notification emails

Each reply notification uses a private reply-to address unique to that conversation, like this:

Text
reply+1234-9f2c4a1b7e3d@inbound.example.com

When the visitor hits Reply in their email app, their answer is added to the same conversation as a normal visitor message. Your team is notified as usual, and a closed conversation reopens. Behind the scenes:

  • Only the visitor can post. The sender must match the contact's email address, and the address includes a signature that can't be guessed. Mail from anyone else is ignored.
  • Quoted text is stripped. The quoted original and lines starting with > are removed, along with headers like “On … wrote:” (also in French and German), “Original Message” blocks and signatures after --. Only the new text is kept.
  • Attachments aren't imported. Only the text of the email is added. Ask visitors to send files through the messenger, using the Reply button in the email.
  • Auto-replies and bounces are ignored, so out-of-office messages don't clutter your inbox. Mail from blocked contacts is ignored too.

Replying to a teammate notification email doesn't post to the conversation. Teammates always answer from the inbox.

Email channel: receive emails as conversations

With inbound email set up, each workspace also has its own email address. Every email sent to it starts a new conversation in your inbox:

Text
inbox+YOUR_WORKSPACE_KEY@inbound.example.com

Your workspace key is the data-key value in your install snippet (Settings → Installation). The address is a convenient way to bring your existing support mailbox into the shared inbox: set your email provider to forward messages to it. TalkingDot recognises the address in the To, Cc or delivery headers.

  • The sender is matched to an existing contact by email address, or added as a new lead using the name from the email.
  • The email subject becomes the conversation subject. Your replies are emailed back immediately with the subject “Re: original subject” and the conversation's reply-to address, so the thread can go back and forth entirely by email.
  • To prevent floods, each sender can start up to 20 email conversations per hour in a workspace.

If inbound email isn't set up

Without an inbound domain, reply notifications and transcripts still go out, but emailed replies are not added to conversations. A visitor who replies to the email reaches your own address instead: your SMTP sending address if you set one up (below), otherwise the workspace owner's email — never the platform's. There is also no workspace email address. The Reply button in the email always reopens the conversation in the browser.

Sending new emails

Start an email to anyone, with a subject: New email at the top of the inbox, or Send email on a contact's page. The address becomes a contact (or matches an existing one), the conversation is on the email channel, and your message goes out at once with the subject exactly as you typed it — answers in the thread are “Re: …”. With inbound email set up, their answer comes back into the same conversation.

Contacts who unsubscribed can't be emailed. To keep mail servers happy there are limits: 50 new emails per teammate per hour and 300 per workspace per day.

Your own SMTP server

In Settings → Email you can send through your own mail provider — Google Workspace, Microsoft 365, Zoho, your host's mail server — so emails to your visitors and contacts come from your own address (for example support@yourcompany.com). It covers missed replies, new emails, transcripts and verification codes; notifications to your team still come from TalkingDot.

  1. Switch on Send through my own server and fill in the From name and address, the SMTP host, port (587 with STARTTLS is the most common, 465 for SSL), username and password. Gmail and Google Workspace need an app password.
  2. Save, then click Send a test email to me. The test goes only through your server, so you see its real answer.
  3. Make sure your domain's SPF and DKIM records allow your mail provider, or receivers may file the emails as spam.

The password is stored encrypted and never shown again. Only public mail servers on ports 25, 465, 587 or 2525 can be used. If your server fails while sending — a changed password, an outage — the email still reaches your visitor through TalkingDot's server (from our address with your team name), the error shows in Settings → Email, and the workspace owner is told, at most once a day.

Which plans include new emails, the email channel and your own SMTP server is set by the platform — see Pricing.

Last updated November 17, 2026 Something unclear? Tell us