Can Assistable reply to emails now with the customer replied trigger and active tag? Anyone having success here?

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 :)

Just figured out how to put the AI to sleep on only manual outbound messages from a user. Whoop whoop! Actually easier to create than I initially thought it would be. Would this be a beneficial Workshop Wednesday build?

C'mon guys and gals. This feels like such a no brainer feature that for some reason is non existent. My med spa client wants to have their patients send in photos to their assistant... We don't need to analyze them, just acknowledge the user with a simple "Thank you for the photo, our team will review and get back to you" It's like checking the fridge for milk before going to the store. All these features like tool calls, automatic extractions, calendar bookings... But we can't check a fridge for milk??? Ludacris In the server logs you can see a line item for "attachments" When there is no attachment, the field is empty When there is an attachment, guest what...ding ding ding. The field is full And instead of a simple prompt to check the field and acknowledge this... Instead when an image is sent we get a repeater response making the AI look....exactly like AI @Jorden Williams @Mike Copeland @Bernie White @Assistable Ai @Assistable Team Will all that's wrong in the world, let's do some good and knock this one out of the park... let's make sure we check for milk so we don't buy what we don't need. Happy to make a Loom or explainer

What would you do if you wanted to pause an entire AI campaign at once? would you just tag all the contacts in a bulk action with ai_off and then when you're ready to resume bulk action remove ai_off?