I have a foundation repair client that i need to transition over.

Quick context: Last week I ran a free workshop inside the LeadIndicator group. During that session, I walked through the exact Assistable workflows and automations we use internally — the real ones that run our business, support, fulfillment, and scaling. There was a lot of interest in getting those workflows, and since the workshop was positioned as pure value with nothing to sell, I decided to give the entire snapshot away for free to that group. Rather than keep that value isolated, I want to make it available here as well. ✅ What I’m giving you - The full Assistable snapshot - The exact workflows we use internally - No stripped-down templates - No pitch, upsell, or funnel This is not something we normally give out publicly. The only thing I’m asking in return If you’ve found value in Assistable, I’m asking for one small favor: 👉 Go to Google, search for Assistable's TrustPilot page. Leave an honest review on our Truspilot page. That’s it. Reviews matter a lot — especially as we continue to grow and as we deal with the occasional bad-faith review that comes with scale. Your feedback genuinely helps. 📬 How to get the snapshot - leave a review on our TrustPilot page - Comment that you've left the review and I'll DM you.

What do you do if your prompt needs to be longer due to pathing through complex scenarios? I have a tax client with like 6 calendars and services that the agent is having to sort and path through and book on the appropriate calendar. I've used a calendar matrix and I think I've reduced every last character I reasonably can. I'm still at 13,351 characters. My concern is that I have an upcoming client with like 20 services with a good 5-6 products each per service and will have a similar scenario. The biggest challenge with length is that I'm having straightforward tools fail on me on both SMS and voice (e.g. add a tag, calendar booking), and help.assistable is telling me it's a matter of prompt length and to reduce it to 8K characters. Any advice, direction, tips, or help would be truly, truly appreciated! ...TRULY APPRECIATED. Thanks in advance!

Hey all, I have been fighting with this prompt for weeks now. I have a an OG client that I'm about to lose because we can't get this right and need your help. @Tom Pacheco @Brandon Duncan I have a prompt that has been modified extensively from the original because of the user's needs and I keep running into the issue with it booking the wrong day. When someone asks for "saturday" and there is a block on the calendar, the ai looks at "monday" (the next available day) and books it for "saturday, october 20th" (its driving me bonkers and the client is fed up). Can someone Please give me an assist here? @Assistable Ai @Assistable Team @Luis Garibay PS yes the prompt is long for sure and might be why it is hallucinating. It adapted to ensure it captures a name everytime vs "guest" from a whiteglove set up I purchased. I have 3 main round robin calendars and 7 personal calendars mapped based on location and caller preferences in a custom tool. Thanks in advance for your help! https://docs.google.com/document/d/1NK0iwQvjEwuhoy6Ed55TrB6snHVM8x4YHeDgqLs6jp0/edit?usp=sharing

Hi everyone, I just read a LinkedIn post where someone lost $20K in minutes because their Voice AI callback form was hit with fake international numbers. Their agent kept calling and talking, draining their balance completely. This is a wake-up call for us. We should make sure we’re fully covered against something like this — things like CAPTCHA, spend caps, geo locks, concurrency limits, etc. I wanted to bring this up here so we can make sure we’re all covered and avoid any risks like that and protect ourselves and our clients. Better safe than sorry. 🙃 We’ve seen a few of our clients go through this too, and it can get really messy really fast. That’s why I think it’s important we put the right safeguards in place together. 🙌 @Assistable Team @Mike Copeland @Jorden Williams