Problem Statement:
Currently, when an agent forwards a digital interaction (like an email) to another channel or department, the system behaves differently than a standard requeue. Instead of seamlessly transferring the work, the system leaves the original interaction in an open state and generates a completely new, disconnected interaction for the forwarded item.

Business Impact:
-Agent Confusion & Friction: Agents must perform multi-step manual wrap-ups to close the original interaction, increasing Average Handle Time (AHT).
-Fragmented Journey: Splitting the interaction breaks the historical thread, making it harder for the next agent to see the full context.
-Administrative Burden: Our admins are currently forced to build and maintain custom webhook workarounds to automatically close these dangling interactions.

Desired Behavior:
We want forwarding a digital interaction to mirror the functionality of recategorizing or requeueing. Specifically:
-The interaction is transferred in a single motion.
-The interaction closes automatically for the forwarding agent.
-The original interaction ID is maintained (not duplicated) as it moves to the new destination.