Rakshit Kalra
02/28/2026, 5:09 PMAI Evy
02/28/2026, 5:09 PMAI Evy
02/28/2026, 5:09 PMcall_d3c729a18b83f4093868bad46ae, I recommend:
1. Check post-call analysis data - This can provide insights into what happened during the call, including call summary and transcript details [(1) ]() [(2) ]()
2. Review webhook events - The call_ended webhook should contain disconnection reason information that may help identify the cause [(3) ]()
3. Consider latency-related configurations - Some users have reported latency issues that can be addressed by changing to a faster LLM or TTS, or optimizing turn-taking model settings [(4) ]()
For this specific call issue where you need direct support and visibility into what happened, I'd suggest reaching out through these channels:
- Visit [Documentation]()
- Visit [Hire certified Retell partner]()
Would you like a general answer based on common causes of agent unresponsiveness, or would you prefer to contact support directly for investigation of this specific call ID?AI Evy
02/28/2026, 5:09 PMAI Evy
02/28/2026, 5:09 PMRakshit Kalra
02/28/2026, 5:10 PMAI Evy
02/28/2026, 5:10 PMAI Evy
02/28/2026, 5:10 PMcall_d3c729a18b83f4093868bad46ae) , you can reach out through these channels:
- **Contact Sales/Support**: [) [(1) ]()
- **Discord**: [) [(2) ]()
- **GitHub**: [)
When reaching out, include your call ID and details about the issue (agent stopped responding, user waited 1.5+ minutes, no errors in logs) so the team can investigate the specific call.AI Evy
02/28/2026, 5:10 PMAI Evy
02/28/2026, 5:10 PM