Please help us investigate this callId: 92441b65-fc5c-4d84-9084-98dd3c3d4ef2 The call looks weird to me, I listen to the audio recording but it is shorter than the call duration. And the call end without seeing any reason. another callId: 0938c45e-34d3-4b3c-8a4c-be57c349f2a6 It is a reason like "customer end the call" which sound weirds, And when I look into the Log tab in VAPI observe, I can see there are still some responses from the Assistant and the customer, but it is not there in the transcription. Thank you very much.

Hi there! 👋 I understand you're seeing some discrepancies with your call logs and audio recordings. While I can't analyze those specific call IDs directly, I can definitely help explain some common reasons for these issues and how you can investigate them further. What I can't help with: I can't access or analyze the specific call logs for the IDs you've provided (92441b65-fc5c-4d84-9084-98dd3c3d4ef2 and 0938c45e-34d3-4b3c-8a4c-be57c349f2a6) to determine exactly what happened in those particular cases. What I can help with: I can explain common reasons for these discrepancies and how to investigate them. ## Why Audio Recordings Might Be Shorter Than Call Duration There are several common reasons for this discrepancy: 1. **Voice Activity Detection (VAD) Settings**: If VAD isn't calibrated correctly, it might miss the beginnings of sentences or entire sections if speech is too quiet, leading to truncated recordings. 2. **Premature Call Termination**: According to [Vapi documentation](https://docs.vapi.ai/calls/call-ended-reason), calls might end prematurely due to: - Reaching maximum allowed duration - Silence timeout - Voicemail detection - Network connectivity issues 3. **Endpointing Issues**: The system might be prematurely detecting the end of user speech, leading to incomplete recordings. 4. **Call Transfer Issues**: Problems during call transfers can lead to the call ending prematurely. ## Discrepancies Between Log Tab and Transcription For your second issue where the Log tab shows responses not present in the transcription, this could be due to: 1. **Transcription Inaccuracies**: Background noise, poor audio quality, or the transcription model's limitations with accents or speech patterns can cause discrepancies. 2. **Issues with Call Transfers and Latency**: Inconsistencies and latency in call transfers can lead to incomplete or inaccurate transcriptions.

Hi there! I see you're trying to get help with those specific call IDs. I've escalated your query to our support team who can directly investigate the call logs for IDs 92441b65-fc5c-4d84-9084-98dd3c3d4ef2 and 0938c45e-34d3-4b3c-8a4c-be57c349f2a6. Unlike me, our support team has direct access to your call logs and can analyze exactly what happened with those specific calls, including why the audio recording is shorter than the call duration and why there are discrepancies between the Log tab and transcription. A support team member will get back to you soon to help resolve these issues. Thanks for your patience! 👍

@Shubham Bajaj sorry I am not sure who should I tag to and I look at the old tickets and find your name. Could you please help or ping any one help?

@Vinh looking into it...

@Shubham Bajaj yeah thank you for looking into it. But there is one weird thing is that the transcription show more than what I can listen in the recording

Hey Vin, What happens is: 1. We get the recording of the human 2. Then it goes to the speech models 3. Then it goes to the LLM models 4. Finally, it goes to the transcription model (it goes to the telephony model any phony system or other) During this process, sometimes if we hang up the call and the audio was passed to the transcription model by then, you might get transcription appended in your final report or you might see it in the logs. That's why you have observed transcription shown more than what you have listened in the call recording.

ok thank you. I will continue monitoring. Thank you for your support.

Marking this ticket as Solved ✅