I know that after exceeding the concurrent limit, VAPI does not queue up. However, I saw in the API documentation at https://docs.vapi.ai/api-reference/calls/create that there is a schedulePlan field that can be used to set the time for making calls. So, I would like to ask if there is a concurrent limit for this? For example, if the free account's concurrent limit is 10, can I set 100 schedulePlans at the same time to make calls?

Vapi enforces your account's concurrency limit even when using

schedulePlan

to schedule calls. If your free account's concurrent limit is 10, scheduling 100 calls for the same time will not queue the extra calls—only up to 10 can run concurrently, and the rest will not be processed. Here’s a code example for scheduling a call:

json
{
  "assistantId": "assistant-id",
  "phoneNumberId": "phone-number-id",
  "customer": { "number": "+11231231234" },
  "schedulePlan": { "earliestAt": "2025-05-30T00:00:00Z" }
}

For large-scale scheduling, consider upgrading your concurrency limit to avoid dropped calls. [See documentation](https://docs.vapi.ai/calls/outbound-calling) for details. Source: - [Outbound Calling Documentation](https://docs.vapi.ai/calls/outbound-calling)

Hi Awezome, Regarding your concern about creating concurrent sessions or schedules, you can now create campaigns without specifying a

schedulePlan

with the latest updates. This means you can handle campaign setups more flexibly without needing detailed scheduling setups initially. For additional context management in chats, consider using either

previousChatId

for simple chats or

sessionId

for complex, persistent conversations. For more details, you can refer to the [June 26, 2025 changelog](https://docs.vapi.ai/changelog/2025/6/26).