We have a couple of Twilio-imported numbers in Assistable, and they work perfectly for inbound calls, but with outbound calls initiated through GHL there seems to be an issue. Usually if there is an error like that there are logs inside Twilio dashboard and I can troubleshoot, but not this time. The Assistable call error just says `telephony_provider_permission_denied`, but there is no trace of the attempted call within Twilio, so I am not sure where the source of the problem might be. Additionally, attempted calls are doubled in "Call List". Not sure if that's relevant, but there it is. Any hint or assistance would be appreciated.

Double checked & made sure that: - assistant ID is correct; - API key is valid. Response body: { "error": {}, "label": "assistants", "message": "Value for argument \"documentPath\" is not a valid resource path. Path must be a non-empty string." } Any thoughts / ideas?

In your experience, how detrimental was exceeding the character limit of 8000 for a global prompt? Do we know exact consequences of going over the limit, or is it just a general guideline, not a strict rule? 🤔

Has anyone encountered that? Occasionally, post-call webhook gets triggered several times for the same call, milliseconds apart, up to three times.

Currently, is there any way to create new, or update existing assistants through API endpoints? I was looking through old threads here, and found one endpoint: https://assistable.ai/api/1.1/wf/create-chat-assistant_open as well as the following: http://api.assistable.ai/assistants Both seem to return 404 "Workflow not found" when sending requests. Searched through documentation, but it seems to be a work in progress. If there is a cheeky way to modify assistants through requests - their prompts, voice settings, custom functions - that would be an awesome piece of knowledge. Thanks in advance!