Troubleshooting Missing Emails After Moving From Gorgias

After migrating from Gorgias, some support emails never appear in your new helpdesk. This guide walks through the most common causes and how to fix them.

NNeuraDesk TeamNovember 19 20264 min read
On this page

You switched from Gorgias to a new helpdesk and now a portion of incoming support emails never show up. The symptom is usually the same: customers say they emailed you, but the messages are absent from the shared inbox and no tickets are created. Below are the most likely reasons, ordered from most to least common, with a quick way to verify each one and the steps to resolve it.

1. Email forwarding from Gorgias is not set up or has stopped working

How to confirm

  • Send a test email to the support address you used in Gorgias.
  • Check the Gorgias interface (or the forwarding rule in your email provider) to see if the message appears as forwarded.
  • Look for bounce or delivery‑failure notifications in the sending mailbox. How to fix
  • In your email provider (Gmail, Outlook, Google Workspace, Microsoft 365), verify that the forwarding address points to the new helpdesk’s inbound address.
  • Ensure the forwarding rule is active and not limited to a specific label or filter.
  • If you used a Gorgias‑specific forwarding address, update it to the new destination.

2. DNS MX records still point to Gorgias

How to confirm

  • Run an MX lookup for your domain (e.g., dig MX yourdomain.com).
  • Compare the returned mail servers with the ones listed in Gorgias documentation. How to fix
  • Log in to your domain registrar or DNS host.
  • Replace the old MX records with the records supplied by your new helpdesk.
  • Allow up to 48 hours for propagation, then repeat the MX lookup to confirm.

3. Spam or junk filters are swallowing messages

How to confirm

  • Ask a customer to forward the original sent email to you directly.
  • Check the spam/junk folder of the inbound address used by the new helpdesk.
  • Review any third‑party filtering services (Proofpoint, Mimecast, etc.) for quarantine logs. How to fix
  • Whitelist the new helpdesk’s sending IPs or domains in your email provider and any external filters.
  • Add a rule to move messages from the support address out of spam and into the inbox.

4. Email‑to‑ticket conversion rules are misconfigured

How to confirm

  • Open the helpdesk settings for email‑to‑ticket conversion.
  • Verify that the inbound address matches the one you gave to customers.
  • Check that the rule is enabled and that no condition (subject keyword, sender domain) excludes legitimate mail. How to fix
  • Update the inbound address if it changed during migration.
  • Remove or broaden restrictive conditions.
  • Run a test email from a personal address and confirm a ticket appears.

5. Shared inbox permissions or view filters hide tickets

How to confirm

  • Log in as an admin and view the full ticket list without any filters.
  • Compare the count with what agents see in their default view. How to fix
  • Adjust role permissions so all agents can see tickets created from email.
  • Remove any saved filters that limit the view to a specific tag, status, or assignee.

6. Gorgias account still active and processing mail

How to confirm

  • Log into the old Gorgias account and check the recent conversations list.
  • Look for tickets that were created after your migration date. How to fix
  • Disable or delete the Gorgias inbound email integration.
  • Cancel any auto‑reply or routing rules that forward mail back to Gorgias.
  • Confirm that the old forwarding address is no longer accepted by your email provider.

7. Rate limits, API throttling, or temporary service outages

How to confirm

  • Check the helpdesk’s status page or incident log for the time window when emails went missing.
  • Review any API usage dashboards for spikes or errors. How to fix
  • If a temporary outage occurred, the missing emails may have been queued and will appear once the service recovers.
  • For persistent rate‑limit errors, contact the helpdesk support team with timestamps and sample message IDs.

What to do if none of the above solves the problem

  1. Enable full email logging (if your helpdesk offers it) and capture the raw headers of a missing message.
  2. Send a test email from a completely different domain (e.g., a personal Gmail account) to rule out sender‑side issues.
  3. Verify that the inbound email address accepts mail from unauthenticated senders; some providers reject messages that fail SPF/DKIM.
  4. Collect the evidence — timestamps, sender addresses, header excerpts — and open a support ticket with your new helpdesk provider.

If you’re still looking for a free helpdesk that handles email‑to‑ticket conversion, a shared inbox, AI reply suggestions, and ticket tracking, try NeuraDesk free.

Try NeuraDesk free

Found this useful? Share it with your team.

Join teams already using NeuraDesk

Ready to get started?

Create your workspace and try NeuraDesk for free.

Sign up free