@Kings_big💫 @Shubham Bajaj

Hey Yuko, Thank you for reaching out. Please note that our team does not operate over the weekend. We’ll be back in the office on Monday and will dive straight into your issue then to determine the best way forward. Regards, Shubham Bajaj Solutions Engineer

Hi Yuko, When a call does not end as expected with a "silence timeout" trigger, it usually indicates that the call configuration settings may need review or adjustment. Based on the documentation, here are a few steps you might consider: 1. **Check Timeout Settings**: Ensure that the configured silence timeout is appropriate for the user scenario. Adjusting the

customerJoinTimeoutSeconds

could be beneficial. A higher timeout might prevent premature call terminations due to perceived inactivity. See the [Customer Join Timeout](https://docs.vapi.ai/calls/customer-join-timeout) for more details. 2. **Grant Microphone Access**: If users don't complete the process to grant microphone access, calls can end unexpectedly. Confirm that microphone permissions are properly set before the call starts. 3. **Message Plan Review**: Evaluate the message plan to ensure the idle messages are executed correctly and are not causing unintended call terminations. 4. **Connection and Pipeline Checks**: Make sure there are no disruptions in the connection to Vapi's servers or the AI processing pipeline. Errors in these areas may cause unexpected behavior. Check if any recent changes have been made to your assistant or voice settings. By addressing these areas, you might be able to pinpoint and resolve why the call isn't ending with a silence timeout as intended.