i am trying to understand why the end call report doesn't always have the assistant id. sometimes it is available inside the call.assistantId property but there are times when it is inside the assistant.parentId property in the json

@Raju The presence of the

assistantId

in different properties within the end call report can depend on the specific call flow or how the call was handled. If the

assistantId

is found in the

call.assistantId

property, it typically means that the assistant was directly involved in the call. However, if the

assistantId

is located in the

assistant.parentId

property, it may indicate that the call was handled by a child assistant or a sub-process where the

parentId

refers to the original assistant that initiated the process. If you're consistently seeing discrepancies in where the

assistantId

is located in the end call reports, it might be worth looking into the call handling logic to ensure that the

assistantId

is being recorded in a consistent manner. If this doesn't resolve your issue or if you need more detailed information, please ask support for more info on this.

Hey @Raju To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) This would really help me figure out what went wrong!

@Shubham Bajaj for now i just had to do with checking for two fields

@Raju sorry I didn't understood can you please rephrase it?

I am checking for two properties so if one object doesnt have the assistant id another one does so not an issue

When you use persistent assistant (through the dashboard), you will get the assistant ID; otherwise, you will not get it. You will get the complete assistant data.

oh thanks man. no wonder the values were different

@Raju @Shubham Bajaj just ran into this myself - I've never seen the

assistant.parentId

property being used to pass down the id, only

assistant.id

Are there any other properties on the end-of-call-report besides those two that I should expect to come down with the assistant's id?