I’ve seen some news about WhatsApp planning to restrict the use of general-purpose AI on the WhatsApp Business API starting in 2026. Does anyone here know more details about this change or how it might affect AI-powered workflows? I’m specifically wondering if business use cases like appointment confirmations, rescheduling, and follow-ups will still be allowed. Any insights, documentation, or experiences would be greatly appreciated. Thanks! https://www.whatsapp.com/legal/business-solution-terms/preview?lang=en

I was struggling with a prompt and RAG knowledge base for days. Decided to use Claude to help me diagnose and rebuild it, within 30 minutes, I fixed a problem that had stumped me for days. What made the difference: - Claude excelled at structuring data for RAG retrieval - Caught edge cases I missed in my pricing logic - Created both markdown AND JSON formats without asking - Spotted ambiguities in my original prompt that were causing issues Takeaway: Different AI tools have different strengths. For structured data work, prompt engineering, and systematic problem-solving, Claude definitely gets my vote.

I’m not sure if this is a very obvious question, but I haven’t managed to figure it out. Does anyone know if there’s a way to switch from one assistant to another within the same chat conversation ? I’ve tried using automatic tags, but they don’t seem very reliable. What I’d like is to transfer control depending on the need — for example, moving from a sales bot to a marketing bot, or vice versa. Is there a more stable way to achieve this?

I’ve noticed two things that would be great improvements: 1. Custom fields – right now they can’t be used inside tools, only in the prompt. It would be amazing if tools could also access those values to send as parameters. 2. Logs visibility – when a tool call is made, I can only see what was sent through the webhook. It would be super helpful if the logs showed the exact values that were sent with the tool calls directly inside Assistable.

Hi, I am aiming to use the new FlowBuilder's test messaging to test out the prompt I have built out. I ran into the initial error of: 401 Incorrect API key provided: sk-proj-********************************************************************************************************************************************************5qgA. You can find your API key at https://platform.openai.com/account/api-keys. I have created an API Key and added it to my WorkSpace that shows OpenAI is connected. Is this the issue? Right now, OpenAI no longer gives out the old-style sk-... legacy keys for new projects or accounts — all keys are now project-based (sk-proj-...). Any feedback on how to get this working would be greatly appreciated. Thank you!