Category

How to Troubleshoot Email Notification Delivery in BoldDesk

Updated:

Email notifications are a critical part of keeping customers and agents updated on ticket activity in BoldDesk. When recipients report missing emails—or when you need to confirm whether a specific ticket update was actually sent—this guide helps you validate delivery and isolate the most common causes of non-receipt.

In this article, you’ll learn how to:

  • confirm that the correct email notification events are enabled so notifications are triggered,
  • verify custom support email deliverability prerequisites (such as DKIM),
  • understand how the “Don’t send an email” reply option affects customer notifications,
  • check delivery outcomes using Email Delivery Status on the Ticket Details page and Email Failure Logs in Audit Logs, and
  • troubleshoot scenarios where an email appears delivered but is not visible to the recipient (spam, mailbox rules, quarantine, or organization-level filtering).
  • Some troubleshooting steps in this article require administrative permissions. If you do not have access to Email Notifications, custom support email settings, or Audit Logs, contact your BoldDesk administrator.
  • BoldDesk uses Amazon SES Managed Dedicated IPs for outbound email delivery. To help maintain email deliverability and sender reputation, AWS automatically manages and rotates the dedicated IP addresses used to send emails based on factors such as sending volume, reputation, and ISP requirements. As a result, email notifications may originate from different IP addresses over time, and a specific IP address is not permanently assigned to a BoldDesk account. When reviewing email headers, you may see different Amazon SES outbound mail server IP addresses used for email delivery.
  • If an email notification has been successfully sent but is not visible in the recipient’s mailbox, check the Spam/Junk folder, review any configured mailbox rules or filters, and verify whether the email has been placed in quarantine by your email system. If the email cannot be located after these checks, contact your organization’s email or network administrator to determine whether it is being filtered, quarantined, or blocked by email security policies. For additional troubleshooting steps, refer to the article Check delivery status and fix missing emails for email notifications.

BoldDesk intentionally suppresses email notifications to agents for their own updates, even if those agents are included in the ticket’s CC or watcher field.

Prerequisites

Before troubleshooting email delivery issues, ensure that:

  • You can access the affected ticket.
  • You know the email address that should have received the notification.
  • You have permission to view the ticket and its email delivery information.
  • For organization-wide delivery troubleshooting, administrator access may be required.

Recommended Troubleshooting Order

For the fastest resolution, follow these checks in order:

  1. Verify that the ticket action should generate an email notification.
  2. Confirm that the related email notification event is enabled.
  3. Verify that Don’t send an email was not selected when the update was posted.
  4. Check Email Delivery Status on the ticket.
  5. Review Email Failure Logs in Audit Logs.
  6. Verify the recipient’s email address.
  7. Check spam, junk, quarantine, and mailbox rules.
  8. Review organizational email filtering or security policies.

How to Ensure Email Notifications Are Delivered

Verify Email Notification Settings

Ensure that the appropriate email notification events are enabled in Admin > Email Notifications. If a notification event is disabled, the email will not be generated when the corresponding ticket activity occurs. For more information, learn more on How to Manage and Personalize Email Notifications.

Verify Custom Support Email Configuration

If your organization uses a custom support email address, verify that DKIM has been configured and validated successfully.
Proper DKIM configuration helps establish email authenticity and can improve email deliverability. Missing or incorrect DNS records may cause delivery issues or increase the likelihood of messages being filtered by recipient mail systems. For more information, explore Learn more on How to Setup DKIM for BoldDesk.

Verify the “Don’t Send an Email” Option

When an agent replies to a ticket, they can choose Don’t send an email.
If this option is selected:

  • The ticket update is saved successfully.
  • The update remains visible in the customer portal.
  • No email notification is sent to the customer.

This option is useful when an agent wants to update a ticket without generating a customer email notification.

The presence of a ticket update does not necessarily mean that an email notification was sent. If a recipient reports a missing email, verify that Don’t send an email was not selected and review the update’s Email Delivery Status before investigating delivery-related issues.

Verify the Recipient Email Address

Before investigating delivery failures, confirm that:

  • The requester’s email address is correct.
  • Any CC recipients are valid.
  • There are no spelling mistakes in the email address.
  • The mailbox exists and can receive messages.

Incorrect recipient information is one of the most common causes of notification delivery issues.

How to Check the Email Delivery Status

BoldDesk provides tools to track whether customer-facing email notifications were successfully processed and delivered.

  1. Check Email Delivery Status for a Ticket Update
    • Navigate to the relevant ticket update.

    • Open Email Delivery Status.

      Email delivery status.png

Email Delivery Status helps you review the delivery outcome of email notifications associated with a specific ticket update. For more information, explore How to Check Email Delivery Status for BoldDesk Ticket & Activity.

If a customer reports that they did not receive the email notification for a ticket update, review the Email Delivery Status first to determine whether the notification was generated and delivered before investigating mailbox, spam, quarantine, or email filtering issues. For example, a customer may be able to see the update in the Customer Portal while still not receiving the related email notification.

  1. Review Organization-Wide Email Failure Logs
    To review email delivery failures across the portal:
    • Navigate to Admin > Audit Logs.

    • Open Email Failure Logs.

      Email failure logs.png

