First identify which email is missing: an inbound message that should create or update a ticket, an alert sent to an agent, or an outbound reply or notification intended for a customer. Then use the ticket or conversation record to see whether the support platform attempted to send anything. That separates a workflow or configuration problem from an email-delivery problem.
Identify the missing message before changing settings
“Missing email notification” can describe three different failures. Record the recipient, the expected event, and the channel that started the interaction before investigating. A message sent by email, a conversation that began in chat, and a ticket created through an API may follow different notification rules.
| What is missing? | Where to start | What the result tells you |
|---|---|---|
| An inbound email did not create or update a ticket | Check the address the sender used, email forwarding or routing, and the platform’s suspended or spam queue. | If the message never reached the support platform, an agent notification trigger is unlikely to be the first problem to fix. |
| An agent did not receive an alert about ticket activity | Inspect the ticket’s event history and the notification rule or trigger for the event. | A send event points toward delivery or recipient-side filtering; no send event points toward the platform’s rule or configuration. |
| A customer did not receive an automatic notification or reply | Check the ticket or conversation event history, the destination address, and delivery-failure details. | A public reply or notification may have been attempted but blocked, or the workflow may not have sent it at all. |
The steps below use Zendesk and Intercom as examples. Their settings and defaults are product-specific; use the equivalent event logs and notification documentation if your help desk is different.
Follow this troubleshooting sequence
1. Define the expected event and recipient
Write down whether the expected message was for an agent or customer and whether it should follow a new ticket, a reply, or a status change. Note whether the ticket began as an email, chat, WhatsApp conversation, or API-created ticket. If only one person is affected, verify that person’s exact email address before treating the issue as a system-wide outage.
#1 Best Overall
- Update Remote Mute: Enjoy the convenience of dismissing the hub's beep directly from the Smart App, eliminating the need to manually press a button
- 24/7 Remote Monitoring: The wifi freezer thermometer constantly monitors your freezer and immediately alerts you if temperatures rise or drop unexpectedly, including during events such as an improperly closed door or power failure. This allows you to take prompt action to protect your stored items, with continuous monitoring available from anywhere. (Supports 2.4GHz Wi-Fi only)
- 3 Optional Instant Alerts: App push notifications, email alerts, and loud 90dB audible alerts from the Hub. These multiple notification methods help you respond quickly when issues arise. The system also includes hub offline alerts for power outage incidents, low battery warnings, anti-false alarm, and other smart alert settings designed to make monitoring smarter. iOS Critical Alerts bypass Do Not Disturb modes to deliver alarms
- Industrial Grade Accuracy: Powered by a high-sensitivity sensor, this refrigerator thermometer delivers precise monitoring from -40°F to 158°F with an accuracy of ±0.9°F. The 0.9mm ultra-thin flat cable easily passes through refrigerator door seals, helping prevent cold air leakage and reduce frost buildup for more stable internal temperatures. It’s ideal for kitchen freezers, garage refrigerators, fish tanks, hot tubs, RVs, greenhouses, nurseries, as well as commercial and laboratory settings
- Scalable Coverage with Flexible Expansion: The H6Lite Hub connects up to 30 MOCREO BLE sensors within a 230 ft range, including MS1, MS2, ST5, ST6, ST8, ST9, ST10, and SW2. Easily monitor multiple areas at once, and expand your coverage anytime by deploying additional hubs for larger spaces
2. Check whether the platform recorded a send
In Zendesk, open the affected ticket and inspect its events. Look for the trigger or notification event that should correspond to the missing email. If there is no expected notification event, review whether the relevant trigger is active and still exists. Zendesk’s guide to agents who are not receiving new-ticket or update alerts identifies deactivated triggers as a common cause.
If an event indicates that the platform sent the message, do not assume it reached the inbox. Zendesk’s guidance distinguishes a recorded send from successful inbox delivery: when a trigger runs and sends a notification but the recipient still does not receive it, the cause is likely outside Zendesk or the ticketing system. Treat that as a diagnostic direction, not a guarantee that every other part of the workflow is correct.
3. Investigate delivery to the recipient
- Confirm that the ticket or user record contains the intended recipient address, including spelling and domain.
- Ask the recipient to check spam and junk folders, and any quarantine folder they can access.
- Ask the email administrator to check mail-flow rules, blocked senders or domains, quarantine, and other gateway filtering for the support platform’s message.
- In Zendesk, inspect delivery-failure details beside the recipient and review the ticket events log for evidence of an unsuccessful delivery.
If several recipients at one company are affected, ask the administrator to check organization-wide filtering and mail rules. If one recipient is affected, start with that mailbox’s address, rules, and quarantine. These comparisons help narrow the scope without changing a working notification setup for everyone.
4. If inbound mail did not become a ticket, check the route
Verify that the sender emailed a support address configured in the help desk’s email channel. Then check that forwarding from that address to the platform is functioning. In Zendesk, review the suspended-ticket queue: a legitimate message can be held by spam filtering rather than converted into a normal ticket. Zendesk notes that recovering a suspended email signals to its spam filter that the sender is legitimate.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not confuse a message that is suspended or misrouted with an agent notification failure. First establish whether the inbound message reached the support platform and whether it created or updated a ticket; only then investigate alerts generated by that ticket.
5. Review domain authentication for custom sending
If your support platform sends from a custom domain, ask the email administrator to review SPF, DKIM, and DMARC against the platform’s current setup instructions. Zendesk’s deliverability guidance includes include:mail.zendesk.com in its SPF guidance. Domains that send through multiple services need an SPF configuration that accounts for those services according to the platform’s current requirements; do not add a second SPF record as a shortcut.
Authentication changes affect domain configuration, so have the administrator check the applicable records and the platform’s current instructions rather than copying a setup intended for another provider or domain.
6. Run a controlled two-way email test
- From an external email account, send a test message to the configured support address.
- Confirm that the message creates a ticket in the help desk. If it does not, investigate the support address, forwarding, and suspended-mail handling.
- Confirm whether the automatic notification reaches the external mailbox. If the ticket exists but the notification does not, inspect the send event, recipient address, and delivery evidence.
- From the test ticket, add a public reply and check whether it reaches the external mailbox.
- Compare the event history with the mailbox result. Use the failed leg of the test—intake, automatic notification, or reply—to focus the next check.
A public reply tests outgoing customer email. An internal note is for staff and is not an outgoing customer reply, so it is not a valid test of customer email delivery.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCheck channel-specific behavior in Intercom
Intercom’s notification behavior can depend on how a ticket or conversation was created. Check the workspace setting at Settings > Channels > Email > Email settings, then compare the conversation’s origin with the expected notification.
Rank #4
- Smart Wi-Fi Remote Monitoring: Connects to your home WLAN and smartphone, enabling you to check for water leaks anytime, anywhere, and safeguard your home property.
- 100dB Adjustable Loud Alarm: Features a 100dB adjustable audio alarm, ensuring alerts are clearly heard even in remote areas like basements or garages.
- High-Sensitivity Precision Detection: Adopts high-sensitivity sensing technology to accurately detect minor leaks and drips, providing early warnings before problems escalate.
- Battery-Powered & Compact Design: Battery operation ensures functionality during power outages, while its 20×20×10mm compact size allows easy installation in tight spaces like kitchens or bathrooms.
- Detachable Rotatable Bracket The motion sensor is equipped with a removable rotating bracket. With the holder, you can better adjust the detection level.
- API-created tickets: The API call must request notifications by setting
skip_notifications = false. If notifications are skipped by the call, changing an agent’s mailbox settings will not address that cause. - WhatsApp-origin tickets: Intercom does not send email by default for these tickets. Confirm that an email notification is expected for this channel before treating its absence as a delivery failure.
- Chat when the customer is offline: Chat notifications may be delayed. Check whether the message is delayed rather than assuming it failed immediately.
- Spam or bounce status: Spam classification or bounce-list status can block delivery. Check those states when the platform’s expected email is absent.
These examples are documented in Intercom’s “Troubleshooting email notifications for tickets and conversations” article, dated July 17, 2026. Workspace behavior and interface labels can change, so confirm the current setting and ticket behavior in your account.
Interpret the evidence and choose the next action
| Evidence | Likely area to investigate | Next action |
|---|---|---|
| No ticket or conversation exists for an inbound email | Address configuration, forwarding, routing, or suspended mail | Verify the support address and forwarding path, then search the suspended queue. |
| The ticket exists, but no expected notification event appears | Trigger, notification rule, or channel-specific behavior | Check whether the relevant rule is active and whether the originating channel follows that notification path. |
| The event history records a send, but the recipient has no email | Recipient mailbox, gateway filtering, bounce, or delivery failure | Confirm the address, inspect platform delivery details, and ask the email administrator to trace or release the message. |
| External email creates a ticket, but an automatic notification or public reply does not arrive | Outbound notification behavior or delivery | Compare ticket events and delivery details, then check recipient filtering and, for custom sending domains, authentication. |
| Only tickets from one channel lack email | Channel or integration rules | Check the originating channel’s settings and, for API-created Intercom tickets, the notification parameter in the API call. |
Zendesk’s relevant official guidance includes “I am not receiving email notifications of new tickets or ticket updates” (edited September 18, 2026), “Troubleshooting email deliverability” (edited September 17, 2026), and “Testing your email setup” (edited August 28, 2026). Its guide to incoming email requests and notifications also describes inbound routing and notification behavior. The Intercom article cited above covers its workspace, API, channel, spam, and bounce cases.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to send your email or help-desk administrator
A focused handoff makes it easier to trace the message through both systems. Include:
- The ticket or conversation identifier and the time the event occurred, with time zone.
- The sender and intended recipient addresses, shared only through your organization’s approved support process.
- The message direction: inbound email, agent alert, or customer notification/reply.
- The ticket’s origin channel and the specific event that should have generated the email.
- What the platform event history shows, including any delivery-failure details, and the result of the external-account test.
- Whether the issue affects one mailbox, a group at one organization, or all recipients.
For security, do not paste passwords, API secrets, or full message contents containing sensitive customer data into an ordinary support request. Share only the message identifiers or headers your administrator specifically needs and your policy permits.
Frequently Asked Questions
What does it mean if the email appears in the recipient’s quarantine?
The recipient’s mail system received or evaluated the message but held it from the inbox. Ask the email administrator to review the quarantine decision and allow the message if it is legitimate under the organization’s policy; also check whether a rule is likely to quarantine future notifications.
Should I resend the notification while I troubleshoot?
Avoid repeated manual resends until you know whether the platform already sent it. Duplicate notifications can confuse recipients, and a resend may repeat the same filtering or configuration failure. Use the ticket event history and a controlled test to determine which part of the workflow failed first.
What if notifications fail for every help-desk user at once?
Compare a ticket event and delivery result for more than one recipient, then involve both the help-desk administrator and email administrator. A broad failure is more consistent with a shared trigger, sending-domain, forwarding, or mail-gateway issue than with one person’s mailbox, but the logs should identify which side needs correction.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
