Hi Assistable Community, I am having issues with our workflows on how to adjust when a lead says, check back with me in January but then our workflow kicks in and starts hounding them a few minutes later. What would be a way to solve this if the AI made a note to check back in January and have it stop workflows until then? Looking for your wisdome and feedback

Is there an easy way to implement Assistable in other platforms instead of GHL ?

I hope you are having a great week. I am testing an outbound agent and it cannot access the calendar to book an appointment. The tools are selected, calendar synced, and calendar active in GHL. I already re-connected and the bot still says that is having technical problems and cannot book the appointment, can't even open the calendar to give time slot options. I added the note. The agent actually gets the task for live agents to call, but I want the AI agent to be able to book the appointment. 😐 Is anyone having similar issues? SOLUTION: I figured the issue. The assigned calendar was a Round Robin. I created a Personal Booking and now is able to book the appointment.

So, its been a long process and a lot of work - literally re-writing our voice orchestration to be native - and we still have a small sprint before we will start flowing traffic that way. Here is just a general guide of somethings that will change, be added and be deprecated. So, rollout. first - the users using our numbers will start seeing the traffic flow first. Then older numbers. Then trunked numbers. Nothing tangible changes from your perspective besides lower latency. Tooling - So, we are adding POST / GET / PUT / PATCH / DELETE to api request types. We also have it where you can configure headers, query parameters, path parameters and body parameters. So, fully customized API calls. We will suppose variables in these as well so you can pass API keys or your access token for GHL. Here's the thing, tools is now running through a proxy of ours that will open up the doors for a couple things: - Tools to run as they do today - Direct API calls (will be a toggle), so instead of being wrapped in a args object with metadata, etc - we will just send the API call. This gets rid of the need for middleware because you can make direct API calls. - Workflow execution; not today or the next week but we are adding native workflows to the platform. You can configure a custom tool to trigger a workflow locally to run multi-agent frameworks and basic automation so we will support a middleware internally. Abilities - all stays the same, but we are adding agent teams in voice (chat following right after). So, add different assistants into call to create a team env on the call either through a "prompt change" so we just change the prompt dynamically, or through a team so mutliple voices, etc. AI Models - We will be running a custom fine-tuned model thats been fine-tuned for voice orchestration. aka, this llm outputs text-to-speech friendly output to keep weird translations to a minimum. You will be able to select an OpenAI model if you would like and run it with your key if you prefer OpenAI output.

Happy Holidays Assistocrats! I have a potential client that currently is using Follow up Boss and I was wondering is anybody has experience connecting Assistable to Follow Up Boss that would be willing to provide insight as to how to connect the AI agent to that CRM, Thanks in advance!