Hi Jukka, Thanks for Your explanation. I, personally, totally agree and understand why the "Delete" button is not there anymore. Sadly, for customer service, old habits die hard and they are asking for it 🙂 . I've also made a feature request, but won't be dissapointed, if it won't be taken into work. Nevertheless, coming up with my own hack is difficult, but am slowly getting there. I've also considered and proposed to use either script or Internal notes. I even proposed to send the e-mails into another dummy queue where a custom script would make regular deletions. Too many clicks and too confusing for them 🙂 . The "custom extension" part, could You elaborate on that abit more? What I've currently managed to achieve, is that an Agent accepts the e-mail. In the Extension Area there is an extension with two choices: Mark for deletion Leave alone Mark for deletion - changes a variable in the javascript to <true>. Now agents selects "Mark as Handled". The script checks the variable and the tasks status value. If it's right for it, it waits 3.5sec and sends a DELETE request to RTI. The 3.5sec wait is at the moment the safest time to wait. With that the wrap-up also triggers correctly. Leave alone - just marks the variable as <false> and nothing special happens from there. What I just found from the API documentation that in the ../RI/rti/tasks/{taskId} there is a "key" called values. And it looks like additional data can be added there. Kind regards, Alder
... View more