Trigger conditions and actions reference

Have more questions? Submit a request

14 Comments

  • Vassilios Lourdas

    Hi, very good article! I have however a question concerning the 

    Requester: Language Returns the language preference of the person who submitted the request.

    What does actually see as language? The language that is set in the user account? What if the user does not have an account and sends an email, which is converted to a ticket? Does Zendesk read the content of the message and identifies the language automatically?

     

    1
  • Mariliam

    I would love to understand what Vassilios is asking. I'm currently trying to set up triggers for languages for Answer Bot and the trigger for Notify Request received are not firing.

    What would be the best practice to set up a trigger for multi-language support? 

     

    0
  • Vassilios Lourdas

    Hello @mariliam, my question is if Zendesk identifies the language of a support ticket that has come via email. E.g the user who has sent an email and has been converted to a ticket has in his account as language 'English'. However, the email that he sent and has been converted to a ticket is in another language, e.g. Greek. Will Zendesk identify Greek, or will it simply consider it as English?

    0
  • Andrea Rodriguez

    I know this is a newb question, but what would be the difference between "Ticket Status is New" vs "Ticket is Created"? (By default, aren't all created tickets New?) And why would I choose one over the other? 

    0
  • Heather R

    @Andrea - Great question! The difference is, not all tickets are new upon CREATION depending on your setup and use of Zendesk -- in our instance, many times we are the the phone with a customer, create the ticket for them, resolve it on the phone and set the the ticket to Pending or Solved upon creation!

    Likewise, you can update a ticket in New status and it doesn't change from New, particularly if it's being rerouted to another group or a Private note being added for whatever reason.  

    So a ticket can be created and be in any status and a ticket in New status can also have an update and stay in New status (except if it was assigned or manually changed to a different status...)

    THEREFORE... rounding 3rd base here.  In some triggers, I want it to run the moment the ticket is created, no matter what status.  Like, if a ticket is created and any word says "unhappy" I want the system to email the Customer Service Manager immediately so he/she can get on it quick.

    And in some triggers, I want to just tend to New tickets - like, if an agent doesn't attend to a ticket in 5 hours since it was last actioned on by my receptionist who does some triage before the Customer Service agents, then i want to set that time from the last update on that ticket which should also still be in new status. Actually, in this last example it would be an Automation (time-based) but I hope you get my meaning.

    Hope that makes sense!

     

    0
  • Jesse Sarkis

     

    What I am trying to do is filter out auto-replies and feedback surveys and change their ticket status by running a trigger when an end user updates a ticket with a message containing a specific string. My concern is that often these auto-replies come mid-way through a longer investigation during which there have already been messages back and forth between an agent and end-user, but I only want this trigger to run if the auto reply is the first message on the ticket from the end-user. 

    I am curious as to how the comment text : contains string condition would handle replies from an end-user that includes the message history (some of our end user's email services do this). Any suggestions? Will comment text : contains string be sufficient in this case? Or should I add an additional IS NOT status condition? 

    0
  • Bora

    Can i set up a "Ticket: Comment text" filter for URLs in the comment text of a ticket? Consider my options are: 

    • Contains at least one of the following words
    • Contains none of the following words
    • Contains the following string
    • Contains not the following string

    If I wanted to filter by a url such as "acme.com/pricing" where present in the Ticket Comment, can I set up the following: 

    [Ticket: Comment text] [Contains not the following string] [acme.com/pricing] 

    Realize this is an edge case, and for purposes of this question the [Received at] [is not] [acme.com/pricing] filter by domain is not applicable. So I need to know - can URLs can be recognized as strings or words in comment text?

     

    0
  • Jessie Schutz

    Hi Bora!

    I've never done this specifically, but I don't see any reason why it wouldn't work. I'd recommend doing some testing on trigger to make sure it works, but I think you should be find.

    1
  • Lori Sardoff

    The only option I am seeing when creating a trigger is "ticket" "is". where are all the other conditions?  I want to create a trigger for a tag.

    0
  • Nicole - Community Manager

    Hi Lori -

    What plan type are you on? If you're on Essential, you only have access to the default triggers and conditions related to those triggers. Those triggers are outlined here: About the Support default triggers

    0
  • Wouter

    Is there a way for me to activate the trigger when the status doesn't change from a specific status?
    So for example.

    We have a webhook script running that may only be called when the trigger is sent again with the status solved.

    I looked at the conditions and there is not really something that gives me the feeling that is should be used for my usecase.

     

    The one thing that might be it but I really don't know for sure is the following : 
    `status` -> `is not changed from` -> `solved`.

    0
  • Jessie Schutz

    Hey Wouter!

    As long as the condition in the trigger is Status > is > Solved (rather than Status > changed to > Solved, the trigger will run any time the ticket is updated with a Solved status. This goes for any ticket status.

    0
  • Wouter

    Hello Jessie,

    But that also means the trigger will run when it is set to update for the first time.
    We would like to only run the trigger when the status was solved and is submitted again as solved.

    So it doesn't change the status.
    Hopefully this makes actual sense.

    If this is not possible I will change the webhook script :)

    0
  • Heather R

    Hi Wouter, You're right. I think I would try the `status` -> `is not changed from` -> `solved` condition as you mentioned earlier.  I would test it for sure!  Let us know how it works out.

    0

Please sign in to leave a comment.

Powered by Zendesk