Steve Giller Posted February 20, 2017 Posted February 20, 2017 Very simply - 18 (working) hours after resolving the call, it hasn't auto-closed. As far as I can see (see attached) I have the settings correct, is this a glitch or have I missed something?
Dan Munns Posted February 20, 2017 Posted February 20, 2017 @DeadMeatGF You have to put 0s into the unused years, months. days fields. So it should read 00 00 00 16 00 It should work then.
Guest Chaz Posted February 20, 2017 Posted February 20, 2017 Whatever time period you enter a value for, you need to se anything to the right to 0 for the correct time period to be created for the back-end. In your case you just need to add a 0 to minutes and that should sort it. This was raised previously and I'll chase it up internally.
Steve Giller Posted February 20, 2017 Author Posted February 20, 2017 Thanks, nice simple solution, on it now
Victor Posted February 20, 2017 Posted February 20, 2017 @DeadMeatGF let me know if it works because I tried the same functionality over the weekend (using minutes) but it did not work... I thought it might be related to SLC working times bt did not have a chance to test it yet...
Steve Giller Posted February 24, 2017 Author Posted February 24, 2017 Still no closure, I'm afraid - the attached image is from a call that was closed 18 (working) hours ago. In case you can check anything on our instance, the reference for that call is IN00003679
Victor Posted February 24, 2017 Posted February 24, 2017 @DeadMeatGF yeah, the auto closure node is broken ... We working to have it fixed.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now