Troubleshooting Email-to-Ticket After Moving From Gorgias

After switching from Gorgias, incoming emails stop creating tickets. This guide walks through the most common causes — forwarding setup, DNS propagation, spam filters, inbox mapping, and legacy Gorgias rules — and shows how to verify and fix each one.

NNeuraDesk TeamNovember 19 20264 min read
On this page

You moved your support inbox from Gorgias to a new helpdesk, but emails are no longer turning into tickets. The symptom is usually silent: messages arrive in the mailbox, yet the ticket list stays empty. Below are the most likely reasons, ordered from most to least common, with a quick way to confirm each one and the steps to resolve it.

1. Email forwarding not configured correctly

How to confirm

  • Send a test email from an external address to the support address.
  • Check the forwarding mailbox (or the new helpdesk's inbox) to see whether the message appears there.
  • In the new helpdesk, look for any "incoming mail" log or activity feed that shows receipt.

How to fix

  • Verify the forwarding address in Gorgias (or the former DNS settings) points to the exact inbox address the new helpdesk provides.
  • Ensure the forwarding rule is set to "forward and keep a copy" or "forward only" as required by the new system.
  • Remove any old forwarding rules that may send mail to a deprecated address.
  • After changes, send another test email and confirm a ticket is created.

2. DNS or MX record changes not fully propagated

How to confirm

  • Use a DNS lookup tool (such as dig or an online MX checker) to see the current MX records for your domain.
  • Compare the returned records with the values the new helpdesk expects.
  • If the records still show the old Gorgias values, propagation is incomplete.

How to fix

  • Update the MX records at your domain registrar to match the new helpdesk's specifications.
  • Lower the TTL temporarily (for example, 300 seconds) to speed up future changes.
  • Wait for propagation (typically a few minutes to a few hours) and then test again.
  • If you use a third‑party email provider (Google Workspace, Microsoft 365), make sure the provider's routing rules also point to the new inbox.

3. Spam filters or security rules blocking conversion

How to confirm

  • Check the spam or quarantine folder in the forwarding mailbox.
  • Look for any bounce or rejection notices from the new helpdesk's mail server.
  • Review the helpdesk's email‑processing logs for entries like "rejected" or "filtered".

How to fix

  • Add the new helpdesk's sending domains and IP ranges to the allowlist in your email provider's admin console.
  • Disable or adjust aggressive spam‑filter settings that may strip attachments or rewrite headers.
  • Ensure DKIM, SPF, and DMARC records are aligned for the new sending domain.
  • Resend a test email after changes and verify ticket creation.

4. Inbox mapping mismatch (shared inbox vs. personal inbox)

How to confirm

  • In the new helpdesk, open the inbox settings and note which email address is mapped to the shared inbox used for ticket creation.
  • Compare that address with the one you configured for forwarding.
  • If the helpdesk expects a shared inbox address (e.g., support@yourdomain.com) but you forward to a personal address (e.g., jane@yourdomain.com), tickets will not appear.

How to fix

  • Update the forwarding destination to the exact shared inbox address the helpdesk monitors.
  • If you need multiple teams, create separate shared inboxes and forward each relevant address accordingly.
  • Confirm the mapping by sending a test email to each address and checking the corresponding ticket view.

5. Legacy Gorgias auto‑reply or tag interfering with processing

How to confirm

  • Examine a sample email that failed to become a ticket. Look for headers such as "X-Gorgias-Auto-Reply" or custom tags added by Gorgias rules.
  • In the new helpdesk's email‑processing logs, see if the message is received but then dropped because of an unrecognized header or tag.

How to fix

  • Disable any remaining Gorgias auto‑reply rules that may still be active on the old account.
  • If you cannot disable them immediately, create a filter in the new helpdesk (or upstream email provider) to strip the problematic headers before the message reaches the ticket engine.
  • Test again after the filter is in place.

If nothing worked

  1. Collect the full email headers of a test message that did not convert.
  2. Open a support ticket with the new helpdesk, attaching the headers and a description of the steps you have already tried.
  3. While waiting, consider a temporary workaround: manually create tickets from the missed emails or use the helpdesk's API to import them.
  4. If the issue persists and you need a helpdesk that includes automatic email‑to‑ticket conversion at no cost, NeuraDesk offers that feature free of charge.

For a deeper look at missing emails after a Gorgias migration, see Troubleshooting Missing Emails After Moving From Gorgias.

If you need a free helpdesk that converts emails to tickets automatically, try NeuraDesk free.

Try NeuraDesk free and see if it fits your team.

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