jab | 2023-04-05 14:11:55 UTC | #1
Why does the conversation metadata sometimes include "connectedTime" in the participant object and sometimes does not?
Here is an example of two conversation Ids from the same customer:
- /api/v2/conversations/c4851042-98c8-4a20-8f7e-10c6dbe197fe
- includes "connectedTime" for each participant
- /api/v2/conversations/4c7ede52-ca37-481d-887c-8febbfee50db
- does not include "connectedTime" for any participant, though includes "startTime" and "endTime"
crespino | 2023-04-07 16:25:20 UTC | #2
Without being able to see any of the Conversation JSON for those calls it is hard to give you a definitive answer, but if they are outbound calls that didn't connect (bad number, endless ringing) then you'll have a startTime and endTime but not a connectedTime. You will only get a connectedTime if the call actually connects.
Note an outbound call that gets an answering machine is likely to show a connectedTime because the call was established on both ends, thus "connected".
system | 2023-05-08 16:25:48 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 19322