Why Tickets Stay Unassigned in a Shared Inbox
Tickets that stay unassigned slow down support. This guide walks through the usual causes and shows how to confirm and fix each one.
On this page
When a shared inbox shows tickets without an owner, no one gets notified and work stalls. The symptom is simple: tickets appear in the queue but stay unassigned.
No assignment rule configured
The most frequent cause is that the inbox lacks a rule telling the system who should own a new ticket.
How to confirm
- Open the shared inbox settings and locate the assignment‑rules section.
- If the list is empty or only contains a disabled rule, nothing will automatically assign incoming tickets.
How to fix
- Create a rule that assigns tickets to a specific team member, a round‑robin pool, or the agent who last replied.
- Save the rule and test by sending a test email to the inbox address.
Default assignee not set for email‑to‑ticket conversion
Automatic email‑to‑ticket conversion can be configured to leave the assignee blank.
How to confirm
- In the email‑to‑ticket settings, look for a default‑assignee field.
- If it is set to "None" or left empty, every converted ticket will start unassigned.
How to fix
- Choose a default assignee (a specific agent or a team queue) and save.
- Send a test email again and verify the new ticket shows an owner.
Team members not added to the shared inbox
If agents have not been added as members of the shared inbox, the system cannot assign tickets to them.
How to confirm
- Review the members list in the shared inbox settings.
- Missing agents will not appear, and any rule that references the team will have no targets.
How to fix
- Invite the missing agents using their work email addresses.
- Assign each a role that permits ticket ownership.
- After they accept the invitation, re‑run the assignment rule test.
Ticket status workflow missing an assignment step
The workflow that moves a ticket from its initial status to the next may not include an assignment action.
How to confirm
- Open the ticket‑status workflow settings.
- Check the transition from the initial status to the next status for an "Assign" action.
How to fix
- Edit the transition and add an assignment action (assign to rule, assign to current user, or assign to a queue).
- Save and create a test ticket to confirm the assignee appears immediately.
AI reply suggestions do not assign tickets
AI reply suggestions help agents draft responses but never change ticket ownership.
How to confirm
- Observe a ticket that receives an AI suggestion but no agent clicks "Take" or "Assign".
- The assignee field stays blank.
How to fix
- Combine AI suggestions with an assignment rule (see the first cause) or encourage agents to claim tickets manually when they open them.
UI display issue
Occasionally the interface fails to display the assignee even though the data is stored.
How to confirm
- Open the inbox in an incognito window or a different browser.
- If the assignee appears there, the issue is local.
How to fix
- Clear the browser cache and cookies for the application domain.
- Reload the inbox; the assignee should now be visible.
If nothing worked
When the above checks do not resolve the problem, take these steps:
- Review the audit log for any errors during ticket creation or assignment.
- Verify that the inbox email address is correctly configured and receiving mail.
- Re‑create the shared inbox from scratch, copying over any needed rules, then test again.
- Contact support with the audit‑log excerpts and a description of the steps you have tried.
If you need a free shared inbox that includes assignment rules, AI reply suggestions, and automatic email‑to‑ticket conversion out of the box, try NeuraDesk free.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free