Subject: Concerns About VAPI’s Reliability and Support Structure Hi everyone, I’ve been encountering significant issues with VAPI, particularly with handling the current date reliably. While it’s possible to get the correct date using a single-line system prompt like: Pay attention to the current date: {{ “now” | date: “%b %d, %Y, %I:%M %p”, “Europe/Amsterdam” }} ...things start breaking down as soon as the prompt gets slightly more complex. Despite spending hours troubleshooting, I haven’t found a solution that works consistently beyond basic one-liners. This seems like a fundamental issue for a system designed to handle dynamic and real-world integrations. I’m curious if others are facing similar problems or if there are any workarounds that I might have missed. Additionally, I’ve found the support response times to be less than ideal. While I understand it’s the holiday season, reliable support for critical issues is crucial, especially for a platform with significant backing. These challenges raise questions about the reliability of VAPI for building robust services or businesses. I’d love to see improvements in: Reliable handling of dynamic variables, such as dates. Clearer documentation or best practices for more complex use cases. Faster support response times, particularly for critical or blocking issues. I appreciate the innovation behind VAPI, and I see its potential. But at the moment, it feels difficult to deliver something dependable to clients, which is critical for confidence in the platform. Is the team aware of these issues, and are there plans to address them? I’m looking forward to any insights or solutions from the community or the team.