Email Inbox

Turn emails to your own support addresses into Discord tickets, answer them from Discord, and set up the domain, addresses, Atlas and limits

The email inbox turns emails to your own addresses, such as help@support.yourdomain.com, into tickets in Discord. Every email to one of your addresses opens a ticket. Staff answer in the ticket, and the customer gets the answer by email, from your domain, as a reply to their email. It is for servers whose customers also write by email, so your team works email and Discord tickets in one place.

The email inbox needs a Pro or Enterprise plan on the bot owner's account. Only the bot owner can open its settings page, connect a domain and manage addresses. You also need a domain you own and access to its DNS settings at the company that runs it. Free email providers such as Gmail cannot be connected. View pricing

Go to Email inbox

What you need

  • Pro or Enterprise on the bot owner's account. See Limits for what each plan includes.
  • A domain you own, normally a subdomain such as support.yourdomain.com. One server connects one domain, and a domain can belong to only one server.
  • Access to the domain's DNS, to add five records. They are shown in the dashboard, ready to copy.

Why a subdomain

Connecting a domain routes all email for that domain to TicketCord. If you connected yourdomain.com itself, the email your team already receives there would stop arriving where it does now. A subdomain such as support.yourdomain.com receives nothing today, so your existing email keeps working.

TicketCord refuses a domain that already receives email somewhere else. The dashboard then says This domain already receives email and offers a subdomain to use instead.

These domains cannot be connected either:

  • A domain ending on its own, such as co.uk.
  • A free email provider, such as gmail.com or outlook.com.
  • A TicketCord domain.
  • A domain that is connected to another server, or is a parent or subdomain of one. For example, if yourdomain.com belongs to one server, support.yourdomain.com cannot be connected to another.

Connect your domain

Open the Email inbox page

Go to Email inbox in your server's settings. Only the bot owner sees this page.

Enter your domain

Under Your domain, enter the domain, for example support.yourdomain.com, and click Connect domain. The page shows Domain connected. Add the DNS records next. The page is now one card, Your domain, with the status Waiting for DNS records and the five records.

Add the five DNS records

