Hi Ragheb,
I reviewed the current CX Cloud Voice documentation, particularly the VoiceCall field mapping, VendorCallKey behavior, and the documented handling of transfers/multiple call participants.
There is one important architectural point:
A Genesys Cloud Conversation ID is not necessarily a 1:1 identifier for a Salesforce VoiceCall record.
Genesys explicitly documents that multiple Salesforce VoiceCall records can belong to the same Genesys conversation.
For example, when a call is transferred, the current VoiceCall is completed and another VoiceCall record is created to track the transferred call. Salesforce provides PreviousCallId and NextCallId fields to link those VoiceCall records.
The VendorCallKey also reflects this model.
For VoiceCall records belonging to the same Genesys conversation, the VendorCallKey contains:
<record/leg GUID>:<Genesys Conversation ID>:<call type>
The first GUID differentiates the VoiceCall records, while the second GUID remains the Genesys Cloud Conversation ID.
So seeing:
VoiceCall A → VendorCallKey A → Conversation XYZ
and:
VoiceCall B → VendorCallKey B → Conversation XYZ
is not inherently invalid. The Genesys Conversation ID identifies the overall Genesys conversation, while the VendorCallKey uniquely identifies the Salesforce-side call record/call context.
That said, I would be careful about calling your exact scenario "expected behavior" without qualification.
The Genesys documentation explicitly describes creation of additional VoiceCall records for transfers and multiple call legs/participants, but I have not found documentation that specifically states:
Agent accepts → interaction returns to queue → same conversation is re-routed → new VoiceCall must be created
as a documented requeue behavior.
So I would investigate what actually happens to the first agent participant/session.
If Agent A's accepted participant/session is effectively ended and Genesys subsequently creates a new agent participant/session for Agent B, then a second VoiceCall is consistent with the VoiceCall model documented for multiple call legs within the same conversation.
I would check the two VoiceCall records for:
-
UserId
-
CallAcceptDateTime
-
CallEndDateTime
-
CallDisposition
-
PreviousCallId
-
NextCallId
-
VendorCallKey
and compare those timestamps with the Genesys conversation participant/session timeline.
That will tell you whether Salesforce is representing two distinct agent call legs rather than duplicating the same leg.
The documented VendorCallKey behavior is particularly useful here: different first GUIDs with the same Genesys Conversation ID indicate distinct VoiceCall records associated with the same Genesys conversation.
My conclusion would therefore be:
Multiple VoiceCall records for one Genesys Conversation ID are supported and documented.
However:
I would not state that a new VoiceCall after an accepted interaction is returned to queue is explicitly documented as expected behavior.
If this is occurring because of an abnormal agent-side condition - for example, the agent accepts but the media/session fails and the interaction is subsequently returned to queue - I would treat the reason for that requeue as the primary issue and validate it separately.
If you need Genesys to confirm whether this specific post-accept requeue scenario should create a second VoiceCall, I would enable CX Cloud server-side logging, reproduce it once, capture the Conversation ID and both VoiceCall/VendorCallKey values, and open a Care case. That would allow Genesys to correlate the participant sessions with the VoiceCall creation events.
------------------------------
Gabriel
NA
------------------------------