Hi Tobias,
Can you help me understand how you would expect this to work? Callbacks currently get the same wrap-up code as set to the outbound voice conversation that has been placed. When we initially implemented the feature we felt it was not a good idea to have the agent first wrap-up the voice conversation and then have to do the same thing with the Callback object itself. If you can help me understand what exact used case you are looking for in which you believe callbacks need their own wrap-up codes that would be great? Or are you more worried about the fact that you cannot limit the amount of time the agent spend after they have completed a callback?
Thanks,
Jeroen