Skip to main content
Closed for Voting

Supervisor Operators For "Hours Since"

Related products:Freshdesk
  • May 20, 2015
  • 27 replies
  • 59 views

Please add "Hours since status updated" to the Supervisor rules


We have several custom statuses.  These aren't available in the "Hours since..." group of operators. We would be able to meet our needs for triggers against our custom statuses if we had this operator.


Thanks

27 replies

  • Community Debut
  • November 25, 2015

We would definitely support this idea as well - we are trying to find a way of sending automatic emails a certain number of days after a status has been changed. The workflow:


- Ticket status is set to 'waiting on customer reply'

- After 8 days have elapsed with no reply, send the customer an email requesting feedback

- After 15 days have elapsed with no reply, send a final reminder

- After 17 days automatically mark the ticket as resolved


This would be possible with the 'hours since status changed' enhancement but isn't possible otherwise.


BR


Tom  


mrenaud
Skilled Expert
Forum|alt.badge.img+6
  • Skilled Expert
  • November 27, 2015

We were just about to ask for the same feature. We also use quite a few custom ticket status and currently we have to sort of cheat the Supervisor rules to unreliably do what we need. Thanks!


  • Community Debut
  • December 31, 2015
Yes, we would definitely need a "Hours since status is" and the choice of the status as the parameter...
Thanks,

 


  • Contributor
  • June 13, 2016

We need this as well - supervisor has a good start but needs to add support for custom statuses. In this case we want to send a follow-up email to the requester when the ticket status has been 'waiting on customer' for x hours and the ticket is still open


  • Community Debut
  • August 10, 2016

+1 for Supervisor rules based on hours since custom status updated


If this is implemented, we can use this to create specific ticket reminders without the use of SLA's


  • Community Debut
  • October 26, 2016

+1


  • Community Debut
  • November 28, 2016

+1


Have been looking for a way to do this for a while. The rule that Damion suggested would really unlock a lot of potential.


  • Community Debut
  • November 28, 2016

Automated reminder emails for tickets awaiting responses from requester or third party, should be developed further indeed. This supervisor variable is much needed.

Also, the actions should allow an automatic email to the requester (in case you are waiting for information from him to resolve the ticket) or to the third party to which the ticket has been forwarded (presumably the last person to which the ticket has been forwarded).



This very simple and obvious functionality still hasn't been added after two years of being up here. Adding "hours since" with customized statuses AND allowing more than 1 agent be assigned to a ticket. would resolve more than 1 of the requests being put on these forums.


  • Community Debut
  • January 4, 2017

+1


  • Community Debut
  • January 5, 2017

I am currently using a workaround by using the "hours since assigned" condition on a supervisor rule in combination with two observer rules:

- An observer rule that, on a status change (to a particular status) removes the assigned agent

- A second observer rule that, on the same status change, adds the current actor as assigned agent


For us, this works better than the "hours since agent responded" condition, since that is not always acurate. We do not have any triggers on assignent of an agent, and the agent who changes the status is in 99% of the cases the current assigned agent.


  • Community Debut
  • September 4, 2017

This would be very useful as we use several custom statuses so either an "Hours since XXX status" or "Hours since last action/update" Supervisor condition would help us better manage tickets that are in those statuses.


  • Community Debut
  • November 22, 2017

Yes please, this functionality would be very useful for our setup. 


  • Community Debut
  • April 19, 2018

We would love to use this as well. Our purpose would be more for internal accountability than reaching back out to customers.


It would make our jobs much easier if we had an "Hours since" for Notes added, agent touch, etc. 


Not sure how this is not planned already, people have been requesting this very simple option for 3 years.... it would make many helpdesks easier to maintain...


  • Community Debut
  • June 20, 2018

I'm super interested in this as well! 


  • Community Debut
  • June 28, 2018

 We need this too.


marcus.landgren
Community Debut
Forum|alt.badge.img+3
+1 This is a very common need in most accounts to send out different reminders and create different automatic changes to tickets

  • Community Debut
  • July 18, 2018

+1 on this too, could really use this feature instead of needing to manually handle these


Agreed, work arounds for this tend to obstruct other rules. Please prioritize!



  • Community Debut
  • July 19, 2018

I see this is planned, but has anyone heard any updates on a release? 


  • Community Debut
  • April 11, 2019

We'd like the ability to design a very clean and simple supervisor rule to check time in current status or time since last status change. Very similar to what is discussed above. It would work just like hours since agent/requestor responded, except it looks at how long a ticket has been in the current status. This should also work for custom statuses, or even disregard which status and just focus on time in status. I think we're all looking for a way to increase ticket visibility so nothing slips through the cracks. Our use is case internally escalated tickets (a custom status) should be reviewed every 72 hours.



Please add Hours since status changed. 

This kind of works with with hours since agent responded as the agent "should" have updated the status to waiting for reply at that same time, but there is no guarantee of that and as such we need the ability to have rules run based on when when the status was changed.


  • Community Debut
  • November 4, 2019

Would love an update on this. Seems like a no-brainer feature, especially if it could incorporate business hours.


  • Community Debut
  • January 8, 2020

This feature request is 5 years old and it still hasn't been implemented.  Anybody actually pay attention to these requests?