Martyn Houghton Posted June 13, 2016 Share Posted June 13, 2016 At the moment you are not able to use the Email option when a request is on hold, but you are able to use the update option. Is this a configurable option, as there are quite often the requirement to generate an email from the request when it is on hold, even if it is to chase up the customer. In SupportWorks you can undertake a Call Update actions and email when the incident is any status other than closed. Cheers Martyn Link to comment Share on other sites More sharing options...
Victor Posted June 13, 2016 Share Posted June 13, 2016 The reason for this is that from a practice perspective, emailing will mean an analyst is doing an action on a call which contradicts with the on-hold status. I know that there is a change that will revamp call statuses to a more usable and meaningful way. Our product specialists will be able to giver you an update on this. I can see that a chase email does not necessarily mean that the analyst is investigating the issue reported in incident or the request made by customer but it would still fall under the rationale. With this in mind perhaps you can achieve the "chase email" via business process to set up tasks that trigger an email when they expire... EDIT: I can also see the argument that updating a call is an action same as emailing which will also contradict with the on hold status and why is one available and the other not... our product specialists and product managers can explain this in bit more detail. Link to comment Share on other sites More sharing options...
James Ainsworth Posted June 13, 2016 Share Posted June 13, 2016 We do have a planned change in our backlog to provide settings that will allow you to control which Action items you want to make available while a request is on hold. This is not scheduled yet but it will be something that we look at in the future. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted June 13, 2016 Author Share Posted June 13, 2016 Victor/James Thanks for the updates. As the incident is on hold there is no current activity to expire, as the previous activity was completed in the workflow which resulted in the request being put on the hold and the business process is suspended - Wait for Request off hold. It is not possible as far as I can see to branch based on whether the request was manually taken off hold or the hold expired, post the suspend node, as there is no concept any more of the status off-hold. Indeed there does appear to be a contradiction between being able to undertake an update but not one you want to email. Hopefully the configuration option will scheduled soon. Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted September 13, 2017 Author Share Posted September 13, 2017 @James Ainsworth Just wondering how the planned change for this is progressing? Cheers Martyn Link to comment Share on other sites More sharing options...
James Ainsworth Posted September 13, 2017 Share Posted September 13, 2017 Hi Martyn, This is near the top of the queue and will with our development team soon. Regards, James Link to comment Share on other sites More sharing options...
James Ainsworth Posted October 9, 2020 Share Posted October 9, 2020 Hi Martyn, I came across this old post and I wanted conclude this with the information on how this is now done. We introduce a Request Settings section within the Admin Tool where each Request Action can be enabled or disabled for use when a request is on-hold. Link to comment Share on other sites More sharing options...
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