Our Facilities team use Tasks to make the process of closing calls "on the go" a lot more simple, and this is working very well in testing.
One issue we do have is that (as discussed at the Insights event) you cannot reassign a task, so if, for some reason, a call needs to be reassigned the task must be "failed" and a new one recreated. We have automated the creation part, which occurs when the Request is assigned to an individual (we can't assign to groups or roles as the number of tasks on the list would quickly become unmanageable) and have logic in place so that if a task is "failed" (e.g. the owner is taken ill and has to go home, the request was incorrectly assigned etc.) the process loops back and awaits a new owner.
The problem with this comes when the Requests with the "failed" Tasks are assigned into a Team that includes the original Owner - in this case the Request remembers the Owner and as the call has immediately been assigned recreates a fresh Task and assigns it to the person who's just "failed" it. There are edge cases that prevent the use of "Wait for new owner" because it is technically possible for the call to be reassigned to the original owner, e.g. they have to leave unexpectedly, no-one is available to pick the Request up, and they original Owner is back at work the next day and is reassigned the Request.
What I'd need is either an option to "Unassign" a Request, or an option with the Assign to Team actions to "delete" the owner from the Request.
Is this something that can be added?