Hello, We are developing an automated platform for making mass calls with VAPI. When using the call scheduling parameters, VAPI confirms that the calls are scheduled and displays them as "Scheduled" in the VAPI-OBSERVE-Call Logs dashboard, but the call never actually goes through. This doesn't happen with calls that are queued immediately (without the schedulePlan parameter). Example CallID: ee98bd42-9c14-4e40-af16-1df90480d6a2 orgID: a2bdd225-c1d8-477a-b8d6-a70478739989 https://cdn.discordapp.com/attachments/1358071340267208864/1358071340795564204/example.png?ex=67f281ff&is=67f1307f&hm=7523877694740f694cc4887be884d851ca41968ed805b8f157c137a89548d0fb&

Hi there! 👋 I see you're having trouble with scheduled calls not being carried out in VAPI. I'm unable to determine the exact cause of why your scheduled calls aren't going through despite showing as "Scheduled" in the dashboard. However, I can help with some troubleshooting steps based on similar issues others have experienced. Here are some potential causes and troubleshooting steps for your scheduled calls issue: ## Potential Causes 1. **Timezone Issues**: There might be discrepancies in how timezones are handled when scheduling calls. According to [information I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1275993578950103141), it's important to handle time-sensitive actions like booking appointments in the user's local timezone to reduce confusion. 2. **JSON Response Format**: VAPI might have difficulty scheduling calls if the JSON response format is incorrect. According to [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1327481613004701779), VAPI might ignore the response if the JSON format is incorrect, particularly the structure of the "result" and timeslot information. 3. **Date and Time Formatting**: Issues with date variables and time formatting can cause problems when scheduling calls with VAPI. According to [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1325856450391834817), problems can arise if the correct time is not passed to VAPI due to incorrect date and time formatting. 4. **Telephony Connection Issues**: In some cases, the telephony might not respond or connect, resulting in the call being dropped. One log showed "Call Waited 300s But Transport Never Connected," indicating a potential issue with the telephony connection according to [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333747605628391434). ## Troubleshooting Steps

Message marked as helpful by @ZebazM! 🎉

It seems it is not a timezone issue because the VAPI's confirmation webhook confirms the scheduled time (considering the timezone), and it is correct. It is not a JSON response format because I'm receiving the schedule confirmation, but the actual call never happen. Connection issues are low probable cause I've waited more than 48 hours and the call never goes through sileceTimeoutSeconds, responseDelaySeconds, and other call settings are not the issue, because at the very least the call would be made. endCallFunctionEnabled is enabled The webhook informations is correct, otherwise I wouldn't receive the confirmation response

Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.

Hi. Unfortunatelly It is still happening. This is the VAPI response: {"id":"d4a1190d-dca4-4526-8d2e-842edce924a7","assistantId":"9e905ac8-5415-49cc-b245-f653c455e861","phoneNumberId":"eea42042-701d-4bd0-aeee-6a1deb815ea5","type":"outboundPhoneCall","createdAt":"2025-04-06T15:14:09.846Z","updatedAt":"2025-04-06T15:14:09.846Z","orgId":"a2bdd225-c1d8-477a-b8d6-a70478739989","cost":0,"customer":{"number":"+56986404033"},"status":"scheduled","assistantOverrides":{"variableValues":{"telco":"V.T.R.","todays_date":"4 de abril del 2025","agente_genero":"ejecutiva","agente_nombre":"Maria Paula","customer_name":"Sebastian Marin","customer_amount":"29990","customer_address":"Lastarria 104","customer_deadline":"Abril 4 del 2025","customer_deadline_day":"Viernes"}},"schedulePlan":{"earliestAt":"2025-04-06T15:15:00.000Z"}} However call never happen. This issue only occurs with scheduled calls. If I don't use the "schedulePlan" parameter, the call completes successfully.

Hey ZebazM, let me check with the team why the schedule call at 3 pm wasn't triggered, and I'll get back to you.

@Shubham Bajaj same issue here 5f412024-ee3d-4828-920d-4e63738ac467. The call was on 1pm berlin time but wasnt executed. It also showed me "scheduled" as status

Do you have any update?

Hey, this feature is still under development, and it will take some time to roll it out completely. Until then, you have to manage batch calling or call scheduling by yourself.