Abhishek Kumar Looking forward to Jacob's answer.

My answer is, it depends. That should be up to us. The Trigger shouldn't have automatic actions. It should simply activate a workflow. We then get to decide with Actions what happens next. One option would be to Remove from Workflow (we would need to specify which one(s)). Adding tags and notes are most common actions.

Great meeting you today (this is the correct Abhishek, yes?).

Keith Besherse Yup you are right , we did connect today

Keith Besherse the thing that you are tallking about can be possible in sub account bot , we will be releasing that feature shortly trigger workflow based on condition

but in workflow but we cannot build that .

since the contact has to branch out of the workflow , what is your feedback just to gauge

should I exit from workflow or make the contact stay there as it is and then someone can manually remove or create a branch

Abhishek Kumar I don't think this is something that should be done with the AI prompt. It is a workflow trigger (I assume that is Prasoon Dadhich's team). I think we need a trigger to activate a workflow that we then can use to take actions (one of which might be putting the bot into Inactive mode, https://ideas.gohighlevel.com/changelog/update-conversation-ai-bot-and-status-workflow-action). But what we are asking for here is not a modification to the prompt or your objective-based prompting as discussed on Zoom.

What would be super nice would be the option to tell the bot whether the human user is taking over entirely or whether the bot should just go into listening mode.

Thanks Again, KeB

Keith Besherse nopes , the conversation AI bot actions are within our team any feature that needs to be developed should be developed by us , so if you want the contact to exit or stay .there has to be done by us

Abhishek Kumar, I am not trying to manage the HighLevel development team. I apologize for implying that I care who or which team is responsible.

My point is, this is a workflow trigger that affects the Conversation AI. It also affects adding and removing tags, executing math operations, activating wait steps, adding notes to the contact record, assigning tasks to users, updating opportunities, and a whole host of other possible workflow actions.

We want to trigger a NEW workflow that can then be used to pull the contact out of the Conversation AI workflow if (but only if) we want. But more important than a Conversation AI workflow would be a long-term nurture workflow where the contact might be getting an email every couple weeks or a month. But if they had a live conversation with a human or Conversation AI it might not make sense to let the nurturing email sequence continue without checking for whether it is still relevant.

Keith Besherse lets get on a call tomorrow , I will Dm you over fb .

I think we have something solid to discuss

Abhishek Kumar So this is important for metrics. Customer Replies > Fires Hook to detect 1st chat timestamp. User Replied Trigger > Hook out. Average reply time. You may also want to use it to disable external 3rd party chatbots. Some sales teams may also want wait steps where if the client isnt spoken to in 5 minutes or less by an assigned user that it switches to a new user. So you would need this other workflow with user replied trigger to help revoke them out of the 1s workflow.

Abhishek Kumar To answer the question more directly: It would be nice to have an option at the workflow settings top level that removes contacts when users reply. But having that as a workflow trigger also opens up a lot of new automations.

Abhishek KumarI'm with Kieth here. I think maybe there is a miscommunication or misunderstanding on what the goal here is.

This isn't about just the Conversation AI

This is about ANY TIME a user replies in a conversation, we want to be able to trigger a workflow.

Possibly we can have a filter on this trigger, that checks if Conversation AI was active when the user replied, so we can then handle bot related actions.

But this goes above and beyond Conversation AI.

Sure give us a setting if you want on a Conversation AI where we can default what happens when a user replies to this bot (Pause for x, or stop bot or trigger a workflow)

But this idea on the board is about an actual Automation Trigger that allows for handling any conversation with or without a conversation bot involved.

Hope this clears up what we are all saying.

Carl Taylor okay carl , we can do that , but for time being since I am managing conversation AI , we will give you an additional branch in conversation AI , when user replies manually , the contact will be moved to the new branch

In that new branch you can do anything you like

Brandon Burris Yeah for sure, I built an app does this: https://cloudlab.so/stellarr/outb-msgs

That way you can use the context from outbound messages too for automations involving AI

Adam S thank you. The only thing I find is that I need to have payment details in my sub account to actually use it. I don't have SAAS mode enabled on some of my free sub accounts, and so there is no way to use it on those accounts unless I enable SAAS mode on them and add payment details.

Rohan Williams Nice speaking with you just now. Yes this is a problem with their built-in billing it seems. I'm gonna re-work things so you can install it on any/all subaccounts

Mike Hochwald, link to your version please.

Tommy Mutchler also messaging channel as a filter so we can fine tune our

automations.

Myles Walsh this was a problem we had with DRIP campaigns. A user would send a message to someone and then the DRIP automation would send another message soon after confusing the contact.

If we had a user reply trigger we would simply remove them from drip campaigns or at minimum restart the drip timer so they don't get bombarded with messages both manual and automated.

James Campbell Yes you can. I think that it's more about giving this as a common action since it is an api thing already: https://highlevel.stoplight.io/docs/integrations/028dcf92ee0b9-outbound-message

James Campbell we get charged 0.01 for every run on that webhook, and it is so basic to add an outbound reply trigger that we need to push for it.

Robert Lemmens, yes! The AI doesn't have any idea what to do with image responses. Especially in the Instagram channel, "You were mentioned by ___."