Agent actions are currently written to always respond (as AI models were not yet robust enough to decide when to avoid sending a message). We have a beta in place now to test new message prompting that allows the agent to decide when it does and does not make sense to process a response. If you want to join the beta, email jarod@closebot.ai and he will get you added!

📈 -> we are again pushing focus onto our Analytics (reporting) features. This has been long in the works, but we are getting close! Once complete, this will allow you to customize the analytics shown on your dashboard, allow you to split test personas in measured A/B tests and more.

💻 -> The MCP released a few weeks ago allows CloseBot to MCPs. The CloseBot MCP that allows you to connect tools like Claude, OpenAI, Viktor to CloseBot is still in the works. We expect this to be released late-July.

📚 -> A general revamp on how our Knowledge base reads information and adding Google Drive and Notion as upload sources you can connect to your CloseBot knowledge base as LIVE knowledge base options! 🎉 Expect this next week!

After one full year of operating in V2 we decided to clean up the subscription selection screen to give better insights on instant charges, trial adjustments, and next payments. This is also more suitable for viewing on mobile devices which aligns with our push for providing some features as mobile-friendly.

Along with the visual updates and mobile support for the settings and subscriptions pages, we also adjusted the chat and home screens for mobile view so you can watch CloseBot conversations while on the go.

Agent actions are currently written to always respond (as AI models were not yet robust enough to decide when to avoid sending a message). We have a beta in place now to test new message prompting that allows the agent to decide when it does and does not make sense to process a response. If you want to join the beta, email jarod@closebot.ai and he will get you added!

📈 -> we are again pushing focus onto our Analytics (reporting) features. This has been long in the works, but we are getting close! Once complete, this will allow you to customize the analytics shown on your dashboard, allow you to split test personas in measured A/B tests and more.

💻 -> The MCP released this week allows CloseBot to MCPs. The CloseBot MCP that allows you to connect tools like Claude, OpenAI, Viktor to CloseBot is still in the works. We expect this to be released mid-July.

📚 -> A general revamp on how our Knowledge base reads information and adding Google Drive and Notion as upload sources you can connect to your CloseBot knowledge base as LIVE knowledge base options! 🎉 Expect this as well before mid-July.

