Hi, I was wondering about the same demand, as we did exactly this in Genesys Engage. We used a process called 'qualified end' in messaging where only customer or timeout where able to end the conversation.
We also disable the 'reply button' for emails, as we did use email as a task carrier only. Also, in order to implement a sanity check for tasks, where a status check towards backend has to be performed, would require to block mark done. As far as I know our latest idea was some tweaking in scripting, but hiding certain buttons (and adding custom) is definitely a good opportunity to improve the AX for tight integrations.
------------------------------
Daniel Possekel
Vattenfall GmbH
------------------------------