The webhook of type status-update or end-of-call-report is not sharing the actual duration of the call like startedAt and endedAt field is also coming as null.

Hi @IP_NINJA, I'm an AI assistant for Vapi. While a team member reviews this question, I'll look through relevant sources and see if I can provide suggestions. Please tag @Vapi Support with any follow-up questions.

Also, the cost is coming as zero most of the times.

@IP_NINJA can you share some call_ids in which you got cost zero?

@Sahil Here are some call_ids c0c86261-ac0a-4931-9e99-33abe64d05e7 15ce2d9a-f13f-4373-98e2-be1d06ccbfc8 0a38b8d6-7261-4051-867c-8ae39964dc15 3070bc83-586e-4385-b72a-3105a6e31676

So, I confirmed with my team regarding this, and it is currently stalled due to performance issues. It will be fixed very soon.

Thanks @Sahil . I hope we start getting the cost, start and endedAt fields soon. I have one more question regarding the call transfer. Is there any way I can make the bot stay in the call after transferring the call?

Can you elaborate?

I mean if a call is going on and bot decides to transfer the call to an agent. Then is there any way that we can add the third person in the call via conference instead of dropping the bot from the call.

No, there is no way to do it as of now. But, maybe in future, we can achieve it.

Thanks @Sahil for the explanation.

Glad I could be helpful. Feel free to create a new thread with any new questions you may have.

Was this issue fixed? (startedAt and endedAt fields null in end-of-call-report). Or should we retrieve this data another way now? I don't receive this fields in wehbook call now? I noticed that the webhook post payload changed, for instance for this callId

c5920305-f1cb-492a-a666-50aed0cfd658

, here are the call object I receive in the end-of-call-report webhook payload. I don't have startedAt neither endedAt fields in it anymore.

call: {
      "assistantId": ,
      "createdAt": ,
      "customer": {
        "number": ""
      },
      "id": "c5920305-f1cb-492a-a666-50aed0cfd658",
      "metadata": null,
      "phoneCallProvider": ,
      "phoneCallProviderId": ,
      "phoneNumberId": ,
      "status": "ringing"
    }

We are working on it to fix it.

Ok. For now I am calling the call/{callId} endpoint to retrieve the full details.

Cool.

We are still missing the endedAt and duration portions in the end-of-call-report. Has this issue been fixed?

Nope.

Is there a timeline on a fix for this?

Currently, there is no timeline for it.

You can always get this. This information is available when you pull the call after, not during. When you think about it, how could pull that information while the call is still going? Even if you did it would not be accurate. So just pull the ID like you are doing. https://cdn.discordapp.com/attachments/1229468390981107853/1257955520875331684/Screenshot_2024-07-03_000532.png?ex=668649df&is=6684f85f&hm=5ddc8e3f7af2bf7edd576257bfe9ca38c1c75eecf5f108b4e00b41598e7183e9& https://cdn.discordapp.com/attachments/1229468390981107853/1257955521198030908/Screenshot_2024-07-03_000425.png?ex=668649df&is=6684f85f&hm=6dc9d75d835dec999144c12f0c43c84528749977c2b1c2f7dbc6e12a6ac46882&

That's what I do now indeed. But I don't get your point, It's a end-of-call report so the call is finished. We have the the

endedReason

,

transcript

and everything, we should have this data in the report. And we received these values before something changed on Vapi side which forced me to get the call after.