We updated the default setting to be

turn on the chatbot time and use the fixed time zone of UTC.

Please update your chatbot configuration based on the attached screen according to your time zone.

Hi Meraik,

I believe this is either a setup issue or a misunderstanding with your chatbot, as many other users have been able to use the time function correctly.

Could you please email me the chatbot ID so I can take a look?

Here are a few things to know about how the time function works:

If you're using WhatsApp, Instagram, or Messenger integration, you need to set a fixed time zone, as there's no browser-based time zone available in these channels. The browser time zone setting only applies to the website widget. The fixed time zone works for both the browser and the WhatsApp/Messenger/Instagram integrations, but it will be the same for all users.

Regarding exporting the conversation via an AI Action:

There is no built-in feature for exporting a conversation through an AI Action. I'm not sure what method you're using—it seems like you may have created a custom implementation that hasn’t been configured properly. I’ll need to inspect the chatbot to be sure, so please send us the chatbot ID.

In a chatbot that validates vacation requests based on required advance notice, the bot compares the requested date with an incorrect current date (e.g., October 2023), leading to incorrect validations—even outside AI Actions.

This suggests that the time function is either not enabled or not functioning correctly, and your chatbot is falling back to the model’s default (trained) time. For example, you turned on the browser time and are using the Whatsapp to test the validation action, it will fail because there is no browser with Whatsapp messages.