1 of 1 people found this helpful
Just a rough theory but it sounds as if perhaps you could have a bulk action to stop and start the clock based on the date specified? Perhaps you could have a collection on the case process which is called something like "Client Extension Request". Then on this record you could specify the date that you are extending to and have an automatic action stop the clock once this record has been added. Then once the date specified on the "Client Extension Request" record is reached your bulk action will start the clock again. A bit similar to the example in this document:
Someone might have a simpler idea though!
Thanks for your suggestion. It will obviously take me some time to have a look at this, and it may be we just go manually with a stop clock and a manually set reminder in the mean time. In essence, your response lets me know that we can't have the expiry times for the escalations changed without stopping and starting the clock.
The article you directed me too was certainly worth the read, and has opened my eyes to perhaps doing similar things in other processes we have coming up.