Not generally. You'd have to route to a prompt that would play the touch tones that would trigger your takeback and transfer event.
Route-to will bridge the incoming call to another leg of the call.
If you use network routing (say, an overflow to another destination on an all-trunks-busy condition) you'd only have to test the destination for expected wait time or no resources (or something like that), and then goto a line in the vector that says "busy".
That will return a busy indication to the network, and it will seek an alternate destination for it's overflow. Much cheaper in the long run than using T&T. You get a charge associated with each call. Even if you don't transfer that call, you still get a charge for takeback & transfer.
Carpe dialem! (Seize the line!)