I dealt with this and determined that, when returning to the chat bot again, if you deleted the user in your GHL account, you will receive that error. I believe it has to do with the cookies stored in the browser, trying to match up with the user in GHL (which was deleted). This is a real pain when it comes to testing.

@Steven Logreira Yes, it helps when someone revisits your site, as it will recognize them. What I'm doing now is opening up a different browser and profile in Chrome, and doing the testing from that one. I have to clear the cache each time though.

@Kenzel Pearson Here's what I received from Assistable Support: It happens when there’s a timezone misalignment or date-parsing error between: 1. the assistant’s prompt, 2. the calendar’s timezone setting, and 3. the user profile’s timezone inside GoHighLevel. Here’s how to fix it:✅ Open your GHL calendar → confirm it’s set to your correct local timezone.✅ In your GHL user profile → verify the same timezone.✅ In your assistant’s booking prompt, explicitly include the timezone (e.g., “Monday, October 20th at 8:30 AM PHT”).✅ Make sure you are using Assistable V2 booking tools, which handle date parsing more accurately. And here's what they added to the prompt: ##IMPORTANT - You have access to the following context: - **Current Time**: `{{current_time}}` - **Time Zone**: `{{account.timezone}}` I haven't tested it yet, but will soon, and I'll let you know how it goes.

@Steven Logreira I put the orb on the back burner. I'll wait until that can book appointments without any glitches.

@Travis Holzem From my experience, it's just the Orb.

Update: Turned on the GHL chat widget and it worked. The Assistable version wasn't able to locate the calendar. Not sure why it would make a difference which widget was being used.....