I wrote a tool to allow our assistant to check calendar availability and schedule meetings. The caller asks the assistant to check to see if Michael is available between 1:00pm and 1:30pm tomorrow. She then calls the tool with the authentication token, the start date and the end date. However what she passes the tool is: start time: 2023-10-04T13:00:00Z end time: 2023-10-04T13:30:00Z As you can see, it looks like she is picking dates from over a year ago? 1) Has anyone else encountered this? I'm wondering if the date/time at the O/S level on the VAPI servers is set wrong? 2) Do you have a good work around? It would be a hack but I could have her call a function to obtain the current date and time.

@Michael P 1) It's quite unusual for the VAPI servers to have an incorrect date/time setting, as these are typically synchronized with time servers to maintain accurate system time. However, if you suspect that the assistant is using outdated timestamps, it would be best to check the system logs or reach out to the support team to confirm the server's date and time settings. Please ask support for more info on this. 2) As a workaround, you could indeed implement a function that retrieves the current date and time to ensure that the assistant is using the correct timestamps when scheduling meetings. This function could then be used to calculate the correct start and end times for the meeting based on the current date. If you'd like, I can assist you with calling such a function or provide guidance on how to implement it. Would you like to proceed with this workaround?

@Vapi Confirmed - call your assistant and ask her what time it is. Without any functions, just a base assistant, if you ask her what today is, she says it's October 21st, 2023.

@Michael P It seems there might be an issue with the base assistant's internal clock or the way it retrieves the current date. If the assistant is reporting the date as October 21st, 2023, and today's actual date is January 1st, 2024, then there is definitely a discrepancy that needs to be addressed. For the time being, as a workaround, you could use a function to obtain the correct current date and time. This would ensure that any operations dependent on the date and time, such as scheduling meetings, would use the accurate information. If you have a function ready to retrieve the current date and time, I can assist you in calling it. Otherwise, I recommend reaching out to the support team to report this issue and get further assistance.

I can confirm, Vapi assistants always get the default date and time wrong

Same issue here, not sure how we're supposed to provide the current date to the assistant through a function call though

bots dont know current time, it just refers to its knowledge cut off (oct 2023). you have to get the current time into your assistant so it is able to refer to it @Michael P

in the VAPI documentation you will find placeholders that you can include in your prompt like {{now}} which will be replaced by the current date and time. There are a few others. read the DEFAULT VARIABLES section https://docs.vapi.ai/assistants/dynamic-variables Use this so that your assistant knows the date and time and the issue will be solved. 🙂

Thanks @Quintus and @User for the help!