Can someone elaborate on how excactly this works. If someone leaves a no, how exactly does the agent gets this information.  How is it integrated with agent desktop?

If I may, I'd like to press for some additional detail here.  We're actually working on a custom callback feature like this, and I'm curious about the upcoming solution based on how you describe it.
 
What I'm curious about specifically is the "virtual call", if you will.  Does the VXML Server script allow communication with ICM after the live caller is dropped?  I've long felt that extending the capability of something like the "ReqICMLabel" element could be a HUGE advantage in the CVP solution.  We should be able to launch a "call" into the system, queue it, and deliver to an agent without having to use anything other than signaling (a true "virtual" call - no actual RTP/bearer path).  The desktop integration piece is something that can easily be delivered as a custom solution.
 
Can you elaborate on how the solution operates, and whether it might be something that could be utilized today with custom code, without giving away anything "Cisco proprietary"?
 
Thanks!
 
 - Bill

Thanks Adam -
 
I'll move forward with our current solution as this customer is looking to go into production with UCCE 7.5 and CVP 7.0.  I'll be anxiously awaiting the release notes and other documentation around this new feature when it is available, though!