Linq has been a functional custom provider through GHL for a while now, and out of its popularity with our user base we decided to make it an option for Blank and HubSpot sources too! (While HubSpot supports custom providers, they don't natively work through the app marketplace)

With more clients joining agencies in CloseBot, it was time for a facelift. Though nothing functional has changed, the clients now land on their view of the agents page where they can more easily navigate the settings.

📈 -> we are again pushing focus onto our Analytics (reporting) features. This has been long in the works, but we are getting close! Once complete, this will allow you to customize the analytics shown on your dashboard, allow you to split test personas in measured A/B tests and more.

💻 -> The MCP released this week allows CloseBot to MCPs. The CloseBot MCP that allows you to connect tools like Claude, OpenAI, Viktor to CloseBot is still in the works. We expect this to be released mid-July.

📚 -> A general revamp on how our Knowledge base reads information and adding Google Drive and Notion as upload sources you can connect to your CloseBot knowledge base as LIVE knowledge base options! 🎉 Expect this as well before mid-July.

Finally your CloseBot Agents can utilize MCPs to quickly gain access to more tools. Currently supported natively are the Calendly and Cal(dot)com MCPs, with more MCPs coming within the next several weeks. You can also connect to a custom MCP.

Use these MCPs as a way to grant your agents access to other systems quickly instead of having to build a Custom Tool for each endpoint one-by-one.

Access these MCPs by going into your Job Flow and clicking the Custom Tool tab.

In situations where it would be helpful to allow your bot to share its thinking, referenced uploads and tool use with leads, you can now toggle on the optional setting within your Chat Widget settings.

We have this turned on within our home page because we want contacts to see what's going on behind the scenes! If you want to see what this looks like, try it out yourself by chatting with CloseBot on our home page.

This is also helpful for situations like support or demo experiences where you want to show the transparent information to the person engaging with the AI.

I'ts easier than ever to see which channels are available to connected sources. We auto-display all built in channels, and will begin to display custom channels here as well. Click on each to see setting for each.

You'll begin to see CloseBot-native channels for Blank sources too!

📈 -> are again pushing focus onto our Analytics (reporting) features. This has been long in the works, but we are getting close! Once complete, this will allow you to customize the analytics shown on your dashboard, allow you to split test personas in measured A/B tests and more.

💻 -> The MCP released this week allows CloseBot to MCPs. The CloseBot MCP that allows you to connect tools like Claude, OpenAI, Viktor to CloseBot is still in the works. We expect this to be released mid-July.

📚 -> A general revamp on how our Knowledge base reads information and adding Google Drive and Notion as upload sources you can connect to your CloseBot knowledge base as LIVE knowledge base options! 🎉 Expect this as well before mid-July.

We have redone all templates in the template library... all 66 of them. These all include a walkthrough video as well showing how they work!

Find these templates by clicking "Add Flow" within the Agents page to create a new job flow from one of these new templates.

This endpoint ingests your job flow file and validates it... returning any issues it detects.

When testing in the testing portal, You will see a visual display under the messages that shows you the follow-up cadence that would be followed at that time. Helpful to understand the full picture of outreach based on your follow-up settings.

Next week is a bigger week than normal for planned releases. We should finally have the following items released next week:

Finally we have a way for you all to see uptime. Anytime you're wondering, "Am I the only one experiencing this?", the status page will be the first place to go. You'll see a banner in the header of CloseBot if there's detected downtime, and you can navigate to the status page at any time via the HUB.

We will log details about incidents and resolution steps our team is taking for each downtime incident.

When you choose to import an exported bot file either on new job flow creation or overwriting an existing flow with an import, we will validate it for you to make sure it's a valid file first.

Some users get stuck not knowing what to put into the Job Information section, which your CloseBot agent with foundational knowledge. AI recipes solve that. Two sections can be auto-generated.

You'll soon find a new endpoint within our dev docs to do this check as well, which will help your agents (like Viktor, Manus, OpenClaw) troubleshoot flows they are making programmatically.

There's so much in the works for you all that we are excited about. I'm a broken record, but still in the queue is...

This is something we are extremely excited about. Now you can create different follow-up cadences and have Agent Node change cadences based on your instruction. Want a different follow-up cadence for warm vs. cold leads? Want to stop following up within an agent node without exiting if an appointment is booked? Follow-up states now let you do that! Learn more in the updated follow-up help article HERE.

The below video shows the updated settings area where you can create different follow-up states 👇

This image shows how you can explain to your agent node when it should change the follow-up state. When the follow-up state is changed, your follow-ups will happen on the new cadence 🤩 Cool right!?

You'll notice the tools sidebar now only has your list of custom tools... no ability to enable them globally. Any tool you want enabled must be enabled on the Agent Node level. Smart FAQ is now always on for nodes that are not the agent node.

Previous to now, CloseBot had and . With this change, we now permit you to have full edit access over the global prompt, including the headings. By default, nothing changes until you come in and edit. We've also given you more space to see what you're typing here and enabled @-mentioning variables.

We put great importance into making sure updates we make don't break existing bots. This is one of those improvements... you get greater control, and nothing you have in production performs any differently.

Now it's way easier to update job flow variables on sources within the Job Flow. Previously, you had to go to the Source Settings page to update these variable values.

Similarly, if you're doing testing in a job flow where the testing source is missing variable values, you see a helpful warning (click it to fast-navigate to fill in the variable values)

You can now have default values for source variables and descriptions. Descriptions display alongside the input area to assist the users filling them out. Default values can be helpful so they don't start out as blank.

We've been working quietly on Persona split testing... something we've always planned on doing, but just now able to implement. This will likely be coming next week, allowing you to assign two personas and split test to see which one compares better against your selected comparison metric, auto-selecting the winning persona.

MCPs, both CloseBot's MCP and support for MCPs as agent node tools should also be coming next week.

With all of this work on these above items, we've fallen behind on implementation for Google Drive knowledge base integration and the reporting module... but once we release all of this stuff next week our focus will again turn to those items!

Phew! How are we doing? 😅

Previously you could only filter for and tag rules. Now we give you the power to filter however you want!

For example...

only reply to contacts who have either the tag or and doesn't have the tag

There were updates this week to the job flow builder to make it operate faster for those with larger flows, but also a big improvement to the user interface to make it easier to build, and give you greater clarity in testing by showing "placeholder nodes".

We are constantly working on speed improvements. We have larger updates coming within the next couple of weeks with our reporting update that will bring more notable speed enhancements, but improvements were still made this week nonetheless!

This week our dev team had a hackathon... which means there was A LOT of code that happened... and almost none of it got pushed. We will review the results of the hackathon and spend the earlier part of next week pushing some things that we think you'll really like! Look for upcoming things like MCPs, job flow settings revamp, follow-up settings for agent nodes and more.

Now within Agent Node settings you can unlock 3 items...

🧠 Thinking Mode -> This allows your agent to think longer, displaying its , before replying. This will improve the output.

🏆 Max Mode -> This will make it so CloseBot uses the strongest models for your AI Provider instead of our defaults which are models that are optimized for cost & quality.

♾️ Unlimited -> This allows you to use custom tools with your agent, have unlimited prompt size and use an unlimited number of tools

Unlocking any of these messages sent with that node so they no longer cost 1 message each. We calculate token costs and pass the extra cost of usage on to you. Read more about that via message segments HERE.

Now instead of referencing CloseBot's standalone as , which can sound scary, we reference it as . This Blank source type allows you to chat via our standalone Chat Widget or connect via Webhook within Settings > Channels. No CRM? No problem 😉

Seeing all of your knowleget base items, chats, job flows together can be nice. It's all in one place. But it can also be overwhelming and cluttered.

We've made an update that allows you to a source. This auto-applies appropriate source filters as you navigate the different pages. You only see data related to that source.

There were a few issues from our big push that were fixed, including some tooling issues for agent node and back to back message sending not working well within our native chat widget. These items have been cleaned up and we feel great going in to the weekend.

We are finishing up the job flow template revamp today, so you will see those within your account next week. Next week the dev team is doing an internal hackathon, so you will be slower feature releases next week as we prioritize internal creativity and ideation.

After the hackathon, focus turns again to the following:

There's so much we have in store for you! Make sure you stay updated here on our weekly progress 🙌

Agent Node has exploded in popularity. We have even updated our own home page chat widget to use a single agent node and custom tools for booking our group demos conversationally 🤯 Learn more about how you can create your own custom tools to do whatever you want, wherever you want HERE.

Instead of referencing our standalone source as it's now referenced as . This Blank source has the chat widget channel as well as webhooks as a channel. In the future we will add more channels to this area for those who are using CloseBot standalone.

📝 Note -> CloseBot does not intend to be a CRM, but we want our users to have the power to use CloseBot by itself with a Blank source. See docs on our Blank source HERE.

Agent node is super new, and we are getting new data. We've made some changes that will deploy tonight to tweak things for improved performance. We also noticed some areas where custom tools UI felt clunky that we were able to fix as well as instances where Agent Node struggled with sending images. All fixes that will roll out tonight or over the weekend.

We have the changes ready to push for Agent Node superpower unlocking, but we want to test more before release. This will allow you to unlock greater tool count limits, prompt size, more powerful models, and thinking mode. You will be able to do this per Agent Node for fine-tuned pricing optimization.

Next week we will continue working on Reporting as well as Persona split testing, but also remain focused on watching stability of Agent Node. We have an unrivaled uptime, and we want to keep it that way 🔥

There's also work we are looking in to to get the UTM data collected by our sales pixel synced with HubSpot and HighLevel.