Is the inbound {{greeting}} being worked on? Its not the end of the world but when the assistant answers she immedietly starts explaining her identity and role and it just feels robotic and salesy

I know there are limits to the recommended character count but has anyone gone a good amount over and the assistant still works fine? Just don’t wanna mess it up unintentionally. Also have tried {{current_date}} don’t use UTC, search web to match dates, p much everything recommended by ppl. If I ask what’s your availability next Tuesday still gets it off by one day. If anyone has a fix for this other than outright telling the AI to stop referencing days of the week would be great.

Just wanted to say after a really tough couple of weeks with all the changes, our assistants are working amazing this week. Multi-calendar working seamlessly again, custom tools being called correctly, assistant sounds more "human-like" then we've ever had before (switched everything to Claude), conversations flowing and appointments being booked from old stale leads. Just wanted to share some positives in light of some rocky weeks. Inbound {{greeting}} is the only small issue we have but it's not the end of the world. Thanks for to everyone putting in work behind the scenes!

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.

Hey, we're 6 weeks into 2026 and the day is still 1 day earlier than the date as if it's still 2025. Is there any update on when this is going to be fixed? Lots of clients having huge effects because they book for Feb 10 on Monday for example (AI books for Feb 10 Tuesday which is correct), then the prospect waits around on Monday and is annoyed when the sales rep shows up on Tuesday. @Jorden Williams @Assistable Ai