Placeholders in Zendesk are used in triggers to pass content to users, but they can be exploited by spammers. To prevent this, you should remove placeholders that spammers target, such as {{ticket.title}}. Update your account's version of the 'Notify requester and CCs of received request' trigger by adding the condition 'Current user | Is | (end user)'. Then, remove any reference to placeholders in the 'Email subject' and 'Email body' fields.
This adjustment doesn't stop spam tickets from being created but prevents spammers from sharing their content with your customers.
Requiring authentication for Zendesk's request and uploads APIs is a great way to combat spam. To enable this, go to the Admin Center, click on 'People' in the sidebar, then select 'Configuration' > 'End users'. Here, you can enable 'Anybody can…
Blocking email domains is a temporary but effective way to prevent spam in Zendesk. You can use the blocklist feature with the modifier 'reject:' to block specific domains or email addresses. For example, use 'blocklist: reject:domain.com…
Using wildcards in Zendesk's blocklist can be a challenge, especially if spammers frequently change their email addresses. While Zendesk doesn't support wildcards directly, you can try blocking patterns like 'reject:NAME*@gmail.com'. This approach…
Creating a trigger for agent-created tickets in Zendesk ensures that users are notified of ticket content without allowing spammers to do the same. New accounts typically have the default trigger 'Notify requester of new proactive ticket', but…