Recent searches
No recent searches
Feature Request: Allow Trigger to have a "case" condition that would change the action based on the "case" matched
Posted Jun 09, 2020
Based on https://support.zendesk.com/hc/en-us/community/posts/360002973268/comments/360011548354
Feature Request:
Allow Trigger to have a "case" condition that would change the action based on the "case" matched
Description/Example/Use Cases/Proof of End-Users Requesting:
https://support.zendesk.com/hc/en-us/community/posts/360002973268/comments/360011548354
Use Case:
When using a trigger based on keywords, it is necessary to duplicate the trigger to check for a different keyword and change the action. This would simplify how many triggers Admins would need to accomplish this.
8
3
3 comments
Brandon Meyer
Why is this still not a feature? The lazy excuse by the moderator in the forum post indicates Zendesk's lack of understanding when customers use their triggers. If I have 20 triggers and I want non-customer emails to not go through all the triggers I should be able to set it to not use all triggers if it matches my criteria.
The excuse to "save us from ourselves" is both disrespectful and insulting to the admins. ANY FEATURE can be used negatively.
0
mfg
This feature would also allow ease of use and control. If a ticket shouldn't need to interact with rules, or if you want confidence that it won't, this feature would simplify its reactivity.
0
Joel Cohen
Hey Alejandro - New PM for Triggers and Automations here catching up on community posts.
Thank you for taking the time to provide us with this feedback. I apologize for the delay in our response.
I understand the frustration with having to create multiple triggers due to the lack flexibility with Triggers logic. This is a great feature request and it is on our backlog. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.
0