Out of office triggerAnswered
I needed to create a trigger to reply to any customers emailed update to tickets to notify that that all agents were away on a company event. I set up a basic trigger as below, thinking it would do the trick. But turns out that this didn't work. Can someone help me with what i'm doing wrong or why the trigger didn't actuate. I even tried copying the default "new ticket received" trigger that comes with ZD suite and amending the Ticket Is Created to Ticket Is Updated and placed this trigger at the top of the list but none seemed to make any difference.
Hi Rolf Hayes,
Your trigger looks like it should work. I have one similar. Maybe this will help.
Another option is to create a Trigger that happens during a "scheduled" event or Holiday. So, if you add your Company event to the Zendesk schedule, you can create a Trigger that emails the client about it.
Rolf Hayes One note is that this trigger wouldn't fire for any newly created tickets with how you have it setup currently. I'm wondering if perhaps that's the issue you've been observing? Were you testing this trigger on brand new tickets?
The Ticket Is Updated only fires when an existing ticket is modified and the change is submitted. If you'd like it to fire for both new & existing tickets, you can do that by including both conditions under the Meet ANY of the following conditions section of your trigger setup. See screenshot below:
I also think you're going to want to add some more logic to this trigger, similar to the logic included in Kyle Davis's screenshot. Specially, some Comment is Present logic as well as Current User logic.
Otherwise, this trigger will fire on any update made to the ticket - not just when the customer emails in. For example, if an agent leaves an internal comment on the ticket or simply changes the status of the ticket, this trigger would be fired as it stands currently.
I had a different trigger with different email body for new created tickets and yes I was trying this on an existing ticket. What I have found out since is that this trigger seemed to run on updates by an agent but not by the requester or customer.
I've changed the conditions to be similar to Kyle Davis's and will be trying this out later.
Please sign in to leave a comment.