Anyone else having a similar problem? We're constantly getting this error with the dates the AI ​​is entering. I've tried setting the temperature to 0, and sometimes I even enter the current year's dates in the prompt, but it still doesn't work. I don't know what to do anymore. Some of my clients are already frustrated. Any ideas?

The AI gives wrong dates, for example, in this conversation: Great, Claudia! We can schedule your virtual assessment for Saturday, January 18th at 12:00 noon or Tuesday, January 22nd at 3:00 pm. Which of these options sounds better to you? 22nd is not tuesday, and in the calendar in GHL, the tuesday isn't even available

How do you guys get around the agent using the merger field name outloud? My previous logic is not working very well: 1. Calling tool silently 2. Adding logic for custom fields that do not resolve, to ignore them - but for some reason it does not detect that the information in the custom field and sometimes would just use the name of it.

Did you guys turn off voice agents and work only with text? Or how do you handle client dissatisfaction caused by the technology—and how much longer can you realistically push it?

We've set up an automation inside of GHL with the "Make AI Call" trigger. We've put the assistants ID, but when adding a contact to the automation it's not making any call in assistable. We have imported a phone number successfully into assistable, but inside of the call logs in assistable no call shown. In the automation in GHL it says "Action execution successfully for assistant_call with version 2.7". What is missing/wrong here?