We use anna for our outbound and she is picking up an Australian accent mid-way through our script, as if the actual bot is changing voice any idea why that is or how to stop it from happening?

Has anyone created a workflow for when someone calls your bot back or calls into your inbound bot for it to create a contact or update a contact if the contact is not in the CRM yet?

I'm having an issue mapping the webhooks. I have a few custom tools that should be sending data over to my workflows, but they are not posting the info to the webhook. The main outbound webhook is working but none of the custom tools are, anyone have any assistance they could offer or some insight?

The wallet is connected and we follow up with it consistently but it is isn't auto-filling on a low balance. Any news or suggestions here?

Vid tells all - but TLDR below. BTW sorry about call yesterday, I slept pretty much all day preparing for this Chat migration is done... - Chat infrastructure is now on GCP which is a really scalable env for like... ever. - Context action is now on it too but on a local endpoint so I will monitor this to day if we need to move it - end to end sending on 0 wait time is about 800 - 1600 ms, great for live chat - Claude + Groq + User input cleanses are in place, on par to get rid of platform down time and vendor downtime on track for 100% uptime - Latency estimates and knowledge embedding tester is now showing - a lot more stuff but ill let you find that stuff on your own - Context action is on this as well. Claude Beta: - Claude models are usable in chat. They are good - long winded and tend to take prompt a bit different than you are used to but you are free to use it - Its in beta so if you say "it didnt xyz..." im just going to tell you to go back to openai lol - Custom Tool Schema (Chat): - { "name": "book_appointment", "locationId": "123", "contactId": "123", "account": "123", "args": { "request": "123" }, "meta_data": { "calendar_id": "123", "location_id": "123", "access_token": "eyJh...R4", "timezone": "America/New_York", "contact_id": "123", "assistant_id": "123" } } - So your custom tools should be good to go in the migration. locationId, contactId, and account will be deprecated in the future in favor of meta data. Marketplace Beta: - Create listings for lead magnets, sharing ideas, getting bots and resources. Community focused building - How it works: Create a listing, connect an assistant, write a landing page and attach files for the buyer to receive. Shop around or create listings - if you have an assistable-based business, your files can include lead magnets etc etc... - Everything is free in beta - in prod, you'll be able to charge and transact around bots, snapshots, knowledge, tools and more. Go get the 3 on there because they have good resources.