Zendesk employs several strategies to prevent mail loops, though not all loops can be stopped. Measures include suppressing automated notifications for Zendesk-to-Zendesk emails, maintaining a partner addresses list, using unique support addresses, and not creating tickets from bulk or no-reply addresses. Additionally, Zendesk limits the number of updates a user can make in an hour to prevent loops from escalating.
For more details, check out theZendesk help article.
A mail loop occurs when two systems automatically reply to each other, creating a never-ending cycle of emails. This can happen when a ticket is created in Zendesk Support and an automatic notification is sent, which then triggers another automatic…
When Zendesk receives an email from another Zendesk account, it creates a ticket or threads the reply into the original ticket. Automatic message triggers are suppressed to prevent mail loops, but notifications generated by agent actions are still…
Unique support addresses are crucial in Zendesk to prevent mail loops. If a user has an email address that matches a support address, it can create a loop where notifications are sent back to Zendesk, generating more tickets. By ensuring support…
Zendesk does not create tickets from bulk mail or no-reply addresses by default. These emails are often suspended to prevent mail loops. If necessary, you can add these addresses to the allowlist, but automatic notifications will still be…
Zendesk limits the number of updates a single user can make within an hour to prevent mail loops. The limit is set at 20 emails per hour, with the next 20 updates being suspended. If more than 40 updates are received, additional updates are…