Understanding The CloseBot Classic Workflow
First, let's start with a refresher on how the CloseBot Classic workflow works. To set up CloseBot Classic, we required that you install the CloseBot app and create one simple workflow (shown below).
Trigger - Any time a customer replied, this worklflow would get triggered
Action - Any time this action was executed, the message would be sent to CloseBot Classic to determine a response
Read through these examples below and look at your own CloseBot workflow to see if you've modified it. There isn't a way to automatically adjust on CloseBot's end for adjustments you made within GoHighLevel. It's up to you to understand how you've modified things and adjust accordingly during migration.
⚠️ Multiple Bots in One Subaccount
If you were using CloseBot Classic to trigger different bots within the same subaccount, this required an edit to the one workflow (shown above). This will stop working with the update.
SOLUTION: The update allows branching and triggering different agents depending on tags from within the CloseBot user interface. If you were previously using multiple bots within the same subaccount, you'll need to instead either...
Build one agent flow that can handle the job alone
Build both agent flows and then choose the tags that each should be on for when you connect your source to the agent (see below)
⚠️ Filtering Out Responses
With CloseBot Classic some users chose to filter out messages that they didn't want the bot to respond to. Users did this by modifying the CloseBot workflow to only send messages they wanted to process a response for to the CloseBot webhook. Again, since CloseBot does not use workflows anymore, this method no longer works.
SOLUTION: CloseBot still honors the tag ai off. If the contact says something and you want the ability to turn the AI off when the contact says certain things, use a GoHighLevel workflow to add the tag ai off in these scenarios. CloseBot support does not help with GoHighLevel workflow modifications. If you need clarity on how this can be done, please contact GoHighLevel support. CloseBot's move away from workflows makes it easier than ever to troubleshoot and deploy expert level agents!
⚠️ Disqualifying Leads
Users modified the CloseBot workflow to disqualify leads. They would edit the workflow to make it so disqualified leads no longer got a response from CloseBot depending on the value of a field or the presence of a tag. CloseBot is always on after the update as long as a contact matches your tag settings.
SOLUTION: Build your CloseBot agents utilizing branching to disqualify leads. CloseBot branch actions make it incredibly easy to do lead qualification now.
⚠️ Only Reply on Certain Channels
As a workaround to only have the bot reply on certain channels, users could modify the triggers that triggered the CloseBot Classic workflow. Since CloseBot no longer uses workflows in this update, this will stop working.
SOLUTION: Instead, you're able to modify the channels when you connect a source to an agent job similar to how you are able to make the agent only listen when certain tags are present.