@Jorden Williams @Mike Copeland I recently deployed the following Chat follow-up, and it looks like the follow up message is simply going through the next task in the global prompt with each iteration, resulting in it ultimately booking an appointment for people when it gets to that task even when they have never responded yet. Anyone have any suggestions on how to prevent that within the "Chat Followup" tool? Here is my context within GHL: ## Context: The user has not responded to your last message. It has been {{datetime_formatter.6.days}} day. It is your responsibility to re-engage users that have not responded. Here is the previous message history to have complete context of what has been discussed so far: {{contact.message_history}} ## Task: 1 Generate a message to follow up with the user to restart the conversation based on the known message history and the last message you sent.

We have been working on this very heavy. The chat widget that is in the portal is marked as beta because that is what it was at the end of the day - a way to test the use case if it was worth it over GHL widgets. As the horizons expand, and use cases continue to grow, the need for a omni-channel widget integrated with / and modularly decoupled from GHL comes up more and more. So, we can expect that chat widget goes into official production with proper support and caching within the next week - will be omni channel, voice and chat, and configuration with prompts.

I’m having an issue with outbound AI calls.When the system places a call and the person hangs up almost immediately, before the call fully connects, the system instantly makes between 2 and 4 additional contact attempts. In my setup, it should only make 1 call, not multiple retry attempts in a row.I already checked and I do not have multiple workflows triggering the call. What I want:If the person hangs up immediately, I want the system to stop and not call again. My question: Does anyone know whether this is controlled by the workflow, the call logic, or whether the system is interpreting those calls as not connected and automatically retrying? Thanks! @Anthony Castiglia @Luke Houk @Jason D @Jakin Harper @Justin Lee @Brandon Duncan @Esteban Lopez

trying to add balance to my wallet, but I am getting this

Inbound calls are showing as inbound in GoHighLevel and outbound calls are showing as outbound - instead of all being outbound. If you are having trouble with transfer's, we have voicemail detection on it - we added an option where you can turn it on and off depending on your usecase. - If its on, and we hit a voicemail on transfer - the assistant will return back to the call and let the user know that it hit voicemail. However, this may trip up as being marked as voicemail for VOIP round robins or queues so it may not be the best in that use case. - If it off, we will just send the call through. This is best if you are calling to a queue / roundrobin / apple inteillgence where we think that we are hitting a voicemail but really arent. --- Dev sprint to day so patches flying in