Rufi
01/07/2026, 12:35 PMAI Evy
01/07/2026, 12:35 PMAI Evy
01/07/2026, 12:35 PMdial_failed, dial_no_answer, dial_busy) , they would still appear in call history with those disconnection reasons.
- There may be a display/UI delay between when calls are sent and when they appear in the interface. [(1) ]()
Recommended next steps:
- Share your batch_call_id with Retell support so they can investigate the specific status of those 2 missing calls
- Check if the destination numbers for those 2 calls were valid and reachable
If the issue persists, I'd recommend reaching out via [Contact Sales]() for direct support with your batch call ID.AI Evy
01/07/2026, 12:35 PMAI Evy
01/07/2026, 12:35 PMRufi
01/07/2026, 12:36 PMRufi
01/07/2026, 12:37 PMAI Evy
01/07/2026, 12:37 PMAI Evy
01/07/2026, 12:37 PMcall_status which includes: registered, not_connected, ongoing, ended, error
[(1) ]()
2. Calls stuck in registered state — If the calls are showing in concurrency but not appearing as ongoing, they may be stuck in registered status (call ID issued, starting to make a call) rather than ongoing (call connected and ongoing)
Try this filter to catch all active states:
json
{
"filter_criteria": {
"call_status": ["registered", "ongoing"]
}
}
Recommended next steps:
- Try filtering for registered status in addition to ongoing
- Share your batch_call_id with Retell support — they can investigate why those 2 calls are consuming concurrency but not appearing in the expected call status
If the calls are genuinely stuck, this would require Retell support to investigate on the backend.AI Evy
01/07/2026, 12:37 PMAI Evy
01/07/2026, 12:37 PMRufi
01/07/2026, 12:38 PMAI Evy
01/07/2026, 12:38 PMAI Evy
01/07/2026, 12:38 PMregistered and ongoing statuses, but you still see 2 calls in concurrency, this is a known issue where calls can become stuck in a state that doesn't properly reflect in the API. [(1) ]()
What's happening:
Based on similar reports, calls can sometimes get stuck where the status doesn't change properly — the call may have already ended but the status remains as "ongoing" in the concurrency count.
Unfortunately, there is no API endpoint to force-end a stuck call. Users have reported trying to disconnect the agent from the number and even deleting/re-purchasing the number, but the stuck calls persisted.
Recommended action:
You'll need to contact Retell support directly with your specific call_id values (if you have them from the batch call response) or your batch_call_id. The Retell team can investigate and manually resolve stuck calls on the backend.
In previous cases, Retell confirmed that stuck calls would not be charged.
Check out these potentially useful sources: [List Calls]() , [Contact Sales]()
Would you like me to provide a general answer on how to retrieve call IDs from your batch call initiation response?AI Evy
01/07/2026, 12:38 PMAI Evy
01/07/2026, 12:38 PM