The order in participants array

Hi

for inbound call, I found that most of time, the purpose of customer was the first children in participants array, but for sometimes the purpose of customer could be the second children in participants array.
how the order was defined in participants array ?

Hi @chengcheng

It's best not to rely on the participant array for chronological order. For example, participants can be involved at the same time. Instead, refer to the segmentStart/segmentEnd fields to understand the periods of involvement for each participant.

Hi Jacobshaw

thanks for your reply.
1, I found that the first children of one call was IVR purpose for inbound call, is that strange ?
2, I would like to get the value of "account" and "password" from customer's input which was set by "Set Participant Data" in inbound call flow and secure flow, the best way was that find the "account" and "password" in attributes from purpose=="customer" , right ? the input data by customer always exist in customer purpose, right ?
3, is there any flag which can represent transfer call or is there any way we can use to check whether this call is transferred or not ?

Regards,
Zhang Chengcheng

Hi Jacobshaw

I found an very strange thing that participate order in notification which subscribe "v2.users.{id}.conversations" is different from API : /api/v2/conversations/{conversationId} for the same conversation, why they are different ?

what I mean is that the first children of participate array was IVR purpose if I use API : /api/v2/conversations/{conversationId}.
but the first children of participate array was customer purpose if I use notification API which subscribe "v2.users.{id}.conversations" for the same conversation.

now we are using notification API which subscribed "v2.users.{id}.conversations" to get the value of attributes from the first children in participate array.

it seems work very well now.

Regards,
Zhang Chengcheng

The order of participants is usually in chronological order, but they are in fact not sorted and clients should not infer any meaning from the order of the participants. If you wish you use them in a particular order, you must sort the participant list yourself, probably by the participant's segment's start time.

no

Participant attributes set by Architect will be set on the customer participant.

No. This is inferred from the participant segments.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.