​ To learn more, see the sources I considered: [[1] Create Batch Call](https://docs.retellai.com/api-references/create-batch-call) [[2] API Documentation Error for Batch Calling](https://discord.com/channels/1186424376300679209/1451330558679584871) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer The

reserved_concurrency

parameter reserves a number of concurrency slots for all other calls that are not triggered by batch calls, such as inbound calls. [(1) ]() For example, if you set

reserved_concurrency

to 5, then 5 concurrency slots from your total pool will be reserved for non-batch calls (like inbound calls) , and the remaining concurrency will be available for the batch call processing. [(2) ]() This ensures that your batch calling operations don't consume all your available concurrency, leaving room for other call types to still be handled. [(1) ]()

Thanks for the follow-up, @K Rudy. I'll get back to you soon.

### Answer The available documentation doesn't explicitly clarify whether

reserved_concurrency

applies globally across all batch calls or only to the specific batch call being configured. [(1) ]() Based on the parameter being set per batch call request, it appears to be configured on a per-batch basis. However, I don't have explicit documentation confirming whether multiple concurrent batch calls share or independently manage this reservation. For a definitive answer on this behavior, I'd recommend: - Checking out: [Create Batch Call]() - Reaching out via [Contact Sales]() Would you like me to try providing a general answer based on typical concurrency management patterns?

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer The available documentation doesn't explicitly describe what happens when you delete a scheduled batch call before it runs, or when you delete an ongoing batch call mid-execution. What the documentation does cover: - Planned batch calls are scheduled for a future time and cannot be edited once scheduled. [(1) ]() - Ongoing batch calls are currently in progress, with calls initiated as concurrency slots become available. - There is a "Stop batch call controls" feature mentioned in the changelog. [(2) ]() However, the specific behavior of deleting a batch (versus stopping it) and whether deletion cancels pending/running calls is not documented in the available sources. For a definitive answer on deletion behavior, I'd recommend: - Checking out: [Create Batch calls]() - Reaching out via [Contact Sales]() Would you like me to try providing a general answer based on typical batch processing patterns?

​ To learn more, see the sources I considered: [[1] Create Batch calls](https://docs.retellai.com/deploy/make-batch-call) [[2] Platform Changelogs | Retell AI](https://www.retellai.com/changelog) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer The "Stop batch call controls" feature is mentioned in the changelog as one of the recent improvements. [(1) ]() [(2) ]() However, the available sources don't specify the exact location or UI path for accessing this control within the dashboard. The changelog only confirms the feature exists as part of recent platform updates. [(1) ]() For the specific location of this control, I'd recommend: - Checking out: [Platform Changelogs | Retell AI]() - Reaching out via [Contact Sales]() Would you like me to try providing a general answer based on typical batch management UI patterns?

​ To learn more, see the sources I considered: [[1] Agent transfer, MCP Client, Static IP and more](https://www.retellai.com/changelog/agent-transfer-mcp-client) [[2] Platform Changelogs | Retell AI](https://www.retellai.com/changelog) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.