Enhanced functionality with Triggers

Hi @chris19 , 

PM for Triggers & Automations here. Thank you so much for taking the time to provide such detailed feedback! Please find a few follow-up questions and feedback on the asks below: 

1. Rearrange conditions/actions - this is new feedback, so thank for sharing! I am assuming you are talking about when you are building a trigger and moving the conditions on the form page. I'm curious what your use case is here. Do you like to see particular conditions/actions grouped? Are you trying to see these in the order of your workflow? Maybe something else...

2. Search text in ticket fields - I hear you, we have some discrepancies in the available operators and would like to create consistency across the field types. These are weighed against our other priorities going into the new year. Is there a particular field that you were referring to? Custom text fields? 

3. Enhanced logic - you hit the nail on the head here! We are currently working towards more flexible logic to build out triggers. More to come on that in the new year!

4. Posting comments with triggers - again, another highly requested feature that we are prioritizing for 2023. More to come on exact timing! I'd also love to hear your use cases here for internal and public comments if you'd be up for sharing. 

5. This would actually fall to the email team. I reached out and they have noted the feedback but it is not currently on their roadmap. 

Thanks, 

Bailey

Hi @bailey11, 

Hope it's ok to jump in here and join this conversation but I'd like to second Chris's feature request as 4/5 of these would be super helpful for us as well! 

1. Rearranging conditions/actions would be immensely helpful! Any time there are 10+ conditions it becomes difficult to keep track of when the Trigger does/doesn't fire and being able to sort them would make it more readable. Being able to group them would be a dream!

Really excited to hear that 3 & 4 are being worked on, would be a game-changer!

Hi Bailey, thank you for the response! I’m happy to hear that some of these are already being discussed. I’d love to answer some of your questions.

1 - One example I could give is my Employee On/Off-boarding workflow. Using Myndbend Process Manager, we have up to dozen child-tickets just for Onboarding (depending on conditions), and even more for Offboarding, that route to other teams as part of the overall request. For each child-ticket, I have 4 triggers based on a custom field for Status (On Track, On Hold, Back On Track, and Cancelled). This resulted 48 triggers just for updating the child-tickets subject lines and posting comments in the tickets. During testing and designing, I’ve added and removed conditions and actions over time. Now, although each trigger is almost entirely identical aside for a few things that make them unique, the conditions and actions are all arranged differently. Whenever I make a change, I need to review each one to verify the change was implemented properly, it becomes quite hectic when they’re all arranged differently. If I could just sort the conditions and triggers, it could save me a lot of time and confusion. Like I said, it’s minor, but sometimes the small things could be the most valuable to a customer.

4 - One thing that’s great about Macros is they support rich text and you can post comments with tables. Using Email triggers, these tables can carry through to Emails alerts. This helps data in Email alerts be easier to read and helps give the impression of a more professional system to my end-users. Right now, Agents have to use a macro to insert a table, but if I could build this into my automated workflows I could reduce the number of clicks performed by the Agents. 2023 is going to be the year of automation for me, and being able to automatically send Public Replies when things happen, and if I could do it without using JSON, and if they supported rich text including tables, I could greatly reduce the number of mundane clicks the agent have to perform.

A specific example is when an Onboard request is submitted, HR has to make sure they use a macro I built for them before submitting the ticket. If the person who normally submits them is on vacation, the individuals filling in for her sometimes forgets. This results in the Email alert not having the standardized table that the company has been accustomed to seeing (and grown to appreciate). I plan on automating the Onboarding ticket creation process when an employee is entered into the HR system this year, but we will be sacrificing the professional looking Email alert unless I could either A - trigger a Macro as an Action, or B - have the ability to post comments with rich text from the trigger.

Thats just one example, but I heavily use Email alerts and Internal Notes in my workflows. I am the only person in the company that knows Zendesk from a technical standpoint. As I climb the ladder, I’m hoping to assemble a small team of people who can be admins of this system, and I think using JSON just to post comments would be a frustrating learning curve for them.

Thanks again for the response! I look forward to seeing what Zendesk announces in the new year!

- CJ

@chris19 & @Shmuel Holzman

Thanks so much for sharing additional details. It is really helpful as we dig in on discovery to make sure we are solving for actual use cases. I'll be sure to include the rich text request as the team moves forward. 

When you are thinking about rearranging conditions, is drag & drop a sufficient solve? You also mention sorting. Would you be looking to sort by the field in the condition?