Problem Description
When a RingCX agent (Party A) places a manual outbound call to Party B, then adds Party C to create a 3-way conference (Agent + Party B + Party C), if the agent (Party A) disconnects, the entire conference call is dropped for all participants (Party B and Party C).

Expected Behavior
If the agent (Party A) disconnects from a 3-way conference, the call should continue between Party B and Party C. This is expected in standard call conferencing logic where the initiator disconnecting does not necessarily terminate the call for all participants.

Business Impact
Very large customer is in a Proof of Concept (POC) with RingCX. The inability for remaining parties (B and C) to stay connected after the agent (Party A) leaves the call creates significant disruption, especially for logistics workflows that rely on warm transfers or escalated collaboration. It also presents a challenge to adoption, as the behavior is unexpected and reduces confidence in the reliability of RingCX's conferencing feature.