Skip to main content

Currently we are using a supervisor rule which sends an email notification to a requester if they do not respond after five business days, it was created using the recommended method as below;

 

 

The issue is sometimes, usually over weekends, users get caught inbetween the hours since agent responded due to it being based on Business hours.

The scenario is Friday 17:00 (no longer in business hours) comes and the hours since an agent responded is at 38

For the supervisor role above the conditions are met, as its between 37.8 and 38.9, therefore the automation takes action, send an email to the requester.

However because we are no longer in business hours the hours since an agent responded is still at 38, and will be until Monday 09:00

This results in an email reminder being sent out every hour that the rule is ran.

Is there anyway to prevent this other than setting the rule to work on calendar hours?

 

I’m trying to solve the same issue.  I actually started to put in a ticket, then I had a a-ha moment where there can be very small cases that things get stuck as you say above.  There’s no good workaround, however, I think I may try adding a field in the ticket itself, where I would use the automation tools to change to 0 when not in pending, 1 when greater than 24 calendar hours, 2 when greater than 48 calendar hours and 3 when greater than 72 calendar hours.  Then run a scheduled workflow once a business day to process when equals one of the flags. 

 

Honestly, this is a little annoying to do, but I cannot think of any other way to fix this unless they build in better logic.


Reply