Troubleshooting Missing Tickets in NeuraDesk Shared Inbox

Tickets that should appear in your shared inbox are missing. This guide walks through the most common causes and shows how to confirm and fix each one.

NNeuraDesk TeamNovember 19 20263 min read

You open the shared inbox expecting a new customer request, but the ticket is nowhere to be found. The email arrived at the forwarding address, yet the inbox stays empty. This usually points to a handful of configuration or routing issues that can be checked systematically.

Common causes and fixes

1. Email forwarding not set up correctly

How to confirm – Send a test message to the forwarding address and watch the source mailbox. If the message never leaves the source inbox, the forwarding rule is broken or disabled. How to fix – Verify the forwarding address in your email provider matches the unique inbound address exactly, including any plus‑sign tags. Make sure the rule is active and not limited to a specific folder or label. If you recently changed the inbound address, update the rule accordingly.

2. A filter or rule diverting messages to another folder

How to confirm – Search the source mailbox for the missing sender or subject. Check spam, promotions, archive, or any custom folders you created. How to fix – Adjust the filter so that messages matching your support address are not moved, labeled, or marked as read before forwarding. In Gmail, edit the filter and uncheck "Skip the Inbox" and "Apply label". In Outlook, remove any rule that moves the mail to a subfolder before the forwarding step.

3. Team member permissions hiding tickets

How to confirm – Log in as a different agent who has full access. If the ticket appears for them but not for you, the issue is permission‑based. How to fix – Open the team settings and confirm that your role includes "View all tickets" or the specific shared inbox. Add the missing permission and refresh the browser. Permission changes take effect immediately.

4. Email threading merging separate conversations

How to confirm – Open a recent ticket that looks like it should be separate. If the subject line is identical and the thread shows multiple unrelated messages, threading has combined them. How to fix – Ensure each inbound email uses a unique subject or includes a ticket reference that the system can parse. You can also disable automatic threading in the inbox settings if you prefer each email to create its own ticket.

5. Automatic email‑to‑ticket conversion turned off

How to confirm – Go to the inbox configuration page and look for the "Convert emails to tickets" toggle. If it is off, incoming mail will stay as raw messages. How to fix – Enable the toggle and save. The next incoming email should generate a ticket automatically. If tickets still do not appear, review the troubleshooting steps for conversion failures.

6. Recent migration left status updates missing

How to confirm – Compare ticket counts before and after the migration. Look for tickets that show a status of "Open" in the old system but are absent or show "Closed" in the new system. How to fix – Re‑run the migration for the affected date range, or manually create the missing tickets with the correct status. Verify that the migration tool mapped status fields correctly.

If nothing worked

  1. Check the activity log for any error entries around the time the ticket should have arrived.
  2. Confirm that the inbound email address has not been blacklisted or blocked by your email provider.
  3. Test with a fresh email address that forwards directly to the helpdesk, bypassing any intermediate rules.
  4. If the problem persists, contact support with the test email headers and a description of the steps you have already tried.

If you need a simple shared inbox that catches every email, 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