I am particularly interested regarding the dynamic value incorporation within workflows, the assistant's understanding of the prompts, the integration of the end-call-report API, and the process for obtaining the call ID directly within workflows.

Hi cloudsteer, You can use dynamic variables and API request nodes in your workflows to access the call ID and manage dynamic values. 1. **Call ID**: Use an API request node to send a request with the call ID at the start of the call. 2. **Dynamic Values**: Use placeholders like

{{variableName}}

in your messages and set values with

assistantOverrides

in your API calls. 3. **End-Call Report**: Add an API request node at the end of the call to send a summary to your endpoint. This setup will help you manage and report on calls effectively.

Hi Parveen Nair, We’re currently trying to use placeholders like {{variableName}} in our messages and are setting values via assistantOverrides in our API calls. This approach works well for most variables. However, we’ve encountered an issue with the {{callId}} placeholder—it doesn’t seem to be working as expected. As a result, we’re unable to send an API request with the call ID at the start of the call. Could you please help us understand how to correctly use {{callId}} in this context, or let us know if there’s an alternative approach?

Hey cloudsteer, 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!

Hi Shubham, Thank you for the transparency and for taking responsibility — it’s genuinely appreciated. I understand how process changes can sometimes have unexpected outcomes. Just wanted to check in and see if there’s any update on the support issues i raised. Looking forward to the improved consistency you noted starting from today. Thanks again, and we appreciate your efforts.

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

i am still waiting for any update on my issue.

Hey, I can help with that. The {{callId}} placeholder should work if it's set up correctly in your API calls. Make sure that the call ID is being passed properly in the request. If it’s still not working, you might want to check if there are any specific requirements or formats needed for that placeholder. If you continue to have issues, let me know, and we can explore alternative approaches together.

actually i want to store the conversation data in my database to store in need call id so, that based on callid i can store the values. but when passing or calling the api it just passind {{callId}} in the parameter not the value..

Hi cloudsteer, To fix the login issue on the mobile app, please check that you're using the right credentials and have a stable internet connection. If that doesn't work, try these steps: 1. Clear the app cache in your device settings. 2. Make sure the app is updated to the latest version. 3. Uninstall and reinstall the app. If you're still having trouble, please provide: - Steps you took before the issue. - Any error messages you see. - Your device model and operating system. This info will help us troubleshoot further. You can also check the [issue reporting guide](https://docs.vapi.ai/issue-reporting) for more tips.