Shared Inbox Not Syncing Across Agents: Troubleshooting Guide
When agents see different emails or missing threads in a shared inbox, collaboration breaks down. This guide walks through the most common sync problems and how to fix them.
On this page
- Check the basics first
- Cause 1: Permission or role misconfiguration
- Cause 2: Email forwarding or routing rules conflict
- Cause 3: Cached or stale views
- Cause 4: Conversation assignment or status filters
- Cause 5: Threading or conversation grouping errors
- Cause 6: Sync delays from high volume or API limits
- Cause 7: Mobile app background refresh disabled
- Cause 8: Two-way sync not configured for "send as" addresses
- What to do if nothing worked
You open the shared inbox and see a conversation your colleague says they replied to — but it's not there. Or two agents reply to the same customer because neither saw the other's draft. Sync issues in a shared inbox create duplicate work, missed messages, and frustrated customers.
Check the basics first
Before digging into platform-specific settings, verify the fundamentals:
All agents are logged into the correct account Confirm every team member is signed in to the same shared mailbox or help desk workspace. A common mistake: an agent accidentally uses a personal email alias instead of the shared address.
Internet connection is stable Intermittent connectivity can delay sync. Ask agents to refresh the page or restart the desktop app. If your tool has a sync status indicator (often a spinning icon or cloud symbol), watch it for a minute.
Browser or app is up to date Outdated browsers or mobile apps sometimes fail to pull real-time updates. Have everyone update to the latest version and clear cache if the problem persists.
Cause 1: Permission or role misconfiguration
How to confirm
- One agent sees tickets another cannot
- An agent can reply but not assign or change status
- New team members report missing historical conversations
How to fix Review each agent's role in your help desk settings. Most platforms use roles like Admin, Agent, and Viewer. Ensure everyone who needs full access has the Agent role (or equivalent). Check that the shared inbox is explicitly added to their permitted mailboxes — some tools require this step per user.
Cause 2: Email forwarding or routing rules conflict
How to confirm
- Emails arrive in the shared inbox but disappear after a few minutes
- Some messages skip the shared inbox entirely
- Replies sent from the shared address bounce or go to a personal sent folder
How to fix Check your email provider (Google Workspace, Microsoft 365, etc.) for forwarding rules that might redirect messages before they reach the help desk. Common culprits:
- A rule forwarding support@ to a personal address
- A "send as" delegation that routes replies through an individual mailbox
- Spam filters quarantining messages before the help desk fetches them
Disable or adjust these rules so the help desk is the primary receiver. If you use automatic email-to-ticket conversion, ensure the forwarding address matches exactly what your help desk provides.
Cause 3: Cached or stale views
How to confirm
- Refreshing the page shows different content each time
- Search returns a conversation that doesn't appear in the main list
- Mobile app shows older data than the web app
How to fix Force a hard refresh (Ctrl+Shift+R / Cmd+Shift+R). On mobile, pull down to refresh or close and reopen the app. Some help desks have a manual sync button — use it. If your team uses browser extensions (ad blockers, privacy tools), disable them temporarily; they can block the WebSocket connections that push real-time updates.
Cause 4: Conversation assignment or status filters
How to confirm
- An agent says "I don't see that ticket" but search finds it
- The ticket count in the sidebar doesn't match the list
- Switching between "Open," "Assigned to me," and "All" changes visibility dramatically
How to fix Shared inboxes often default to a personal view ("Assigned to me") rather than "All conversations." Train agents to check the active filter. Create a saved view named "Team queue — all open" and pin it for quick access. If tickets auto-assign on reply, verify the assignment logic isn't hiding conversations from agents who should see them.
Cause 5: Threading or conversation grouping errors
How to confirm
- Replies appear as separate tickets instead of one thread
- The same customer email splits across multiple conversations
- Agents reply to different threads for the same issue
How to fix This is usually a threading algorithm issue. Most help desks group by subject line, references header, or sender/recipient pair. If subjects change ("Re: Re: Fwd:") or the customer replies from a different address, threads can split. Check your tool's threading settings — some allow stricter or looser matching. Merge split conversations manually if needed.
Cause 6: Sync delays from high volume or API limits
How to confirm
- Sync works normally during quiet periods but lags during peaks
- Error logs show rate-limit warnings
- The help desk status page reports degraded performance
How to fix If you're on a free or lower-tier plan, you may hit API rate limits. Check your provider's limits (often 60–100 requests per minute). Reduce polling frequency if configurable, or batch operations. For persistent high volume, consider a plan with higher limits or a tool with flat pricing that doesn't penalize volume. NeuraDesk includes shared inbox, AI reply suggestions, and ticket status tracking free with no per-agent fees, so volume spikes don't trigger surprise bills.
Cause 7: Mobile app background refresh disabled
How to confirm
- Desktop users see updates instantly; mobile users see delays of minutes or hours
- Opening the mobile app manually triggers a sync
How to fix On iOS: Settings → General → Background App Refresh → enable for your help desk app. On Android: Settings → Apps → [Your Help Desk] → Battery → Allow background activity. Some Android manufacturers (Samsung, Xiaomi) add extra battery optimizations — add the app to the "never sleeping" list.
Cause 8: Two-way sync not configured for "send as" addresses
How to confirm
- Agents send from the shared address but sent emails don't appear in the shared inbox
- Sent folder shows the message in the agent's personal sent items only
How to fix This depends on your email provider. In Google Workspace, enable "Send as" delegation and ensure the shared mailbox has "Store sent messages in this mailbox" turned on. In Microsoft 365, configure the shared mailbox with "Sent Items" copying via PowerShell or the Exchange admin center. Your help desk may also need SMTP credentials for the shared address to capture outbound mail.
What to do if nothing worked
- Reproduce with two browsers — Log in as two different agents in incognito windows. Perform the same action (reply, assign, change status) and note exactly what each sees.
- Check the audit log — Most help desks log every action with timestamps. Look for gaps or errors around the time sync failed.
- Contact support with specifics — Provide: time of issue, agents affected, steps to reproduce, browser/app versions, and screenshots of both views side by side.
- Test a minimal setup — Create a test shared inbox with only two agents and no automation rules. If sync works there, re-enable rules one by one to isolate the conflict.
If your current tool makes troubleshooting this hard — hidden logs, no audit trail, limited permission granularity — it may be time to evaluate alternatives.
Try NeuraDesk free and see if a simpler shared inbox solves the sync headaches.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free