Taking action in SQL Server PER-Record - is it possible?

Dear Experts,

I am making a marketing application which will allow the marketer to call a list of contacts who meet the criteria setup by the marketing manager. The manager can setup multiple queues for each marketing user.  The marketing user should start calling from the queue which has the highest priority, and as it runs out, they should keep moving down the list of queues assigned to him.  I have everything working, except for the Stored procedure which determines WHICH contact to call.  It should have one input parameter which is @UserID and should return one parameter, which is @ContactID

For example, user 104 logs in and requests a contact to call.  What *Should* happen is the stored procedure looks in the [AppMarketing].QueuesUsers table to determine which queue has the highest priority assigned to this user. Lets say the following information is returned from the QueuesUsers table for user 104:

FK_User_ID  FK_Queue_ID   Priority
------------------------------------------
104               2000                 1
104               2001                 2
104               2002                 3
etc...

First, the procedure should pull the FK_Queue_ID with the highest priority (lowest number in the priority field) and then determine if this queue has any contacts in the buffer. If there is a contact in the buffer, it should update QueuesBuffer.FK_LockedBy_User_ID and return the ContactID of the record we just locked... However, a few things could come into play, and this is where I Have the problem...

If there are no records in the buffer (Queues.CurrentBufferSize = 0) AND (LastQueryRun > 1 hour ago) THEN we need to execute [AppMarketing].INS_PreloadQueueBuffer to load the buffer.  This stored procedure will load 15 contacts into the buffer for this queue AND SET LastQueryRun = GetUtcNow(). After doing this, we need to check this Queue record (again - because it just changed) to see if it has any available records in the buffer.  If it does, then return one like stated above.  However, if there are no records, then we go to the next queue and do the same thing...  Phew...  Next time the marketer requests a contact it should skip over this queue because the buffer is empty and the LastQueryRun < 1 hour ago.  This ensures we don't do a lot of processing and select statements on ten different tables when we don't need to.

------------------------------------------------
Three fields have importance in the Queues table:
1. LastQueryRun - this is the last time the stored procedure [AppMarketing].INS_PreloadQueueBuffer was executed.
2. CurrentPoolSize - This is the integer count of all of the contacts meeting the criteria for the Queue.
3. CurrentBufferSize - this is a tinyint count of all of the contacts related to this queue in the QueuesBuffer table.  It is updated via a trigger and is always accurate.
------------------------------------------------

For a visual layout of what I am talking about, please view this screenshot:

http://75.33.104.230/public/db_queues.png

I hope this makes sense - I have been trying to do it for a few days but I don't know if it is even possible.  Since SQL server sends an entire result set I can't work with each individual record, as I could in C# with say, a DataSet.  PLease help!  

Thanks in advance,

StankStank