Feature Requests

When CloseBot displays a “Source error: Unable to refresh token” notification, it currently does not indicate which connected source the error is related to. This makes it impossible to troubleshoot, or implement a fix. The current error message — “There may have been an issue with your source connection. This is not an issue with our platform. See if this has caused any AI response issues and add the source again to fix.” — is too generic to be actionable. Without knowing the specific source, users cannot determine which integration needs to be reauthorized or reconnected. This results in unnecessary time spent guessing or re-adding all integrations just to find the one that failed. Proposed Enhancement: Add source-level attribution to these error notifications. For example: “Source error: Unable to refresh token for [Source Name]. Please reconnect this source to restore functionality. Why This Matters: Users can immediately identify which source to fix rather than guessing. Reduces support burden: Support teams can quickly isolate and verify the issue. Example Scenario: A user receives three “Unable to refresh token” errors within 24 hours. Without source attribution, it’s impossible to tell if the issue is with one connector repeatedly failing or three separate sources. Identifying the exact source would make the message meaningful and enable a quick fix.

It would be great if a "does not contain" option was added to the Switch etc nodes for us to choose from.

As shown in the attached in image. It would greatly speed up our workflow if we could have the cursor auto focus into the search field after clicking the '+' icon in a node. Currently we have to click the + icon and then click again into the search field to begin typing.

Link the contact name in the Closbot conversation tab, to the GHL contact tab. When checking the conversations inside CB, it would be nice to have an easy way to immediatly check the contact in GHL. This is possible if you make the contact name a link; Just fill in location id and contact id: https://app.gohighlevel.com/location/{{location.id}}/contacts/detail/{{contact.id}}?view=appointment

It would be super useful to have a time and date stamp showing when each conversation log is generated

Currently, the only available option is to see how many Job Flows are connected to a Persona, but not which specific ones. To check that, you would need to open each Job Flow individually. This is not useful enough when trying to trace things or trouble shoot. Solution: Allow us to click into the number of Job Flows a Persona says it is connected to and see which actual Job Flows are connected - make it clickable to dig deeper.

See attached image. Looks like the follow up edit buttons weren't properly coded.

In the deletion confirmation modal, it would be very helpful if the file name of the item to be deleted was added... Just in the off chance someone clicked the wrong item's selection dots and thought they were deleting a file different from the one they selected.

Maybe a way to check in which conversation specific bots are being used. We have many bots for one source and there seems to be no way to track the usage of a specific bot. Maybe filter by agent?

Action panel is way too wide especially on wide screens, taking valuable space from the grid. It should have a maximum width where all actions/items fit relatively well and anything beyond that don't allow it to get any wider.