Can we please understand why this call hung up? Was it is due to a concurrency limit? Concerns over losing business due to these types of call. Call ID: 75a5f8ee-a136-4ab7-902f-c262e1233cf1 Time stamp: At 00:28 the call should have transferred. Instead, the assistant did not transfer, then said the Idle message, and then ended the call.

Based on the information provided, the Idle message followed by call termination suggests a timeout issue. When the assistant plays an Idle message, it's often configured to end the call if there's no further interaction. To troubleshoot:

// Check your idle message configuration
{
  "idleMessages": ["I haven't heard from you..."],
  "idleMessageMaxSpokenCount": 3,
  "idleTimeoutSeconds": 5  // Consider increasing this value
}

For detailed investigation, please share this Call ID with Vapi support to examine the specific logs. Sources: - [Discord post about idle messages triggering call termination](https://discord.com/channels/1211482211119796234/1313293840580612166) - [Discord post about idle message configuration](https://discord.com/channels/1211482211119796234/1344633027925377064)

The call likely hung up due to exceeding the concurrency limit, which may have caused the assistant to fail in transferring the call and instead play the idle message before ending it. To avoid this, check your concurrency usage, consider increasing the limit, and monitor the call logs for any over-concurrency incidents.