Automated callback blueprint... multiple conversations?

Hi guys, not strictly a developer question but I'm asking here in case someone has an idea. I've deployed the Automated Callback blueprint. It works great.. except for the fact that we end up with 3 distinct conversation Id being created - one for the original inbound, one for the "parked" call in the workbin queue and then one for the eventual outbound call made from the agentless campaign.

Is there any way of stitching some of those together, or perhaps some API that can "merge" them into a single conversation from an Analytics perspective?