Thiago
04/02/2025, 6:17 AMVapi Support Bot
04/02/2025, 6:18 AMThe current date is {{"now" | date: "%A, %B %d, %Y", "America/New_York"}} and the time is {{"now" | date: "%I:%M %p", "America/New_York"}}.
Make sure to adjust the timezone ("America/New_York" in this example) to match your desired timezone. [Several users have reported](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334271734332784773) this fixed similar issues.
### 2. Switch to GPT-4o
Some users found that switching the model to GPT-4o in combination with the date/time prompt fixed their timezone issues. This might be worth trying if the first step alone doesn't work.
### 3. Check Assistant Configuration
Ensure your assistant ID is correctly set on the phone number and review the debugging artifacts. The issue might be that your assistant is [using a generic configuration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338961731367604284) instead of the specific settings from its dashboard.
### 4. Verify Date Variables and Formats
If you're using external tools like Make.com, ensure that the date variable is dynamic and correctly formatted, and that the date format matches what VAPI expects.
### 5. Check System Timezone Settings
Verify that your system's timezone settings are correctly configured, as this can sometimes affect how datetime values are displayed.
Is there anything specific about your assistant setup that you'd like me to help with further?
Sources:Vapi Support Bot
04/02/2025, 6:18 AMVapi Support Bot
04/02/2025, 6:22 AMThiago
04/02/2025, 6:32 AMVapi Support Bot
04/02/2025, 6:33 AMVapi Support Bot
04/02/2025, 6:33 AMPraveen
04/02/2025, 1:06 PM