Customer emails aren’t arriving as conversations
When a customer says “I emailed support and got no reply” but the conversation never appeared in Atender, work through this list.
1. Is the domain Active?
Open Settings → Email and confirm the status of the domain the customer wrote to.
- Pending or Failed — verification hasn’t completed. Inbound mail will not be processed. See Domain statuses.
- Disabled — someone turned the domain off. Re-enable it from the domain row.
- Active — keep going through this list.
2. Did the customer actually send it?
Ask the customer to forward you the original message they sent (not “I tried to send something”). Confirm:
- The recipient address they used was on one of your Active domains.
- The timestamp shows it was actually sent.
- They didn’t get a bounce or rejection back from their own mail server.
A common pattern: the customer typed the address wrong (suport@acme.com instead of support@acme.com) and never noticed the bounce notification.
3. Is the message being filtered as spam or bulk mail?
Open the Spam tab in Settings → Email and check whether Enable score based spam filter is on. Mailgun’s spam filter uses a score threshold: first-contact messages that score at or above the threshold are placed in the Spam view instead of Active.
Atender can also use an optional bulk/graymail filter. When that filter is enabled, first-contact messages with bulk or machine-mail headers may be placed in the Spam view instead of Active.
Before escalating to support, check the Spam view for the missing message. If the sender or domain is legitimate, manage trusted sender or domain exemptions in Settings → Email → Spam so future messages are delivered normally.
If you still can’t find the message, ask support to check Mailgun’s logs for the specific message — Mailgun records every inbound message it receives and what it did with it, even when the message was discarded.
4. How is the domain set up to receive replies?
In Settings → Email, check the domain’s How customer replies reach Atender setting. What to verify depends on which mode it uses.
They come straight to Atender
Mail is delivered directly to Atender, so the MX records Atender generated must still be in place. If you recently changed DNS at your provider, double-check them. Some DNS migrations strip records, and some providers have “auto-cleanup” of records they don’t recognize.
- Look for the MX warning shown on the domain in Settings → Email. If it appears, the domain’s MX records no longer match what Atender expects.
- Use a DNS lookup tool to confirm
dig MX yourdomain.comreturns Mailgun’s MX values, not something else.
Your own mailbox forwards them
Mail arrives at your own mailbox first and is forwarded to the Atender inbox address. If the forwarding stops, nothing reaches Atender, even though the domain still shows as Active.
- Confirm that the mailbox forwarding to the Atender inbox address is still active. Forwarding rules can be removed or disabled by mailbox changes, account migrations, or provider policy updates.
- Send a test message to the mailbox and confirm it is forwarded on to Atender.
5. Did mail go to a human mailbox instead?
How this applies depends on the domain’s How customer replies reach Atender setting.
They come straight to Atender: If you use the same domain for human mailboxes (Gmail, Microsoft 365, etc.), inbound mail goes to whatever MX records are active. Atender’s MX records and your old MX records cannot both be authoritative.
If you intend to keep human mailboxes on the apex domain, use a subdomain like support.yourdomain.com for the Atender channel. See Required DNS records for the subdomain pattern.
Your own mailbox forwards them: Mail is expected to land in your mailbox first, so check whether it was forwarded on. Look in that mailbox for the missing message. If it’s there but never reached Atender, the forwarding is the problem. Review the forwarding rule from section 4, including any filters that might hold back some messages.
6. Is the conversation in Archived, not Active?
A customer reply to an old conversation may reopen that conversation rather than create a new one. If the old conversation is Archived, the reply starts a new conversation. If it’s in Done, the reply reopens it back to Active.
Search by the customer’s email address from the inbox search bar. The message may be on an existing conversation rather than a new one.
When to ask for help
Ask support if:
- Domain is Active.
- The customer can show you a sent email that was definitely addressed to a real address on the domain.
- The conversation does not exist in any status (Active, Snoozed, Done, or Archived).
Include the customer’s email address, the address they sent to, and the timestamp. Support can look up the message in Mailgun’s logs to see whether it reached Atender at all.