Agents Receive Duplicate Notifications From Shared Inbox
Agents seeing the same ticket alert twice? This guide walks through the usual culprits — overlapping rules, forwarding loops, duplicate accounts, client‑side settings, and automation — with quick checks and fixes for each.
On this page
When every ticket triggers two or more alerts, agents waste time sorting noise instead of helping customers. The symptom is easy to spot: the same conversation appears in multiple notification channels or arrives twice in the same channel within seconds.
Overlapping notification rules
How to confirm Open the notification settings for the shared inbox and list every active rule. Look for rules that fire on the same event — for example, one rule that sends an email on "new ticket" and another that sends on "ticket assigned". If both conditions are true for a new ticket, the system will send two emails.
How to fix Consolidate the rules so each event has a single notification path. Disable or delete the redundant rule, then send a test ticket to verify that only one alert arrives.
Email forwarding loops
How to confirm Check the forwarding addresses configured on the source mailbox (for example, support@company.com). If the mailbox forwards to the shared inbox address and the shared inbox forwards back to the original mailbox, each message circles back and generates a second notification.
How to fix Remove the backward forward or add a filter that stops messages already processed by the shared inbox. In most email providers you can add a header check (such as "X-Processed-By: shared-inbox") to break the loop.
Duplicate user accounts or aliases
How to confirm Review the user list in the helpdesk. An agent may have two accounts — one tied to a personal email and another to a team alias — both subscribed to the same notification channel. Also check whether a distribution list expands to the same individual twice.
How to fix Merge the accounts or remove the duplicate subscription. Ensure each person has a single primary email in the system and that distribution lists do not contain overlapping members.
Client‑side email rules creating double delivery
How to confirm Agents using Gmail, Outlook, or another client may have local filters that copy incoming shared‑inbox mail to another folder or forward it to a personal address. Open the client’s filter list and search for rules that mention the shared inbox address.
How to fix Disable or adjust the local rule so it only labels or archives the message instead of creating a second copy. Test by sending a ticket and confirming a single notification appears in the agent’s inbox.
Automation or workflow rules sending notifications twice
How to confirm Inspect any automation engine (macros, triggers, webhooks) that posts to Slack, Microsoft Teams, or sends SMS. A workflow that fires on "ticket created" and another that fires on "ticket status changed to open" can both run for the same ticket.
How to fix Combine the workflows or add a condition that prevents the second run when the first has already executed. Many platforms let you tag a ticket after the first notification and skip subsequent runs if the tag exists.
If nothing worked
If the duplicate alerts persist after checking the items above, enable detailed logging for the notification subsystem and reproduce the issue with a test ticket. Compare the log entries to see which component emits each alert. When the source remains unclear, reach out to the platform’s support team with the logs attached. For teams that want a simpler setup without per‑agent fees, try NeuraDesk free.
Related reading:
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free