Fix Notifications Not Sending to Agents

If your agents aren’t receiving ticket notifications, start by checking email delivery settings, spam filters, and user preferences. This guide walks through the most common causes and how to fix them.

NNeuraDesk TeamNovember 19 20264 min read
On this page

Agents open the help desk expecting to see new ticket alerts, but the inbox stays quiet. No email arrives for new tickets, replies, or status changes. The symptom is usually silent — no error message, just missing notifications.

1. Email delivery settings misconfigured

This is the most frequent cause. The help desk sends notifications through an SMTP server or built‑in mail service. If the host, port, username, password, or TLS setting is wrong, messages never leave the outbox.

How to confirm

  • Open the email settings page in the admin area.
  • Send a test email to your own address.
  • Check the sending log (often labeled "Email logs" or "Outbound mail") for a failure entry.

How to fix

  • Verify the SMTP host and port with your email provider (common ports: 587 for TLS, 465 for SSL).
  • Re‑enter the username and password, watching for extra spaces.
  • Ensure the "From" address matches a verified sender domain.
  • Save and run another test email.

2. Notification rules disabled or misconfigured

Help desks let you define which events trigger emails — new ticket, assignment, reply, SLA breach, etc. A rule may be turned off, scoped to the wrong team, or set to "only for high priority".

How to confirm

  • Navigate to the notification rules (sometimes called "Automations" or "Triggers").
  • Look for rules that should fire for the missing events.
  • Check the rule status (active/inactive) and the conditions.

How to fix

  • Enable any disabled rule that covers the needed events.
  • Adjust conditions so the rule matches the tickets your agents handle.
  • Add a test ticket that meets the conditions and verify an email is sent.

3. Agent email address incorrect or unverified

If an agent’s profile contains a typo, an old address, or an unverified email, the system may drop the notification silently.

How to confirm

  • Open the agent’s user profile.
  • Confirm the email address is current and spelled correctly.
  • Look for a verification status badge (often "Verified" or "Pending").

How to fix

  • Update the address to the correct one.
  • If verification is required, resend the verification link and have the agent click it.
  • After verification, trigger a test notification.

4. Spam or junk filters blocking messages

Even when the help desk sends the email, corporate spam filters, Gmail/Outlook junk folders, or domain reputation issues can prevent delivery.

How to confirm

  • Ask a few agents to search their spam, junk, and promotions folders for the sender address.
  • Check your sending domain’s SPF, DKIM, and DMARC records with an online validator.
  • Review bounce reports in the email logs for "spam" or "rejected" codes.

How to fix

  • Add the help desk’s sending domain to the organization’s allow‑list.
  • Ensure SPF/DKIM/DMARC are correctly published for the sending domain.
  • If using a shared IP, consider a dedicated sending IP or a reputable transactional email service.

5. Shared inbox not syncing across agents

When a team uses a shared inbox, a sync problem can make it appear that notifications never arrived, even though the email was delivered to the mailbox.

How to confirm

  • Open the shared inbox view and look for the missing ticket.
  • Check the sync status indicator (often a spinning icon or "Last synced" timestamp).
  • Review the sync log for errors.

How to fix

6. Sending quotas or rate limits exceeded

Some platforms impose daily or hourly email limits. Hitting the cap stops further notifications until the window resets.

How to confirm

  • Look at the email usage dashboard or sending statistics.
  • Search the logs for "quota exceeded" or "rate limit" messages.

How to fix

  • If you are on a free tier, check the plan’s email allowance.
  • Upgrade to a higher tier or request a limit increase from the vendor.
  • Stagger automated notifications (e.g., batch SLA alerts) to stay within limits.

7. Platform outage or maintenance

Occasionally the help desk service itself experiences an outage that halts outbound mail.

How to confirm

  • Visit the vendor’s status page or follow their status Twitter account.
  • Check community forums for similar reports.

How to fix

  • Wait for the provider to resolve the incident.
  • If the outage is prolonged, consider a backup notification channel (e.g., webhook to Slack) if your plan supports it.

When nothing works

If you have verified settings, rules, addresses, spam filters, sync status, quotas, and the platform is healthy, gather the following and contact support:

  • Screenshots of email settings and notification rules.
  • Recent email logs showing the failure.
  • Agent email addresses affected.
  • Steps you have already tried.

A clean, free help desk that handles notifications out of the box can remove many of these variables. If you need a simpler setup, 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