I noticed that the Twillio SIP trunking issue seems to have been solved. But post that I am having a weird issue that I dont think is an assistable issue, my call forwarding to my client is not working. I tried forwarding to another number, it worked for one number, and for the other it didnt work. So I am not sure what the problem is. Could it be an iPhone related problem? I am just trying to see if others faced a similar situation and what did you do to solve it? TIA

30 mins over the calling snapshot and how to dynamically use it - and high level explanation of what everything does inside of the workflows. https://affiliates.gohighlevel.com/?fp_ref=agencentric&share=LLXeKJVPDSwnwlP3rr6Q

Do you not feel that the community is clearly asking for more support, content, help, and answers — or is it simply a matter of not wanting to? At the same time, posts are being removed because there is supposedly too much “negativity” or too much “support” as a theme. My frustration is really starting to run high, because we keep being told to stay calm while, in the meantime, customers are leaving, people are getting angry, and our reputation is taking a hit. It’s time for action.

Hey @Assistable Team and @Jorden Williams appreciate all the effort from your end these last couple weeks to resolve issues and the quick responses on tickets. However, this whole ordeal made it very clear that we urgently need official communication channels for product updates and known issues from you all. Going weeks without official update other than a Skool post and comment here and there is not a good standard, especially considering your growth, and the amount of people affected. I would imagine establishing these channels will also reduce your internal ticket load for support. I’m not ragging on you guys, I’m a huge supporter so let’s address it for the future. Specifically: 1. Public Changelog - Currently discovering new features through Skool, support tickets or accidentally in the dashboard is unprofessional and unsustainable. We need a centralized, publicly accessible changelog documenting all releases, feature updates, and changes. Also I realize there is an existing changelog page - it has not been used since Nov of 2024. Please start using it again and/or relocate it. 2. Reporting Known Issues / Updating the Roadmap - When global issues occur (like we’ve seen recently), we need an official update about it: - Identified bugs and their scope - Expected timeline for patches - Resolution updates In addition, the roadmap needs to be kept updated or house known issues potentially. These are just my suggestions, the execution is up to you but we absolutely need this information. Without these basic channels, we can’t professionally communicate with our clients about service disruptions or changes. When issues arise, we’re left guessing whether it’s isolated to our setup or global, and we have no official source to reference when clients ask what’s going on. Nevermind having Uptime SLA’s and compliance (which are offered by other vendors) — not having a resource for this is becoming detrimental while expecting to implement AI voice operations for a business. Seeing all the headaches people have had with managing clients is all the evidence needed. Stop ignoring it please and let’s do something about it! Given Assistable’s growth and the business-critical nature of voice AI for many of us — it’s a fundamental requirement for enterprise readiness. Would love to hear the team’s thoughts on implementing this.

@Assistable Team Assistants not sending messages in one of my reseller accounts. OpenAI key good and have available balance on my account.