AI suggests time to schedule, then fails. Timezone issue??

We've been trying to solve an issue for way too long where the AI proposes a time, gets a confirmation from the lead, and then proceeds to tell them that the time is not available.

I'm not sure what's going on here. Here's a screenshot of the conversation. We've noticed this happening on Voice too.

Couple of things I'm noticing from this screenshot:

It proposed a 2pm HST (Hawaii) time, but tried to schedule at 9am HST. Is there some kind of confusion between timezones here? Why would it do that?
Second, the bot should be communicating in the lead's timezones, not subaccount's (HST). We have specific instructions to communicate in the lead's timezone, which it's not applying.
The subaccount's user had blocked off his time from 6am to 8pm this day on his Google Calendar, so the bot should have referenced this and not suggested this day. Is it some kind of syncing issue?

Has anybody else experienced this behavior, and were you able to resolve it?

14 comments