Flow for automatic closing On Hold Incident

AdamUMC
Giga Guru

Hi there,

I'm trying to create a flow with the "Flow Designer", that automatically closes Incidents that are for a 6 days On Hold with reason "Awaiting Caller". 

I managed to setup up the following configuration (in order):
1.) TRIGGER AT INCIDENT where (Incident state changes to ON HOLD, and State changes to ON HOLD, and On hold reason changes to AWAITING CALLER, and checkbox for automatical closing changes to true).
2.) UPDATE AT INCIDENT RECORD: with work note and message about checkbox checked / automatic closing activated.
3.) TIMER: For flow delay of 3 days.
3.) UPDATE AT INCIDENT RECORD: Sends reminder to the Caller by adding a new Additional Comment.
4.) TIMER: For flow delay of 3 days (total 6 days).
5.) UPDATE AT INCIDENT RECORD: Closes the Incident and sends a Resolution Note.

This flow does work in a way, but it does not stop after receiving an answer from the Caller in the form of a new Additional Comment. It continues to work and closes Incidents which got response and should not have been closed but remain open. Only responseless Incidents should become automatically closed.

Several Business rules control the Incident State, State, On Hold Reason and checkbox value after updating or re-opening an Incident. Still this problem keeps happening, which says me the problem lays in the flow.

The question is where and how to solve this? Is it even possible? The hardest part is to implement the required waiting time (expressed in days) + meantime checks for new additional comments.

If anyone has ideas, I would appreciate. Thanks!

1 ACCEPTED SOLUTION

Josh Pirozzi
Kilo Sage

Hi @AdamUMC , 

 

We worked on this and experienced similar issues. How we got it to work is:

Trigger: Incident Updated where State = On-Hold and (We added a field on our Incident Form for 'On-Hold Reason') On-Hold Reason = Awaiting Caller

 

Actions:

See screenshot(s) for Flow Details

 

 

Hope this helps!

- Josh

 

View solution in original post

8 REPLIES 8

Josh Pirozzi
Kilo Sage

Hi @AdamUMC , 

 

We worked on this and experienced similar issues. How we got it to work is:

Trigger: Incident Updated where State = On-Hold and (We added a field on our Incident Form for 'On-Hold Reason') On-Hold Reason = Awaiting Caller

 

Actions:

See screenshot(s) for Flow Details

 

 

Hope this helps!

- Josh

 

Hi @Josh Pirozzi I have a similar request, where I want tickets that are on hold awaiting caller and priority is 2 or 3 to be resolved if not updated in 7 days. I'm filling in for our SN designer who is on extended leave and I dont have much experience with flow designer (lots of Youtube watching and Im still struggling). Im having trouble understanding what I need to input for Record and Conditions- do I need to script something?? (AutoResolve1 reference) 

 

I think this sentence is throwing me off but do I need to enter the conditions again? 

DEESN_0-1705430736434.png

 

 

Any help/explanations appreciated! This will be a big win for the team to avoid manually resolving on hold tickets where we never hear from the caller! 

Hi @DEESN ,

I'm not sure if you have it set above the screenshot provided, but I'd recommend:

  1. Wait for condition - Set to wait for XX hours (equaling 7 days)
  2. If Statement (Screenshot you've provided) 
    1. Condition 1:
      1. Priority is 2
      2. State is On Hold
      3. On Hold State is Awaiting Caller
    2. Condition 2:
      1. Priority is 3
      2. State is On Hold
      3. On Hold State is Awaiting Caller
  3. Update Record Step:
    1. State to Resolved
    2. Close Code to Not Solved (Abandoned)
    3. Resolution Notes to 'Due to lack of response from caller, this Incident has been closed.'
    4. Work Notes to 'Based on the lack of response for 7 days and lower priority of this incident, it has been closed.'

Hope this helps point you in the direction you're looking for!

 

-Josh

AdamUMC
Giga Guru

Thanks @Josh Pirozzi !

Still I have one problem:

I want to stop the timer as soon as I get an Additional Comment from the Caller of the Incident.
I tried serveral things, "Lookup Record", etc. and tried to build "Updated By Changes To Caller" or "Additional Comment made by Caller" or something slightly, but I cannot manage to create something like that.