Assistance Needed: Call Campaign Stalled and Early...
# support
f
Hello VAPI Support Team, I recently launched a call campaign to 500 numbers under the Ad-Hoc Infra plan, which permits 10 concurrent calls. However, after the first 10 calls finished, the system did not proceed to dial the remaining numbers—it simply stopped. Could you help me understand why this might be happening? Additionally, while reviewing some of the completed calls, I noticed that the AI starts speaking immediately after the “this call may be recorded” message, even before the callee picks up. Could you advise on how to prevent the AI from speaking until the call is actually connected? Thanks for your help! Org: 8fcae760-23cb-4857-a7bc-32a982810e88 One of CallId of early speach: 8fcae760-23cb-4857-a7bc-32a982810e88
c
Hey, thanks for sharing your details. Our team will look into it and get back to you soon with an update. Lopping in @Kyle
f
Any update yet?
c
Hey, Sorry it's taking longer than usual. Our team is looking into it and will get back to you in a few hours.
Hi, your account allows up to 10 calls at the same time. If you try to make an 11th call, it won't go through. This can happen during your campaigns, which last up to one hour. If a call doesn't go through because you've hit the 10-call limit, it will automatically try again once a line is free, and the other calls will be marked as "scheduled." Sometimes, calls may start playing messages earlier than expected. This occurs when your telephony provider sends updates faster than usual. When we receive these updates, we start the call and play the first message right away. This early start usually isn't a problem and can be ignored. However, if it continues to cause issues, I recommend reaching out to your telephony provider for assistance.
f
We’ve recently upgraded to the Agency plan to support up to 50 concurrent calls, but we’re currently facing two key issues: 1. CSV Lead Loading Issue: When we upload a CSV with, say, 500 leads, only about 300 are actually queued for calling. This creates a lot of confusion and manual work trying to track which leads were missed. Can you help us identify the cause and provide a fix? 2. Idle Message Handling in Multilingual Scenarios: Our default script is in Spanish, and a significant portion of our audience speaks Spanish. However, the idle message settings only allow for English responses. To avoid jarring language switches, we’ve set the idle timeout to 10 seconds with no spoken prompt—but this results in the agent silently timing out. Is there a workaround or upcoming feature that would allow us to set idle messages per language? Thanks in advance—we appreciate your support on this!
c
Hey Fiwa, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!
f
Thank you. I;m trying to use patch request to update the idle message to the conversation language but it's not working I have set it up The patch request is returning error in n8n Here's my setup Method: Patch URL: https://api.vapi.ai/call/:id Input: { "customers": { "assistantOverrides": { "messagePlan": { "idleMessages": {{ JSON.stringify($json.idleMessages) }}, "idleTimeoutSeconds": 10, "idleMessageMaxSpokenCount": 5, "idleMessageResetCountOnUserSpeechEnabled": true } } } } Output { "customers": { "assistantOverrides": { "messagePlan": { "idleMessages": ["¿Sigues ahí?","¿Aún estás conmigo?","Hola - ¿sigues en la línea?","¿Seguimos conectados?","Solo verificando si me escuchas"], "idleTimeoutSeconds": 10, "idleMessageMaxSpokenCount": 5, "idleMessageResetCountOnUserSpeechEnabled": true } } } } ERROR MESSAGE Error code 400 Full message 400 - "{\"message\":[\"property customers should not exist\"],\"error\":\"Bad Request\",\"statusCode\":400}" Request { "body": { "customers": { "assistantOverrides": { "messagePlan": { "idleMessages": [ "¿Sigues ahí?", "¿Aún estás conmigo?", "Hola - ¿sigues en la línea?", "¿Seguimos conectados?", "Solo verificando si me escuchas" ], "idleTimeoutSeconds": 10, "idleMessageMaxSpokenCount": 5, "idleMessageResetCountOnUserSpeechEnabled": true } } } }, "headers": { "content-type": "application/json", "Authorization": "**hidden**", "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7" }, "method": "PATCH", "uri": "https://api.vapi.ai/call/0d840734-6fd6-48f0-aac5-bfe4079878b4", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "followAllRedirects": true, "timeout": 300000, "encoding": null, "json": false, "useStream": true }
@Shubham Bajaj @User I can't seem to reach you personally
c
Hey Fiwa, I'll check in with our team and update you soon.
f
okay, i'm waiting
c
Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team
f
How do you know accounts that has over 1000minutes/month.. is there a support system other than discord? pls share
c
Hey, I see you have a couple of issues. For the CSV upload, it sounds like there’s a limit on how many leads are being processed. I’ll look into why only 300 are queued and see if we can find a solution for the missed leads. Regarding the multilingual idle message, I understand the importance of supporting your Spanish-speaking audience. I’ll check on the possibility of enabling idle messages in multiple languages and get back to you with any updates. Let me know if there's anything else you need in the meantime.
f
Any update on these so far?
c
There are some updates to the platform that could resolve your issue with call queueing. Please run some tests with the most recent update and let us know if you are encountering any issues
3 Views