Sip trunks from twilio to Assistable stop working for me

Chat gives generic answers, escalates unnecessarily, or says it doesn’t have the info. The same global prompt and KB are used for both. KB entries are text-based Q&A and category-specific, and Voice retrieves them correctly.

Is there something wrong with the Assistable System today? We are getting this message on all of our calls "No access token received". I totally understand that sometimes the system could be down, just being asked by our clients. Thanks

anybody else getting this? This came out of nowhere and I'm not sure how to fix it.

I’m setting up a bot , and I want to confirm best practices around call ownership and human transfers. Scenario: - Inbound call hits Twilio - Call is routed via SIP / ZipTrunk to Assistable (AI answers first) - When escalation is needed, I want to ring multiple numbers sequentially (ring group / fallback) My understanding so far is that GHL ring groups only work if GHL owns the live call leg, meaning if the call stays in Assistable via SIP, GHL can’t actually execute multi-line transfers — only logic/notifications. For those running this in production: - Do you keep inbound numbers hosted in GHL and use Assistable only as the AI brain? - Or is there a supported way to hand the call back to GHL mid-call to use ring groups? Curious how others are architecting this without dropped calls or messy workarounds.