So, saw some stuff come in about duplicate / double messages coming through - started as just FB but it seems like meta and custom conversation providers (whatsapp etc). Triaged it to find there was a timeout-retry happening for wait times & / or large tool stacks - the server would think the request is taking too long and try again only to find out that the request was just finishing up. I added a proxy before the chat completion run which allows us to queue the run so this never happens again :) let me know if you see different, happy monday

We're aware of reports of an Oauth issue that's linked to Google Cloud. We're investigating and will keep you posted. Thanks!

Is it possible to use the sleep timer as an automation trigger? The idea is that when the account owner replies manually a tag is set and the bot is permanently blocked from continuing the conversation.

For one client, we have the situation that they have leads in Switzerland, Germany, and internationally, so they get replies in at least 3 languages. How do you guys solve having the chatbot always use the right language? Because currently, in 3/10 cases, the bot just continues in German instead of switching to English.

Loom: https://www.loom.com/share/25e8e7ec1364421c9837fc25be33404e Document: https://docs.google.com/document/d/130Qur08lsWwiN5NxGMkSA_mFqStEf6UZooZx3wYYe-E/edit?usp=sharing Snapshot: https://affiliates.gohighlevel.com/?fp_ref=assistable&share=J0z5svoOXMYHM89KOXFS We'll treat this as a living snapshot meaning we may update versions / patch versions from time to time from our testing and community ideas / feedback. I didn't do CRAZY error handling on it specifically to not over complicate it and not interfere with things going on. This is a state-based practice self-selling demo meaning its a fun way to learn how to use custom fields to change states in your assistant based on different conditions. Feel free to customize and have fun :) Couple things you need to do: 1. Create a demo assistant and use the custom field "{{contact.self_selling_objective}}" as the prompt. This allows you to dynamically change the assistant's prompt based on where in the demo you are. 2. Set up the post-call webhook in the second flow "post-call". Go to Call Settings and then post-call webhook, input the url from the trigger and then initialize it. You can use that reference which maps the rest of the flow. 3. Take your assistant ID and plug it into the 3 Make AI Call actions to make sure you are using your assistant and not ours (it was cause errors if not). 4. Take the prompt from the document and re-format it with your branding for the closer (this will be different for you because it will be your business and your identity etc. - I left it out because its your interpretation on how you want to close after the demo happens but I did leave an example) 5. Trigger the workflow with the form or add your contact to the start flow manually in the contact page. 6. Test, refine and have fun :)