Hi Arjun,
From speaking to appropriate team members, since this is outbound, the first route tried to reach the customer may have failed, producing a call that doesn't connect. When it is tried again on the edge it will show as another call which may succeed. However, there is no way to definitively say thats whats happening in your case. I would suggest opening a ticket with Care
Best Regards,
------------------------------
Ewomazino Onokpise
Software Engineer
------------------------------
Original Message:
Sent: 11-19-2025 05:55
From: ARJUN T P
Subject: Call Participant Connected Time and Multiple Customer Participants in Same Outbound Interaction
Hi,
I was reviewing some interaction details for outbound calls initiated by the agent. In the calls/{{conversationId}} API response, I noticed that two customer participants are appearing for the same call. One of them has a valid connected time, while the other shows the default timestamp 0001-01-01T00:00:00.
Why is the API returning two customer participants for a single interaction, and why is one of them showing a default timestamp? This is causing incorrect customer connected-time values in my system.
Can anyone help me to figure it out?
#PlatformAPI
------------------------------
ARJUN T P
Engineer
------------------------------