Feature Requests

It will be great to add additional booking node result variables. Currently we have: and I'm looking for ID (event created), CalendarID, ContactID in order to run a webhook to update the description information in the event.

Some sources remain persistent despite doing the steps to uninstall them. There should be a way to force remove the source or at least hide them. There are some sources that were added via client's GHL sub account which we no longer have access to. There should be a way to force delete them as source.

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.

currently when customer buying the CloseBot credit, they will get an invoice with all details regarding CloseBot and breaking the whitelabel because CloseBot website also mentioning GHL. Would be great if they can buy the credit and and not mentioning any CloseBot and GHL at all.

I recently discovered that Closebot is not fully white-labeled internally. It is currently selling credits under the name "CloseBot LLC," which can be easily traced back to the primary source through a simple Google search. I strongly recommend prioritizing this issue to ensure full white-labeling. Users of the whitelabel highlevel expect a completely white-labeled conversational AI, and Closebot does not fully meet this expectation. Let's address this promptly to align with our standards of complete white-labeling. Additionally, I propose the idea of offering an upselling feature under our corporation as a valuable addition, although it is not essential. Alternatively, providing the option to disable the feature for purchasing credits would also be beneficial. This flexibility could enhance user satisfaction and align with our business objectives.

Ability to virtually remove the delay set on the persona when testing. Thank you!

Want to be able to edit a persona from a job flow without going back to the main Agents page

If we could get a highly accurate way of determining whether the AI has trouble answering a message and then logging that so we can monitor and add to the knowledge base that would be helpful

Currently, when the setting “Add AI Off on Manual Replies” is enabled, the AI Off tag is applied if a team member replies manually from any channel (SMS, email, etc.). This stops all further bot interactions, regardless of which channels the account is actually configured to use. Example: Our account is set to respond via SMS only. A team member replies to a lead’s email. The system still applies the AI Off tag, and the bot stops responding on SMS — even though email is not a reply channel. Request: Update the feature so that the AI Off tag is only applied when a manual reply occurs in the channels selected as reply channels in account settings. For example, if SMS is the only reply channel selected, then only a manual SMS reply should trigger the AI Off tag. Benefit: This prevents unintended disruptions, ensures the bot keeps functioning in the chosen channels, and gives users greater control and accuracy in managing AI interactions.

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