Please review call ID f6f42ef0-664e-401d-b075-89e96ea8854e The call is only 15 seconds long (as seen in the recording) but the system states that it had 4m27sec and I am being charged as such. https://cdn.discordapp.com/attachments/1354847482177257634/1354847482781241344/image.png?ex=67e6c78b&is=67e5760b&hm=068f842025ee58f309b00fcce1fb2ee5f46c290bc7877c88b3e47eb933fc4323&

Hi Jonas! I understand your concern about the discrepancy between the recording duration and what you're being charged for 👀 I'm unable to review your specific call ID or make adjustments to your account. However, I can definitely help explain why there might be a difference between your 15-second recording and the 4m27s system-stated duration. ## Why the Discrepancy Exists There are several technical reasons that could explain this difference: 1. **Stuck or Hung Calls**: According to information I found, calls can sometimes get "stuck in the

in-progress

state even after being hung up," with the ended reason being "Unknown Error." This is one of the most common causes of duration discrepancies. 2. **Call Status Updates**: Vapi updates the call status based on callbacks from Twilio (which has four states: queued, ringing, answered/in-progress, and completed). If the system doesn't receive the proper "completed" status callback, it may continue counting the duration. 3. **Voicemail Detection Issues**: If the call involved voicemail detection, issues with the

machineDetectionSilenceTimeout

parameter could cause the system to record a longer duration than the actual recording. ## How Charges Are Calculated Your charges are affected by this discrepancy because: - **STT (Speech-to-Text)**: Vapi charges $0.05/min for STT, prorated per second. With a system-stated duration of 4m27s, this explains the $0.05 STT charge shown. - **LLM (Language Model)**: LLM charges are based on token usage rather than duration. Your call used 29,954 prompt tokens and 54 completion tokens, but the cost shows as $0.00, suggesting minimal LLM usage during the call. The total cost of $0.31 likely includes the platform fee and other components based on the system-stated duration of 4m27s, not just the 15-second recording duration. Would you like me to provide more details about any specific aspect of how Vapi calculates these charges? Sources:

i cannot find any issues on my side. Please verify why did this happen. 4m27sec is 18x more than the actual call. If the recording was able to detect the end of connection, why didn't the system do the same?

Hey @jonas. You are right that the actual call duration is lesser than what shown in the ended time. I can refund the credits for this call. Let me know which org you want to get them added. The most likely issue with this was the updation could have taken a little longer than expected and that's why it ended up showing as longer call.

9b2f61ea-7bb8-4a92-ba23-af8e9e0bc7f2 But will this happen again? I'm not able to monitor every call .

This issue happens because of network bursts or high traffic. When there's a high volume, it can take time to update the call's actual duration, and you might absorb these discrepancies. Feel free; it won't appear for you again as we're consistently working on expanding our capabilities and network stack.