The comments on that video are comedy gold btw, and it clearly needs some work, but still cool.

@Halie Bot I will help any way I can.

@Vicente Vercellino The simplest solution is to just remove custom fields unfortunately if you want to be 100% sure it never makes that mistake. But I also tried the following which worked: ## Contact Fields If the value includes "contact." always refer to the key in a casual and natural way when referencing a contact field. This is because you do not have this information present and should not mention it in conversation. If the value includes "contact." you do not have the correct value and the value should remain unknown to the user at all costs. If the user asks for specific information from the value and the value includes "contact." always let the user know that for security purposes you are unable to provide that information since they are calling from a different phone number than the one on file. { "name": "{{contact.name}}", "first_name": "{{contact.first_name}}", "last_name": "{{contact.last_name}}", "call_in_date": "{{contact.call_in_date}}", "lender": "{{contact.lender}}", "mortgage_amount": "{{contact.mortgage_amount}}", "sale_date": "{{contact.sale_date}}", "address1": "{{contact.address1}}", "phone": "{{contact.phone}}" } Field Descriptions: "first_name": "last_name": "name": "lender": "mortgage_amount": "mortgage" "sale_date": "address1": "call_in_date": "phone": In Task 1 under the introduction: - #If the user's name includes "Guest", "Caller", or "Orb", always assume you do not have the user's name and always ask who you are speaking with. -- ##Example Response: "Hello, my name is Lillian. Who do I have the pleasure of speaking with?"

@Vicente Vercellino Anytime! Hope it helps 🙏🏻

@Jorden Williams @Alexa Briggs @Vicente Vercellino @Timo Weber @Simeon Krastev @Robert Boydston Sorry for the late reply, I've been working on some massive rollouts and new TV ad campaigns. It was working amazing with Haiku 4.5 and Andromeda from Rime when I tested it yesterday and I really liked Emily and Grace. That being said... I just did a demo for a massive group live in Zoom of about 60 brokers and the voice on it was super slow... and it also appears that the AI is rambling through tasks again.... Egg on my face... 😔 When it worked though, man was it good. Call examples: Example 1: Model: Haiku 4.5 Voice: (Rime) Andromeda / Default Voice Engine / Multi-Lingual Processor Voice speed 1.55x call_87f897b8-0d95-4e2b-8313-03f849c4dcb8 Example 2: Model: Haiku 4.5 Voice: (Rime) Andromeda / Default Voice Engine / Multi-Lingual Processor Voice speed 1.55x call_a7c7798a-bb6b-423a-934a-4c73e3db5100 Example 3: Model: Haiku 4.5 Voice: (Rime) Andromeda / Default Voice Engine / Multi-Lingual Processor Voice speed 1.0x call_c2645ba8-1b1d-4416-8e20-44f21c27227b Example 4: Rambling call: Model: Haiku 4.5 Voice: Grace / Default Voice Engine / Multi-Lingual Processor Voice speed 1.55x call_57f56571-2dcc-46f1-85c9-5b1cef48e484

@Alexa Briggs Yup. I am also experiencing that as well. It happened in a live presentation where I was demoing the new great voices for about 60 brokers. Super embarrassing.

Curious about this as well. I've been on 4o for ages, but thinking about trying some other models.

@Cemre Sancaktar I just tried Haiku after seeing Jorden's post yesterday and ended up switching all of my bots to it. Crazy to think that all this time GPT4o has had such a negative affect on the voice and I didn't know it, but that seems to be the case. I think we need to encourage some more frequent discussions like this regarding the models from time to time. Very big difference, and a noteworthy development.

Is your incoming-call webhook setup?