Add the records right away, at the company that runs your domain's DNS. The card offers two ways, and remembers the one you used:

  • Cloudflare: if your domain's DNS is at Cloudflare, click Open Cloudflare and choose your domain, then select Add record for each record on the card. The card names every field the way Cloudflare's form does: Type, Name, then Content (TXT), Target (CNAME) or Mail server (MX), and Priority 10 for the MX record. Leave TTL on Auto, and keep Proxy status on DNS only for the three CNAME records: a proxied one is never confirmed. A record that is already in your DNS shows as one line with its status; only the records still missing list their fields. To add them all at once instead, open Add them all at once with a file, click Download file, select Import and Export in Cloudflare, and choose the file under Import DNS records. The file holds only the records that are still missing.
  • Other provider: the card lists the five records with every field: Type, Name, Value, Priority 10 for the MX record, and TTL (your provider's default, or 1 hour). Copy the Name and the Value with the copy buttons. If your provider has a proxy or CDN switch for CNAME records, turn it off. If your provider adds your domain to the end of a name by itself, enter the name without that ending.

Wait for verification

Leave the page open or come back later. The card counts the records it has found (Found: 2 of 5) and shows a status for each one. How long it takes on the card explains the timing. The domain becomes Connected once all five are confirmed. Click Check again to look straight away. Once the domain is Connected, the page says One step left: add an address and shows the Addresses card.

Add an address

Click Add address and create your first address, such as help or support. Emails only arrive at addresses you create: mail to any other address at your domain is refused. See Addresses. With the first address in place, the page gets five tabs: Overview, Addresses, Domain, Blocked senders and Settings. It opens on Overview. On a narrower screen the tabs are a menu at the top of the page.

The five DNS records

RecordTypeWhat it does
First oneTXTProves that you control the domain right now. Its value is a code made for this connection only, so nobody else can connect your domain, even if old records from an earlier setup are still in its DNS. It is only needed until the domain is Connected; you can remove it afterwards
Next threeCNAMEProve that you own the domain, and let TicketCord sign the emails it sends for you as your domain, so mail providers trust them and do not mark your replies as spam
Last oneMXRoutes email sent to your domain to TicketCord, so it can open tickets

Copy each record exactly as the dashboard shows it. The values are unique to your domain, and the TXT code changes every time a domain is connected, so records from another domain, an earlier connection or another guide do not work.

What the statuses mean

While the domain is waiting for its DNS records, each record shows one status:

StatusMeaning
Not found yetWe cannot see the record in your DNS yet
Found, confirmingThe record is in your DNS and is being verified
ConfirmedThe record has been verified

The domain is Connected when all five records are confirmed.

Once the domain is Connected, the records move to the Domain tab: click Show DNS records on the Your domain card to see them again, with their copy buttons and without the statuses. The card also says when the domain was last checked (Last checked). The statuses and Check again come back there if sending is paused because a record is missing (see When sending is paused).

How long it takes

  • When you add the records in the first few minutes after clicking Connect domain, verification usually finishes within a couple of minutes.
  • A record added later can take an hour or more to be noticed. Check again does not speed this up, but it does no harm.
  • TicketCord keeps checking by itself, even when the page is closed: every minute for the first 10 minutes, every 5 minutes for the first hour, then every 30 minutes. After a check, Check again rests for 30 seconds.
  • A domain whose records are not confirmed within 3 days is released. The page then says Its DNS records were not confirmed within 3 days, so the domain was released. Check the records at your DNS provider, then connect the domain again.

Domain statuses

The domain's status is shown on the Your domain card, which is the whole page until the domain is Connected and on the Domain tab afterwards, and next to the domain at the top of the Overview tab. Domain details on the Overview tab opens the Domain tab.

StatusMeaning
Waiting for DNS recordsThe domain is connected, and its records are not all confirmed yet
ConnectedEmails to your addresses open tickets, and replies are sent from your domain
Sending pausedNew emails still open tickets, but nothing is sent. See When sending is paused
Setup did not finishDisconnect the domain, then connect it again
DisconnectingThe domain is being removed. The page updates when it is done
OffThe owner's plan no longer includes the email inbox. See If your plan changes

TicketCord checks the records of every connected domain again once a day. When one of them is gone, sending pauses until the records are back (see When sending is paused).

Addresses

Each address opens tickets with its own settings. On the Addresses tab of the Email inbox page, click Add address to create one, or open an address's Actions menu to Edit or Remove it. The number of addresses you can create depends on the plan (see Limits), and the card shows how many you have, such as 2 of 3. In the list, each address shows its sender name and its Atlas setting (such as Atlas: Auto reply), and Off when Receiving email is off.

SettingValuesDefaultWhat it does
AddressLetters, digits, dots, plus, hyphen or underscore, starting and ending with a letter or digit, up to 64 charactersThe part before the @. The domain is your connected domain. It cannot be changed after the address is created
Sender nameRequired, up to 64 charactersShown as the sender of every email, such as your brand. Staff names are never shown to the customer
SignaturePlain text, up to 1,000 charactersEmptyAdded to the end of every email sent from this address, after a blank line
Ticket categoryOne of your ticket categoriesThe server's defaultWhere tickets from this address open
Staff rolesUp to 25 rolesThe server's staff rolesWho handles these tickets. Leave it empty to use the server's staff roles
Atlas, the AI assistantAuto reply, Draft only, OffAuto replyHow Atlas answers emails to this address. See Atlas by email
Confirm new emailsOn, OffOnReplies with a short "we received your email" when an email opens a ticket, unless Atlas emails its answer instead. See Automatic emails
Email when closedOn, OffOnSends the customer an email when the ticket is closed, with the close reason, and a rating link when ratings are on. See Automatic emails
Receiving emailOn, OffOnWhen off, emails to this address are refused

Removing an address refuses emails to it from then on. Tickets it already opened stay.

Email to an address you did not create on your domain is refused: the sender's email provider tells them the address does not exist. There is no catch-all address.

How an email ticket works

A new email opens a ticket

  1. A customer emails one of your addresses.
  2. A ticket opens in the address's category, visible to its staff roles. The customer never sees the channel, so instead of your welcome message the ticket opens with the Email ticket card for staff: the email's subject as its title, then From: (the sender's name and address, or the address alone when their email carried no name), To: (which of your addresses they wrote to), CC: (anyone copied), Other open tickets from this sender: (as links) and Follows up on: (the earlier ticket, when this one follows a closed one). Lines with nothing to show are left out. Under it are Block sender (see Block a sender), a Merge into another ticket menu when the sender has other open tickets (see Merge tickets), and the ticket's usual buttons, such as Claim and Close. It pings the staff roles your server pings on new tickets, and nobody else.
  3. The same card shows the email itself: its text under the details, then a Reply button above the ticket's other buttons. A long email shows its first part on the card, with the note The email continues in the next message., and the rest follows in a second message under the customer's name, together with any attachments. Later emails from the customer are each posted under the customer's name with a mail avatar: the Subject, anyone in CC, the text, the attachments, and a Reply button.
  4. With Confirm new emails on, the customer gets a short "we received your email" email (see Automatic emails).

Email mark in channel names, under Email inbox → Settings → Email tickets, gives new email tickets a mail emoji in their channel name, so staff can spot them in the channel list. It is on by default and applies to new tickets only.

An email outside your business hours still opens a ticket, even when new tickets are blocked outside hours. The closed notice is not posted in it, because the customer never sees the channel.

The customer's email is cleaned up for Discord: the quoted earlier conversation and phone signatures such as "Sent from my iPhone" are left out. The email that opens a ticket is split over the opening card and a second message when it is long. A later email is posted as one message. An email too long for that is shortened, with the note The email was shortened to fit Discord.

Attachments

Files the customer attaches are posted with their email, up to 10 files and 10 MB in total per email. Program files (such as .exe, .bat, .msi, .apk or .dmg) and files over the limit are left out, and the card says Files left out: with how many. Replies by email are text only.

Answering by email

Press Reply

Any staff member with access to the ticket presses Reply on the customer's email. A box titled Reply by email opens. Write the answer under Your reply, up to 3,000 characters.

Check the draft

The bot posts a Draft reply card in the ticket: "Nothing is emailed until someone presses Send." With the server's Atlas switch on and AI tokens left, the draft is your text cleaned up for grammar and email layout only, in the same language and with the same meaning (Cleaned up by AI: grammar and layout only.). Otherwise it is exactly what you typed.

Choose and send

Use the buttons on the card:

  • Send emails the draft to the customer.
  • Edit opens the box again with the draft in it.
  • Use my text switches to exactly what you typed (Use cleaned text switches back).
  • Translate appears when the draft is in another language than the customer writes in. See Translation.
  • Discard throws the draft away.

After Send, the card becomes Sent by email with Sent by and the staff member's name. The customer sees only your Sender name, never the staff member's. A draft can be pressed by anyone on the team, not only the person who wrote it, and it expires after 24 hours.

The email goes only to the person who wrote to you. People in CC are shown on the card but are never emailed. The customer's reply lands in the same ticket.

A sent email counts as the staff reply for first response, response targets and staff stats. Typing in the channel does not.

Staff chat stays private

Staff can talk freely in an email ticket's channel. Nothing typed in the channel is emailed, saved with the ticket or shown in the transcript. Only the Reply flow sends email: a canned response sent with /reply is posted in the channel like any other staff message, so it is not emailed and does not count as a reply. The transcript of an email ticket holds the customer's emails, the emails sent to them and the bot's messages.

Translation

When Translate tickets is on (AI assistant → Atlas → Translate tickets, Enterprise) and the draft is in another language than the customer writes in, the draft card offers Translate. Pressing it shows both versions, Original and Translation, and selects the translation. Use original and Use translation choose which one Send emails. Nothing is translated until someone presses Translate. The customer's emails are not translated for staff in the ticket. See Translation.

More emails from the same person

  • A reply to an email you sent joins its ticket, when it comes from the same person.
  • A new email that is not a reply opens a new ticket. Once the same person has 3 open tickets on one address, their new emails join the newest of them.
  • A reply to a closed ticket reopens it within the number of days set in Reopen on reply, under Email inbox → Settings → Email tickets: 0 to 30 days, 7 by default, and 0 never reopens. The ticket shows Reopened by: a reply from the customer. A later reply, or one to a ticket that can no longer be reopened, opens a new ticket that links the earlier one (Follows up on: on its card, with the ticket number alone when the earlier ticket's channel was deleted).
  • Because the earlier ticket's channel is usually gone by then, the new ticket also gets a card for staff about the earlier ticket. When Atlas and its Ticket summary switch are on (AI assistant → Atlas → What Atlas does), Atlas writes the summary, as /summary does: what happened, what was already tried and the next step. It uses your AI tokens like /summary, and is skipped for tickets Atlas is kept away from. Otherwise, or when the summary cannot be written, the card quotes the last email the customer sent and the last email sent to them in the earlier ticket, with its close reason. There is no card when the reply was sent to a different one of your addresses than the earlier ticket (its staff roles may differ), when the earlier ticket's messages were already deleted under your ticket retention, or when it holds no email.

Closing

Staff close an email ticket as any other ticket. With Email when closed on, the customer gets the closing email (see Automatic emails). The customer gets no Discord messages, so close DMs, rating DMs and member pings are skipped for email tickets.

Automatic emails

Each address sends two automatic emails, both on by default and both plain text. They count against your email limits. Both greet the customer by the name their email carried ("Hi Jane Doe,"); when it carried none, they start with "Hello,".

  • Confirmation (Confirm new emails): sent at most once, when an email opens a ticket. It thanks the customer, gives the ticket number and says they can add anything by replying. When Atlas is set to answer the email (the address is on Auto reply and Atlas answers tickets on your server), the confirmation waits for Atlas: if Atlas emails its answer first, the confirmation is skipped; if Atlas has no answer, leaves its answer as a draft for staff, or its email cannot be sent, the confirmation is sent then. If Atlas has not emailed an answer after a few minutes, the confirmation is sent then, and an answer Atlas emails later still reaches the customer, so in that case, or when the two go out at the same moment, they get both. With Draft only or Off, it is sent straight away. A reply that joins or reopens a ticket gets no confirmation.
  • Closing email (Email when closed): sent each time the ticket is closed, with the close reason when one was given. When ratings are on (Closing tickets → Ratings), it adds a private rating link. The link opens a page where the customer rates the help from 1 to 5, with an optional comment of up to 1,000 characters. It needs no sign-in, works for 30 days and records one rating.

No automatic email is sent to a sender TicketCord could not verify, or to a no-reply address. Their email still opens a ticket, and staff see why on the email card:

  • This sender could not be verified, so no automatic emails are sent to them. Replies you send are still delivered. The email did not prove that it really came from the address it names, so that address may be forged.
  • This came from a no-reply address, so no automatic emails are sent to it.

A later verified email from them on the same ticket turns automatic emails on again. An unverified email never joins or reopens a ticket that a verified sender opened: it opens its own ticket. Replies staff send with Send always go out.

Automatic emails also stop for the whole server for up to 24 hours when 3 of them could not be delivered because the address does not exist, or when one of them was marked as spam, within the last 24 hours. Staff replies are not affected, and Atlas answers become draft cards meanwhile.

The closing email can also carry a private link to the conversation, so the customer can read it again online. The bot owner turns it on with Transcript link in the closing email under Email inbox → Settings → Email tickets: "The customer gets a private link to read the emails of their ticket for 30 days." It is off by default, and it is separate from the settings for transcripts in Discord and the dashboard.

  • The link opens a read-only page with the ticket's number, subject and the customer's own emails and the emails sent to them, oldest first. Staff chat in the channel, notes, bot messages and staff names are never shown. Attachments appear by file name only.
  • It needs no sign-in, works for 30 days and can be opened as often as the customer likes.
  • It stops working when Transcript link in the closing email is turned off, and once the ticket's saved messages are removed after the time set in Keep closed tickets for.
  • When ratings are on, the closing email carries both links.
  • If you wrote your own Ticket closed email on the Messages page, add {transcriptLink} (and {transcriptText} for the built-in sentence before it) to your version, or the link is not sent. See the message reference.

Change their text on the Messages page: Email received confirmation and Ticket closed email. The card staff see when an email opens a ticket is Email ticket card there. See the message reference.

Block a sender

Press Block sender on the Email ticket card to block the customer's address for the server. A private message asks you to confirm: "Block this ticket's sender? Their emails will be dropped and will not open tickets. The server owner can unblock them on the dashboard." Press Block. Any staff member with access to the ticket can do it. The sender is not told.

The bot owner manages the list under Email inbox → Blocked senders:

  • Enter an address (jane@example.com) or a whole domain (example.com) under Address or domain and click Block. A domain blocks every address on that domain; its subdomains are not included.
  • Each entry shows Address or Domain. Use its Unblock button to remove it.
  • A server can block up to 500 senders. At the limit, unblock one to add another.

Emails from a blocked sender are dropped: they never open a ticket, are never answered, and are counted as Blocked sender under Emails not turned into tickets on the Overview tab (see Email activity). Tickets they opened before stay.

Merge tickets

When the same customer writes more than once and ends up with several open tickets, staff can merge one into another, so the conversation continues in one place.

  1. In the ticket you want to close, open the Merge into another ticket menu on the Email ticket card. It lists the sender's other tickets that were open when this ticket opened.
  2. Pick the ticket to keep. A private message asks you to confirm: "Merge this ticket into the one you picked? Its emails are copied there, replies to either thread go there, and this ticket closes. Nothing is emailed to the customer."
  3. Press Merge.

What happens:

  • Every email of the merged ticket, received and sent, is posted again in the kept ticket, oldest first. A received email keeps its Reply button, which now answers in the kept ticket, and its files are named with a link to the original. A note says Merged in: with the merged ticket's number.
  • Replies the customer sends to either email thread land in the kept ticket from then on.
  • The merged ticket closes with the reason "Merged into ticket" and the kept ticket's number. The customer gets nothing: no email about the merge, no closing email and no rating link.
  • Both tickets must be open email tickets from the same sender in your server, and you need staff access to both. If merging stops part way, press Merge again to finish it.

Atlas by email

Atlas answers emails the same way it answers in tickets: from your help content, with the Atlas switch and Answer questions in tickets on (AI assistant → Atlas → Answer questions in tickets), using the bot owner's AI tokens. It answers in the customer's language, written as an email: a greeting, full sentences and a sign-off. When the address has a Signature, the signature ends the email and Atlas leaves its own sign-off out. Links are written out as plain web addresses. Each address chooses how:

ModeWhat Atlas does
Auto reply (default)Emails the answer to the customer when it knows it. The answer shows in the ticket as Sent by email, Sent by Atlas
Draft onlyPosts its answer as a Draft reply by Atlas card. Staff review it and press Send, Edit or Discard, as for their own drafts
OffDoes not answer emails to this address

In Auto reply, an answer that cannot be emailed (the limit is reached, sending is paused, or the customer's address cannot be emailed) becomes a draft card with the reason, so staff can send it later. The same happens for a sender who could not be verified or a no-reply address (see Automatic emails), with Atlas wrote this answer, but automatic emails are off for this sender, so it was not emailed. Review it and press Send.

Atlas emails at most 8 answers by itself on one ticket in 24 hours. After that its answers become draft cards with Atlas wrote this answer, but it has already emailed this customer several times today, so it was not emailed. Review it and press Send. This keeps Atlas and a customer's auto-responder from answering each other. An answer too long to send by email is not sent, and staff see Atlas had an answer to this email, but it was too long to send by email. Please reply to the customer yourself.

Atlas does not ask for details when an email only says hello, and it does not offer to close an email ticket.

Limits

Only emails sent from your domain count: staff replies, Atlas answers, confirmations and closing emails. Incoming email is free. Limits are per server.

ProEnterpriseEnterprise trial
Emails sent per month3,0005,0005,000
Emails sent per day100No daily limit50
Addresses31010

A paid Enterprise plan has no daily limit: a server can send its whole monthly limit on any days. The Enterprise trial keeps its limit of 50 a day. Free and Basic do not include the email inbox. Months and days are counted in UTC. The Sending limit card under Email inbox → Overview shows This month and Today against the limit.

Part of each limit is kept for staff. Automatic emails (confirmations, Atlas answers and closing emails) use at most half of the daily limit (on plans that have one) and 80% of the monthly limit. Once they reach that share, no more automatic emails are sent until the limit resets, Atlas answers become draft cards, and staff can still send the rest. This way a wave of new senders cannot use up the emails your staff need to reply.

When a limit is reached:

  • Incoming email still opens tickets.
  • Nothing more is sent until the limit resets (the next UTC day for the daily limit, the next month for the monthly one). Send says The email limit for this server is reached, so the email was not sent., and the draft stays. It can be sent once the limit resets while it is still there: drafts expire 24 hours after they were written. After that, press Reply on the customer's email and write the reply again.
  • Atlas answers in Auto reply become draft cards with Atlas wrote this answer, but the email limit is reached, so it was not emailed.

Other limits:

  • Emails larger than 25 MB are not accepted.
  • A sender who writes very often in a short time is limited, and their extra emails are dropped.

Email activity

The Overview tab of the Email inbox page shows what came in and went out. It has four parts.

This month. Six figures under the month's name, such as November 2026 (this month). Under each one is last month's figure (for example 12 last month). Months follow UTC.

FigureMeaning
Emails receivedEmails that reached one of your addresses and opened or joined a ticket
Emails sentEmails sent from your domain: staff replies, Atlas answers, confirmations and closing emails
DeliveredSent emails the customer's email provider accepted
BouncedSent emails that could not be delivered
Marked as spamSent emails a customer reported as spam
Delivery rateThe share of sent emails that were delivered (No emails sent when nothing was sent)

Activity. A chart of the emails Received and Sent on each of the last 30 days, with the totals above it. Point at a day to see its numbers, and how many of that day's sent emails were Delivered, Bounced or Marked as spam when there were any. Days follow UTC.

Sending limit. The emails sent This month and Today against your limits. See Limits.

Emails not turned into tickets. A table of the incoming emails that were dropped, by Reason, for This month and Last month. Months follow UTC. When nothing was dropped it says No emails were dropped this month or last month.

ReasonMeaning
SpamIncoming emails that looked like spam
VirusIncoming emails that carried a virus
Failed sender checkIncoming emails that claimed to come from an address they were not sent from
Blocked senderIncoming emails from a blocked sender
Automatic replyOut-of-office replies, delivery reports, mailing lists and other automatic mail
Over a limitEmails from a sender who wrote very often in a short time, and emails past what one server can receive in a month
Other reasonsEverything else: for example an email too large or unreadable, or one that arrived while the email inbox was not available for your server. Shown only when there are some

Dropped emails never open tickets and are never answered.

Sending rules

The email inbox is for answering people who wrote to you. You are responsible for every email sent from your domain through TicketCord: staff replies, Atlas answers, confirmations and closing emails.

  • Do not send email the recipient did not ask for: no newsletters, marketing, bulk mail or bought address lists.
  • Only connect a domain you own or are allowed to send from.
  • Keep bounces and spam reports low. They are counted for every server, and too many pause sending automatically (see When sending is paused).

TicketCord has to act when emails from a server are reported as spam. Depending on what happened, it can pause sending, switch the email inbox off for that server, or suspend or close the account that sent the spam, as the Terms of service allow for any spam sent through TicketCord. A paid plan does not prevent this.

When sending is paused

A paused domain shows Sending is paused with the reason, above the tabs of the Email inbox page. New emails still open tickets while sending is paused, and staff see Sending email is paused for this server. The server owner can check the dashboard. when they press Send.

Reason on the pageWhat happenedWhat to do
A DNS record of this domain is missing.One of the CNAME records or the MX record was removed or changedClick Show DNS records in the notice, or open the Domain tab, and add the record back as it is shown there. Sending starts again by itself once the records are back and checked. Click Check again on the Domain tab to check now
Too many emails bounced or were marked as spam.A customer marked an email that staff sent as spam, or at least 3 emails that staff sent in the last 30 days could not be delivered because the address does not exist and they are more than 4% of the emails staff sent. A full mailbox or another temporary failure does not count, and automatic emails never pause sending (see Automatic emails)TicketCord reviews it and can lift the pause. Contact support
TicketCord paused sending for this server.TicketCord paused itContact support to lift it
Our email delivery service paused sending for this domain.The service that delivers your emails paused this domainTicketCord support can ask for the pause to be lifted. Contact support

A customer who marked an email as spam, or whose address bounced, cannot be emailed again from your server. Staff see The customer's address bounced or reported spam before, so it cannot be emailed. In the ticket, staff also see when an email bounced, was marked as spam or is delayed.

What is filtered

Incoming email is checked before it opens a ticket. These emails are dropped without a reply to the sender:

  • Spam and emails with a virus.
  • Forged senders: emails that fail the checks proving they came from the address they name. An email that neither passes nor fails those checks still opens a ticket, but gets no automatic email (see Automatic emails).
  • Automatic emails: out-of-office replies, delivery reports, mailing lists and other bulk mail. This also stops two auto-responders from emailing each other forever.

Emails from a blocked sender are dropped too.

Email to an address you did not create, or to an address with Receiving email off, is refused during delivery.

Disconnect a domain

Click Disconnect domain at the bottom of the Your domain card and confirm with Disconnect. The card is on the Domain tab, and it is the whole page while the domain is still waiting for its DNS records or its setup did not finish. Mail to the addresses on the domain stops arriving, and nothing more is sent from it. Tickets already opened stay. Remove the DNS records afterwards. To connect the domain again later, add the records the page shows then: the TXT record has a new code each time.

Deleting a bot also disconnects its domain on every server it was set up in.

If your plan changes

When the bot owner's plan no longer includes the email inbox, the page says Your plan no longer includes the email inbox. Emails to your addresses are no longer received or sent. The domain and addresses are kept, and you can still remove the addresses or disconnect the domain. The Settings tab and the Sending limit card are hidden, and senders can be unblocked but not blocked. On a plan with fewer addresses, you cannot add one until you are under the new limit.

Troubleshooting

ProblemCauseFix
A CNAME record stays Not found yetThe record is set to go through your DNS provider's proxySet the three CNAME records to DNS only, without the proxy
A record stays Not found yetThe name was entered twice over. Many DNS providers add your domain to the name for you, so pasting the full name gives …yourdomain.com.yourdomain.comEnter the name without your main domain at the end, or check how your provider expects names, then click Check again
A record stays Not found yetThe record was added to another domain, or a value was not copied in fullCompare the name and value with the dashboard, character for character
This domain already receives emailThe domain has an MX record pointing to another mail serviceConnect a subdomain instead: the page offers one. Do not delete your existing MX record unless you mean to stop receiving that email elsewhere
The domain is Connected but some emails never arriveThe domain also has another MX record, so some email goes thereKeep only the MX record the dashboard shows on this domain (Domain tab, Show DNS records)
Every record is Found in DNS but not ConfirmedThe records were added a while after connectingWait: a record added later can take an hour or more to be noticed
Its DNS records were not confirmed within 3 days, so the domain was released.The records were missing or wrong for 3 daysCheck the records, then connect the domain again
This domain, or a parent or subdomain of it, is connected to another server.Another server uses the domain or one that overlaps itDisconnect it there first, or use another subdomain
A customer says their email bouncedThe address does not exist on your domain, or its Receiving email is offCreate the address, or turn Receiving email on
A customer's email never became a ticketIt was filtered as spam, forged or automatic, or the sender wrote very often in a short timeAsk them to write again from their own mailbox
Send says The email limit for this server is reached, so the email was not sent. (TC016)The daily or monthly limit is usedWait for the limit to reset, or move to a plan with a higher limit. Send the draft then if it is still there (drafts expire after 24 hours); otherwise press Reply and write it again
Send says Sending email is paused for this server. (TC018)Sending is pausedThe owner checks the reason on the Email inbox page
This draft was sent, discarded or has expired. (TC015)Someone else used the draft, or it is older than 24 hoursPress Reply on the customer's email again
Write a reply first. Emails can be up to 3,000 characters. (TC012)The reply was empty or too longWrite a shorter reply
It could not be confirmed whether the email was sent. (TC000)TicketCord could not tell whether the email went out, so the customer may already have itCheck with the customer, or wait for their reply, before you press Send again. The draft is kept
The email was sent, but it could not be added to the ticket's history. Do not send it again. (TC000)The customer got the email; only the ticket's record of it is missingDo not send it again
Go to Email inbox

Common questions

Can I use my Gmail or Outlook address?

No. The email inbox works with a domain you own, such as support.yourdomain.com, because replies are sent as your domain. Free email providers such as Gmail and Outlook cannot be connected. If you already receive email on your main domain, connect a subdomain so that email keeps working.

Can the customer see what my staff write in the ticket channel?

No. The customer only gets what staff send with Reply and Send, and the automatic emails (confirmation and closing email). Staff can talk freely in the channel: it is never emailed and not included in the transcript.

Why did my domain not get verified?

The five DNS records must be added exactly as the dashboard shows them. The most common mistakes are a record going through your DNS provider's proxy instead of DNS only, a name that ends with your domain twice, and an existing MX record. Records added right after connecting usually verify within a couple of minutes; records added later can take an hour or more. A domain not verified within 3 days is released and can be connected again.

Does incoming email count against my limit?

No. Only emails sent from your domain count: staff replies, Atlas answers, confirmations and closing emails. Pro sends up to 3,000 emails a month and 100 a day per server; Enterprise sends 5,000 a month with no daily limit; the Enterprise trial sends 5,000 a month and 50 a day.

What happens when we reach the email limit?

Incoming email still opens tickets, but nothing more is sent until the limit resets. Staff see that the email was not sent. Their draft stays for 24 hours after it was written and can be sent once the limit resets; after that, they press Reply and write it again. Atlas answers become drafts for staff instead of being emailed.

Are people in CC emailed?

No. Replies go only to the person who wrote to you. People in CC are shown to staff on the email card.

Can Atlas answer emails without staff?

Yes, with the address's Atlas, the AI assistant setting on Auto reply (the default). Atlas emails its answer when it knows it. Choose Draft only to have staff review every answer before it is sent, or Off to keep Atlas out of that address.

What happens if a customer replies after the ticket is closed?

A reply within 7 days of the close reopens the ticket. After that, the reply opens a new ticket that links the earlier one. Change the number of days with Reopen on reply on the Email tickets card, on the Settings tab of the Email inbox page: 0 to 30 days, and 0 never reopens.

Last updated on

On this page