Easy Fix: https://www.youtube.com/watch?v=wAdhjkQTBtM

On August 26, in just one hour, our API Key consumed $29.84, which projects to $21,480 per client per month if that rate were to continue. To put this in perspective: - With 10 clients, this would scale to $214,800 per month. - With Assistable, the cost would only be $3,000 per month. - And the correct cost using GPT-5 mini directly should be just $200 per month. This clearly demonstrates a serious error in token accounting: instead of the expected ~8.5k tokens per conversation, the system is logging around 22k tokens, inflating consumption by more than 1,000x. It is urgent to verify whether the system prompt is being duplicated or if the wrapper/API is sending redundant data. ⚠️ This is a projected analysis assuming each client consumes 15,000 conversations with a prompt of ~8,500 tokens per conversation. We urgently need help with this, because if the API Key were billed correctly, the cost would align with expected consumption. Even compared with Assistable’s API Key pricing, the current difference is abnormally high. I hope I have explained my point clearly. @Jorden Williams

What issues are you having right now with the platform? - Prompts - Workflows - Tools - Automation Let me know in the comments, I will record a loom of my solution or setup and share with you. No strings attached, just me helping you out.

Assistant NOT WORKING. Clients are getting into GHL, adding active TAGs, but the Assistant is not working, not responding. Anyone else having the same problem? @Jorden Williams ? Here's an explanation of what is happening: https://us06web.zoom.us/clips/share/UNKPHKseTsCXLMom-_7qBA

Looks like OpenAI had an unannounced billing top off or invoicing error that would not auto top-off your account. If you have your openAI key in at the workspace, make sure to check your openai acct is funded and valid to mitigate issues, we are adding our open sourced model in as fallbacks for those with their key in the workspace level check a few this morning and they've all been this top-off error