When creating a journey, it would be extremely beneficial to have the ability to designate one ticket as the parent ticket and automatically associate other tickets created within the same phase or subsequent phases as child tickets.
Our team uses a round-robin assignment process for support tickets. Currently, when a journey generates a second ticket, it enters the round-robin queue and is often assigned to a different agent than the one who received the original ticket. This can lead to fragmented ownership and additional coordination between team members.
It would be helpful if all tickets generated as part of the same journey could inherit the assignment of the parent ticket, ensuring they are routed to the same agent who initially received the request. This would improve continuity, streamline communication, and provide a more consistent experience when managing related tasks throughout the lifecycle of the journey.
