Bot mistakes days of the week
# support
r
During the conversation bot properly states date and time (4th january 2025 13:35) but when asked about day of the week says it's Friday and not Saturday. ( Later when I ask him about random days (e.g 12 january) mistakes all of them and not even for just -1 day but the day of the week can be random. In prompt I use standard variable: - Current time: {{"now" | date: "%b %d, %Y, %I:%M %p", "America/Chicago"}} but also tried with just {{now}} - I use GPT 4o mini as a LLM.
v
@rad kruss I'm sorry to hear that you're experiencing issues with the date and time functionality. It seems like there might be a discrepancy in how the date and time are being processed. When using dynamic variables like
{{now}}
, it's important to ensure that the formatting and time zone conversions are handled correctly. For the issue with the day of the week, it's crucial to have the correct date and time settings. If you're using a specific time zone with the
{{now}}
variable, make sure that the formatting string you're using (
"%b %d, %Y, %I:%M %p"
) is compatible with the expected output and that the time zone ("America/Chicago") is correctly set. If you continue to experience issues with the day of the week not matching the date provided, it might be beneficial to double-check the system settings or the code that processes these variables to ensure accuracy. If the problem persists, please ask support for more info on this, as they might need to look into the system's configuration or the underlying code.
You can continue this conversation by mentioning me in the message.
r
@Vapi
v
@rad kruss Please ask support for more info on this.
r
@User
@Shubham Bajaj
j
I also have the same problem and waiting to hear back from support. It’s taking 2024 as the reference and not updating even if you add current year is 2025 in the prompt
c
Hi, I just wrote {{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}} in the system prompt and it worked. Just adjust the timezone according to you and it should work
s
@rad kruss could you share: - The recent call ID - When exactly this happened (the timestamp) This would really help me figure out what went wrong!
r
f26425ee-8ec8-478c-a886-bd5d2d1ccfbd
0:42
Hi Cyber, thanks for checking that, I just tried but the problem still exist
@Shubham Bajaj
s
@rad kruss You can try out the following, the idea is to explicitly pass the Day along with date time to make it work.
Copy code
### Handling Date, Time, and Day  
- Current Date and Time Variables:  
Current date: {{ "now" | date: "%B %d, %Y", "America/Chicago"}}  
Current time: {{ "now" | date: "%I:%M %p", "America/Chicago"}}  
Day of the week: {{ "now" | date: "%A", "America/Chicago"}}  

### Guidelines for Date and Day Handling:  
1. Confirm the Day of the Week:  
   - Always mention the day of the week when proposing or verifying dates.  
2. Check for Weekends and Office Hours:  
   - Ensure meetings are not scheduled on Saturday or Sunday and fit within office hours (8 AM - 5 PM CST, Monday to Friday) based on the prospect’s local timezone.  
3. Relative Date Handling (e.g., Tomorrow/Next Week):  
   - Calculate and verify the weekday for relative dates before confirming.  
4. Final Confirmation Before Booking:  
   - Explicitly repeat the day, date, and time for confirmation before finalizing the booking.
Do Let Me know How it Goes!!
r
After changes bot properly states what day is tomorrow and after tomorrow, but mistakes what day is for example 11 january (it's saturday but Bot state it's thursday)
4cda2bde-e727-4b99-aed7-57364df82048
sorry I see audio wasn't recorded, I don't know why. You can see conversation in the log, mistake starts after 18:18:26:065
@Shubham Bajaj
I added: "5. Always state properly the day of the week when talking about some date. Never give random output. " and it helped partially
but still doesnt work properly
m
Can you check please the prompt {{ now}} ? Im not sure, but it doesnt work anymore for new assistants?
j
@Shubham Bajaj i can confirm this. I’ve used a similar prompt (I’ve another support thread on the same issue which haven’t received any response) and ai kind of understands today and tomorrow properly. That does the job in most cases. But if you keep on probing and start asking questions about how about Jan 11th like mentioned here, ai goes to 2024 Jan 11th and tells the day of the week
r
@jithins @Shubham Bajaj @ML Futures I changed llm from 4o-mini to 4o and now it works perfect, I have tested many llm's and only 4o handles it properly
j
Thanks @rad kruss I changed my time to ISO format and updated the model to 4o and it started to work fine. Thanks for testing out other models as well
s
@ML Futures can you tag me to your #1211483291191083018 ticket.
h
@jithins is it still working for you, mine stopped working!
j
Oh did it. Haven’t checked in a while. Not many inbound calls coming in. Mostly focusing on OB. I’ll update when i check
2 Views