In order to prevent customer from submitting tickets to your support after they have churned , ZD suggested this KB article https://support.zendesk.com/hc/en-us/articles/4408886840986-Setting-your-allowlist-and-blocklist-to-control-email-support-requests.
One of the stakeholder had question that the manual blocklist might not be scalable and what if we have hundreds of domain to the blacklisted , are there any automations ZD can suggest to handle this query. Thanks
Prevent those customers from submitting tickets to your support after they have churned
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Thanks for sharing the KB article and for your thoughtful question!
Managing a large number of domains in a manual blocklist can indeed become difficult as your list grows. To streamline this, instead of relying solely on domain names, you might consider using the organization field within Zendesk to group customers or domains together. This way, you can create automations or triggers based on organizations, which can be easier to manage and more scalable.
For example, you can target tickets from specific organizations to automatically tag, close, or route them according to your needs. Additionally, combining this with your existing blocklist and automation rules will help control ticket submissions more efficiently.
Hope this helps!