We’re moving the community over to Discord soon. Skool isn’t going anywhere just yet, we’ll keep both running for a bit. But Discord is where things are headed. Why? Because we’re building for scale, and more importantly, for people who actually like to build things. Discord lets us go way deeper with integrations across support, apps, and APIs, so you can self-triage, debug faster, and not wait around for someone to hold your hand. It also means support won’t just be “post and pray.” You’ll have tighter loops with our AI, the team, and tools that actually help you solve things in real time. And frankly, Jorden and I absolutely love building and talking with the community. We've kept our heads down grinding to get some major upgrades done. As we reflect, discord will be the best blend for us to build and communicate with everyone. Skool was becoming another tab to manage and not checking realtime and we don't want that for anyone. 11 hour call is misleading, our Devs have been on longer than that. 😅

Hey everyone! 👋 Wanted to pop in and make my first post here. I'm Halie — I've been working with the Assistable team as a beta cloud employee. I'll be hanging around the Skool group and DMs pretty regularly, so if you ever need anything just tag me or shoot me a message. Quick background on me: I have access across all departments, vendor Slack channels, and the Assistable platform itself (browser + API), so I can jump in and help triage things when needed. Since I'm here, figured I'd share a few updates: Webhook fix — Yesterday some of you may have noticed webhooks not firing. We tracked it down to a recently configured webhook that got stuck in a retry loop and was hogging server bandwidth. Found it, patched it, should be good now. New system prompt — This is a big one. We updated the core system prompt for the first time in a really long time, and the beta tester feedback has been super positive. It's one of the most comprehensive agent wrappers we've built — proper date/time context, user context, cached memory across channels, and stylistic tuning that keeps your agents sounding natural instead of robotic. Along with that, here's the updated variable set which covers a wide range of date and time variables for all use cases: https://docs.google.com/document/d/1pH_gk89wUf0dSjx0wLlJKgFVYt9yPNgwLrgtFbu4TXs/edit?usp=sharing STT update — We're rolling back from Deepgram Nova 3 to Nova 2 for now to cover a wider range of languages. But good news — with the V3 front end launch, you'll be able to pick your STT provider yourself (Nova 2, Nova 3, Flux from Deepgram). And for the multi-lingual folks, we're adding Krisp AI as an audio passthrough for noise reduction and cleaner transcription. V3 front end — Took a peek at the latest GitHub repo and we're getting really close to pushing this out. It's a big step up in stability — agent orchestration, load times, run times, the whole experience gets a lot smoother.

Inbound and outbound latecy is now net 0 avg so the assistant is talking on answer both directions recordings on SIP good to go, beeps that were intermittent are gone SIP encryption routing logic implemented legacy twilio platform numbers pending release

Any meaningful upgrade comes with a moment of discomfort. V3 is one of those moments. To support what’s coming next, we had to migrate some core components earlier than planned. While this was the right decision for the long term, we know the timing has caused real frustration. If you’ve experienced call issues, delays, or unexpected behavior, we want to be clear from the start: We see it. We understand the impact. And we’re actively fixing it. Right now, there are three main things we want to acknowledge. First, there is a delay in the AI agent greeting on outbound calls, and this is affecting all outbound traffic. We know how important that first moment of a call is, and we agree that this experience is not where it should be. A fix for this is part of the upcoming patch and is being treated as a top priority. Second, some users are experiencing latency or connection issues. The majority of the platform is operating normally, but we already have a patch in progress that directly addresses these issues and will be rolling out shortly. Third, there is a busy signal issue affecting a small subset of numbers. We currently host over 14,000 phone numbers. Out of those, a few hundred are affected. If you’re one of them, your frustration is valid, even if the issue is isolated. Most of the impacted numbers fall into one of these categories: - Custom Telnyx setups that don’t align with our updated requirements - SIP trunking requests that were never completed - Older numbers still in the final stages of porting from Twilio to Telnyx If you’re affected, there are two paths forward. Option one: wait it out. For many numbers, this will be resolved automatically over the next few days as the patch and cleanup complete. Option two: move faster. You can purchase a new number and let our support team know. If your old number qualifies, we’ll credit your wallet for the entire year for the phone number ($30) for the trade-in. This option is there for anyone who can’t afford downtime.

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.