Yeah, I dig. :-)
Sounds like what you need is for the tests to do more than just exercising the actions but logging results at the various points. TestComplete/TestExecute can take screen shots, right out/compare database queries, etc. So, rather than having user interaction, it might be more advantageous to have your automation development group write into the automation those various validation tasks that you need to have performed. That way, you can just let it run and then, when it's all done, e-mail the results to you to peruse at your leisure.
Log.Picture is one such action that will log a screen shot.
You can use DBTables and Object check points for checking SQL data and such.
For that matter, the automation developers can write out Log.Message, Log.Warning, etc, types of messages during the tests to write out any results that you need to have recorded for your validation work.
I'd be happy to assist with any of this, for technique and such. I think this would be the way to go rather than even having to monitor the tests with a "Pause" every time a test completes.