最近搜索


没有最近搜索

在自行程序中使用“之后的小时数”条件



image avatar

Jennifer Rowe

Zendesk Documentation Team

已于 2025年3月19日 编辑


3

0

47 条评论

8451940939290 just disable it and create a trigger. Should work, I do it that way in my sandbox account. 

0


Hi! Can we usr Hours since ticket category solved is less than 1? 
We want to send the CSAT request immideately. We tried to use the placeholder {{satisfaction.survey_section}} in macro but it automatically becomes a link instead of the rating form ( as when you insert the placeholder manually)

SO if we can use the placeholder in the macro, can we use automations less than in an hour? Thank you 

0


Bonjour, 
Est-il possible d'utiliser la condition "Temps écoulé depuis" en heures plutôt qu'en minutes dans les automatisations ? 
 

0


"Hours since pending" - If we re-save the ticket from Pending to Pending, will it reset the clock, or will it take the first Pending timestamp? Example scenario is, if we update a different field to a Pending ticket and then save as Pending again.

0


6848477249434 the first condition is for tickets in the Solved status

 

The second condition will include any ticket with a status of Solved or any custom statuses that you've created within the Solved category.

 

See “Ticket statuses” in your admin side of your Zendesk instance.

1


6848477249434 yes

 

Ticket statuses all belong to a status category as well 

 

So Open = Open cat

new = new category

Pending = pending category

etc., 

 

This basically gives you flexibility if you use other custom statuses, or plan to in the future, that maybe have a many:1 relationshiip. 

 

My org has “Waiting on Customer” and “Waiting on internal” as two pending ticket statuses. Both belong to the pending category but are labeled as I have in quotes above. So, the automation levers can either let you pick a specific status, or grab the enture category to run your automations. 

1


Anyone know what's the difference between “hours since ticket status category solved” vs “hours since ticket status solved” in this context?

 

0


1263082148149 i am just trying to cheat the system, really. 

 

long story: it all plays into messaging 
short story: i thought maybe an automation for greater than 0 would run on the hour or whatever is the cadence that automations run, and then it would look for all tickets that meet my criteria, basically no matter how recently they were satisfied. 

Basically I want to close messaging tickets via automation, because the instantaneous trigger is too fast and messes with some of our metrics. We decided to add an automation instead, but an entire hour, sometimes more, feels a bit too long, so I was hoping that i could cheat the system!

0


Hi Bobby,

Can you tell us more about your use case what is the goal of the "Ticket: Hours since solved > Greater than  > 0" condition?  As you may already know, Automations execute sequentially every hour, firing on tickets where the conditions are satisfied.

For this reason, "hours since solved greater than "0" is more or less functionally equivalent to "greater than or equal to 1", as the conditions are likely not going to be checked on exactly the 1 hour mark as mentioned in our documentation about automations:

  • Automations run every hour, but that does not necessarily mean top-of-the-hour. Your automations will start running at some point during the hour, maybe five minutes after the hour or thirty-eight minutes after the hour
  • The entire time it takes your automations to run and execute depends on how many automations and tickets there are to process. Automations run again at some point during the subsequent hour.

0


Can you do "Hours since solved.. greater than … 0?

0


登录再写评论。