A complete guide to understanding email in Zendesk - Part 4: Common email channel problems

Fastpath: Admin Center > Channels > Talk and email > Email

Articles in the series

• Introduction: A complete guide to understanding email in Zendesk
• Part 1: How the email channel works
• Part 2: Incoming email requests and notifications
• Part 3: Outgoing email notifications
• Part 4: Common email channel problems

In the last part of this guide, we explain what you can do when things go wrong with the email channel and how you can fix them.

The most common email problem that Zendesk Support customers contact us for support about is that their customers are not receiving outgoing email notifications. This is often the result of issues that are easily resolved.

Here are the common reasons that your customers are not receiving outgoing email notifications:

• You’ve set up an external email domain but haven't added an SPF record to your external domain’s DNS. See Setting up SPF for Zendesk to send email on behalf of your email domain.
• The email notification has been caught in the spam filter in the customer’s email application. To verify that the email notification was sent to the customer, you can easily check the ticket events, which will show you each action that was taken on a ticket. If the notification was successfully sent, the problem is likely on the recipient's end of the email exchange.

  

• You’ve deactivated one or more of the default email notification triggers.
• The conditions contained with a notification trigger (or automation) have not been met.
• The customer’s user account does not include their email address.

Read more about troubleshooting and resolving these problems in Customers are not receiving emails.

Another email problem that occurs far less often but that you should still be aware of is the result of automated email replies created both inside and outside of your Zendesk Support account generating more email notifications than you want. This is called a mail loop and occurs when two automated email reply systems start exchanging messages.

As an example, you might imagine that a trigger such as the Notify requester of received request, which generates an automatic reply, may start a mail loop if the email address it sends an email notification to has been set to generate any automated response that does not announce itself as such, like an out-of-office response. Zendesk Support prevents mail loops like this from occurring, but they sometimes occur under certain circumstances. You can read an in-depth explanation of how Zendesk Support manages mail loops in About mail loops and Zendesk email.