This is me (clone), calling me

Name another platform that gets down in the trenches to not only be obesessed with their ICP but become their ICP. If you want a simply reason, why Assistable? 1. We have an agency too. We live it everyday. We know what it’s like to scale an ai service offering and we take that to make product easier for you to do the same. 2. We got an OpenAI token award from OpenAI, meaning we’ve done this so much that not even OpenAI can deny our volume. Very proud of the team, very proud of our mission. Realize no one will outwork us to be more obsessed with our customers needs. Love yall

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

Alrighty, I finished up the self-selling snapshot. Screenshots attached of a sneak peak. Im going to have the guys (and team) check my work tomorrow before we release it and add more failsafes (like accidental hangups etc) and get 'er launched. I'm gonna go spend some time with little man and will film and send out snapshot after someone else testing / breaking :) This includes 1 assistant with 3 states: evaluator, demo, and closer. Meant to actually extract information from a user, turn it into a usable demo (and send the demo) and then finish them with a closer agent afterwards. This also includes access to 3 unofficial apis: misspelling API, screenshot API, and webscrape API. These send a screenshot of the user's website and a quick blip to kick off the demo stage. I've also included some custom javascript to correct URLs from form fills (some people love to mess up their own website url..) A doc with prompts and instructions included. If yall want, I can throw in our demo landing page as well? dunno if you want that or not. tons of fun, looking forward to it

So, last friday on the Friday founders call (you should so totally join in) -- we built a BAD ASS self selling demo that dynamically changes it's own prompt to actually generate a prompt for the user, demo it to them, and save it to use later (I added a lot of functionality to it) This is a comprehensive self-selling demo :) I will release the snapshot and the accompanying video later today