Track missed message with timestamp

You wouldn't know if a reader has answered a message as some messages don't require a response. Every reader should always go into the oldest message first which then timestamps the message with a read date/time. What I'm trying to accomplish is to find who isn't dealing with the oldest message in the queue first then for that message count how many times it was missed, who missed it, and what job the invividual dealt with instead.

I've updated my example to show how responses are recorded, but like I say some messages won't have a response but someone is still expected to "read" it to get the message out of the queue.  I'm only interested in the messages "In" for this excercise.  For info, outbound messages don't have a read date/time stamp as we don't track when our external suppliers read our responses.

Expected output: