The Email channel
Atender’s Email channel connects your support operation to Atender-managed email infrastructure on your own domain. Customers reach you at an address like support@yourcompany.com, inbound messages are delivered into Atender either directly or through forwarding from your own mail provider (depending on each domain’s How customer replies reach Atender setting), and every reply flows into the same inbox as Web Chat, Voice, and every other channel.
Instead of setting up a domain, you can connect an existing mailbox with a single sign-in. Add inbox offers Gmail, Outlook and Email. See Connected Gmail and Outlook inboxes.
What you get
- Your own domains. You send and receive on addresses customers already trust. Atender does not own the domain — you do.
- Multiple domains per tenant. Run several support inboxes from one Atender tenant. Useful when you operate more than one brand from the same customer service team.
- Data residency. Each domain is pinned to either US or EU infrastructure at setup time. Choose the region that aligns with your compliance obligations.
- Inbound delivery. Atender receives new emails through its inbound delivery infrastructure, so messages land in the inbox in real time.
- Sender identity. You control the From name and From email on every outgoing message.
- Verified ownership. Atender will not send from a domain until DNS records prove you own it, which protects your sending reputation.
- Delivery activity. Admins can review domain-scoped email activity for verified-owned domains from Email → Deliverability → Activity.
How customer replies reach Atender
Each domain has a How customer replies reach Atender setting. It should match where your MX records point, and it sets how inbound mail gets to Atender:
- Your own mailbox forwards them. Your own email provider keeps the MX records for the domain and forwards incoming mail to an Atender inbox address. Choose this if your team needs to keep your existing mail setup in place.
- They come straight to Atender. The domain’s MX records point to Atender, so inbound mail is delivered straight into Atender with no forwarding hop.
Atender adds its own reply address, which threads each customer reply back into its conversation, only on domains set to They come straight to Atender whose MX records point to Atender. On other domains, replies are threaded by their email headers.
Connected Gmail and Outlook inboxes
Go to Settings → Email → Add inbox and choose Gmail, Outlook or Email. For Gmail and Outlook, sign in to connect a mailbox. These inboxes need no domain, DNS records, or forwarding.
- Reading mail. Atender reads new mail every minute. Older mail already in the mailbox is not imported.
- Replying. Replies go out From the mailbox address, including Outlook shared mailboxes.
Each connected inbox shows one of these statuses:
- Connected. The inbox is signed in and Atender is reading new mail.
- Needs sign-in. Atender can no longer access the mailbox, for example because the sign-in expired. Choose Sign in again to restore it.
- Disconnected. The inbox has been disconnected and Atender no longer reads or sends from it. Choose Connect again to reconnect it.
To stop Atender using a mailbox, choose Disconnect.
How it fits
Email is one of Atender’s text-first channels. A customer writes to your support address, the message reaches Atender (directly, via your forwarding rule, or through a connected Gmail or Outlook inbox), the conversation lands in Conversations like any other inbound message, and your team (or an Agent Stack) replies. On a domain, the reply goes back out through your verified domain, so the customer sees a reply from your address — not from Atender. On a connected inbox, the reply goes out from the mailbox address.
If you author branded transactional or campaign emails (CSAT surveys, automation-triggered emails), those use the Email Studio templates and inherit the same domain.
What is NOT in the Email channel
To avoid confusion with what you may have used in other platforms:
- Forwarding is a per-domain choice, not a requirement. Atender does not require you to set up forwarding on your mail server. If you set a domain to Your own mailbox forwards them, your own provider keeps the MX and forwards mail to an Atender inbox address. If you set it to They come straight to Atender, the MX records point to Atender and no forwarding is needed. Only direct domains whose MX points to Atender get Atender’s reply address; replies on other domains thread by their email headers.
- No historical mailbox import. Settings → Email → Add inbox connects a Gmail or Outlook mailbox with one sign-in. Atender reads new mail every minute, but older mail is not imported, and Atender does not poll mailboxes over IMAP. Replies go out From the mailbox address, including Outlook shared mailboxes.
- No full deliverability metrics dashboard. Atender surfaces a Deliverability area with an Activity tab showing domain-scoped email activity for verified-owned domains, but bounce, complaint, open, and click metrics are not surfaced as tenant-facing dashboard metrics today.
Where to start
If you are setting up email for the first time, follow this order:
- Add a domain — pick a region and generate your DNS records.
- Verify the domain — add the records at your DNS provider and wait for the status to flip to Active.
- Configure your sending identity — set the From name and From email customers will see.
After that, every reply sent from a conversation goes through your domain automatically.
If you would rather connect a Gmail or Outlook mailbox, skip these steps and use Settings → Email → Add inbox instead.