Email Failure Logs provide organization-wide visibility into email delivery failures, including rejected, bounced, or otherwise undelivered email notifications. Explore How to Review Email Failure Logs in BoldDesk.

How to Check if Emails Have Been Delivered

If Email Delivery Status indicates that an email notification was delivered, but the intended recipient reports that they did not receive or cannot locate the email notification, review the following items.

At this point, BoldDesk has already reported the email notification as delivered. The investigation should focus on the recipient’s mailbox, email security systems, quarantine, filtering rules, or organizational mail policies.

  1. Check Spam or Junk Folders
    Ask the recipient to review:

    • Spam folders
    • Junk Email folders
    • Other filtered folders used by their email service

    Some mail providers automatically move messages out of the primary inbox.

  2. Review Mailbox Rules
    Ask the recipient to verify whether mailbox rules automatically:

    • Move messages to another folder
    • Archive messages
    • Forward messages to another mailbox
    • Delete messages automatically

    Mailbox rules can make a delivered email notification difficult to locate.

  3. Check Email Quarantine
    Many email security platforms quarantine suspicious or unexpected emails before they become visible to end users.
    Ask the recipient or email administrator to:

    • Review the organization’s quarantine.
    • Locate the email notification.
    • Release the email if it was quarantined.

    For Microsoft 365 environments, administrators can review quarantined messages through Microsoft Defender. If an email is quarantined, please release it.

  4. Test Delivery Using an External Email Address
    If appropriate, test notification delivery using an external mailbox such as:

    • Gmail
    • Outlook.com

    If email notifications are successfully delivered to external email addresses but are not reaching internal corporate mailboxes, the organization’s email security, filtering, quarantine, allow/block lists, or mail-routing policies may be affecting delivery. In this situation, contact the organization’s email administrator for assistance.

Agents will not receive email notifications for their own updates, even if they are included in the ticket’s CC or watcher field.

Retry or Resend a Failed Email Notification

BoldDesk does not currently provide a manual Retry or Resend option for an email notification that appears as failed in Email Delivery Status or Email Failure Logs.

The behavior depends on the failure type:

Failure Type Retry Behavior Required Action
Transient bounce The email-delivery system may retry automatically because the failure is temporary. Monitor the delivery status and correct temporary mailbox, server, DNS, throttling, or filtering issues when required.
Permanent bounce The failed notification is not automatically resent after the permanent failure is confirmed. Correct the recipient address, domain, authentication, sender reputation, or recipient-server policy before generating another notification.
Complaint The recipient or email provider marked the message as spam or unwanted. Review the recipient, notification event, consent, and sending pattern before sending another message.

Correcting the delivery issue does not replay the original BoldDesk notification event.

If the recipient must receive the information immediately, use an appropriate new customer-facing action after correcting the failure, such as sending a new reply from the ticket. This creates a new ticket message and can generate a new notification according to the current email-notification settings.

Do not add an unnecessary or duplicate public reply solely to force a notification without first reviewing the ticket conversation and confirming that another customer-facing message is appropriate.

Frequently Asked Questions

  1. How do I confirm BoldDesk email notifications are actually being sent?
    Verify three items in order:

    • the correct Email Notification event is enabled in Admin > Email Notifications,
    • the agent did not use Don’t send an email for the update, and
    • Email Delivery Status for the ticket update shows the notification was generated and processed.
  2. Where do I check whether a specific ticket update generated an email?
    Open the ticket and use Email Delivery Status on the relevant update in the Ticket Details page.

  3. Where can I see portal-wide email failures such as bounces or rejected emails?
    Go to Admin > Audit Logs > Email Failure Logs to review organization-wide email delivery failures.

  4. What does “Don’t send an email” do in a ticket reply?
    Selecting Don’t send an email saves the ticket update and keeps it visible in the customer portal but prevents BoldDesk from sending the customer email notification for that update.

  5. We configured a custom support email. What deliverability prerequisite should we validate first?
    Validate DKIM configuration and successful verification for the custom support email domain. Incorrect DKIM DNS records can increase filtering or cause deliverability issues.

  6. Email Delivery Status shows “delivered,” but the recipient can’t find the email. What should we do next?
    Check the recipient’s spam/junk folders, mailbox rules, and the organization’s email quarantine. If the recipient uses Microsoft 365, administrators can inspect quarantine in Microsoft Defender.

  7. Why didn’t an agent receive an email notification for an update they posted?
    BoldDesk suppresses email notifications to agents for their own updates, even if the agent is included in the ticket’s CC or watcher field.

  8. Do BoldDesk outbound email IP addresses stay the same?
    No. BoldDesk uses Amazon SES Managed Dedicated IPs, and AWS may rotate outbound IP addresses. Email headers can show different SES outbound IP addresses over time.

Related Articles

  1. How to Manage and Personalize Email Notifications in BoldDesk
  2. How to Setup DKIM for BoldDesk
  3. How to Check Email Delivery Status for BoldDesk Ticket & Activity
  4. How to Review Email Failure Logs in BoldDesk
  5. How to Prevent Duplicate Email Notifications in Ticket Replies
  6. Troubleshooting: Custom Field Placeholder Is Empty in Email Templates
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found