Skip to main content
New Idea

Automation: Actions performed by system should have same criteria as actions performed by agent/requester

Related products:Freshdesk
  • May 10, 2022
  • 7 replies
  • 136 views

tboardman
Apprentice
Forum|alt.badge.img+1

In automation rules, it’s baffling why “When action performed by System” has so few options available compared to actions performed by agent/requester. This makes 0 sense, because I can’t trigger additional automations based on another automation rule. Please expand the options for System actions to mirror those for agent/requester ASAP. 

 

For example:

Freshdesk is binary when it comes to Closed/Resolved email notifications. Meaning you can only have 1 closed email format for all ticket types, groups, etc. 

I’ve implemented an auto-check in automation which is time based. This series of rules sends a check in to the customer after x amount of hours. After an amount of time without the customer responding, the automation rule then sets the ticket to resolved. This is standard practice. 

We operate with multiple groups in Freshdesk. Some groups handle our implementation tasks for customers, others handle daily support. Within those groups, there are multiple ticket types, products etc. What I was hoping to accomplish was to create ticket closure emails via automation so I can customize the closure email contextually for different tickets instead of being limited to the generic ticket closure email that Freshdesk provides. But, since our tickets are closed and sometimes resolved via automation, I cannot accomplish this because the automation options do not allow to trigger when a status is changed by the System. 

This is but the tip of the iceberg for shortcomings that Freshdesk has. When I browse through ideas here, I see many that are years old without any updates. What gives?

 

7 replies

Forum|alt.badge.img+4

Yes! This is causing me some big headaches right now


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Yes! This is causing me some big headaches right now

It’s coming to Freshservice, my guess it’s to prevent loops. 
 


afautley
Top Contributor ⭐
Forum|alt.badge.img+11
  • Top Contributor ⭐
  • August 23, 2023

Yes it is to prevent loops that what i was told. My response was that is the coders problem for bad code… they should put an automatic stop after say 5 or 10 loops so their system does not clog up but if you are looping its becuase you’ve designed it that way or you need to code it better… not restrict those people who know what they are doing. 

 

Great though that this is coming! @Daniel Söderlund any idea of time frame?


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Yes it is to prevent loops that what i was told. My response was that is the coders problem for bad code… they should put an automatic stop after say 5 or 10 loops so their system does not clog up but if you are looping its becuase you’ve designed it that way or you need to code it better… not restrict those people who know what they are doing. 

 

Great though that this is coming! @Daniel Söderlund any idea of time frame?

As I understand this year( in Freshservice)  but don't quote me on that :) 


Thomas H
Top Contributor ⭐
Forum|alt.badge.img+2
  • Top Contributor ⭐
  • August 24, 2023

Yes it is to prevent loops that what i was told. My response was that is the coders problem for bad code… they should put an automatic stop after say 5 or 10 loops so their system does not clog up but if you are looping its becuase you’ve designed it that way or you need to code it better… not restrict those people who know what they are doing. 

 

Great though that this is coming! @Daniel Söderlund any idea of time frame?

I am also pretty sure that it is to prevent loops, so changes in automations cannot trigger automations → Which I kind of understand. When you develop fast and try to put in as much features in as possible in a short amount of time, you may rather do it as it is instead of going the “difficult” way. But at some point, these things need to be consolidated. Freshdesk isn’t a startup anymore!
What I want to see is admins to be notified if a ticket did loop a few times in order to adjust automations.


Forum|alt.badge.img+4

I’m just in Freshdesk and I haven’t heard anything about this coming soon - though I hope so! 

But yeah, I totally agree. Loops are the problem of the coder. 


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

I’m just in Freshdesk and I haven’t heard anything about this coming soon - though I hope so! 

But yeah, I totally agree. Loops are the problem of the coder. 

Nothing for Freshdesk :(