This week was the last week focused solely on bug fixes. You'll see there have been many changes:

You'll notice a change in the conversations UI that allows you to clearly see how many objectives the Agent is working on and which nodes with clear icons. Hover over icons to see more information about them. You will also clearly be able to see booked appointments from within the UI and the time taken to generate a response. You'll also see icons for each knowledge library item that was pulled in for reference.

More changes coming to this screen next week will include the ability to click on icons to hyperlink to appropriate logs for quicker troubleshooting and more details in the section (like time the message was sent and estimated profit based on re-billing settings). You will also see follow-ups displayed here with the ability to modify and delete follow-up times that are scheduled.

The chat widget is now added as a channel. This refers to the SMS Widget that HighLevel supports. When a message comes in on this channel, we will responds via SMS.

Some users wish to allow Custom Scenarios to jumpt to a booking that has already been booked previously. Remember, by default Custom Scenarios can be entered multiple times. This allows you to let a contact book multiple appointments to the same calendar. Common for repeat customers.

Follow-ups now sound a lot less awkward. Next week we will release an update that allows you to edit for follow-ups, but this was the first step. It has taken so long for us to release this feature because of our hard mandate on no new features until we reached stability.

The client portal was previously showing these items in the sidebar that should not have been displayed.

The knowledge library is now much more reliable and we are open to feedback! We display when items are loading and when they have finished loading.

We now give you the ability to book your onboarding call(s) from within the CloseBot interface. This includes rescheduling instances of you missing your onboarding call.

The team has put in hard work over the past couple of weeks on general platform stability, but also some user interface updates. Many of the changes we are working on now are things that you don't see, but feel. You'll feel more and more that the platform operates faster and more reliably both for you and clients.

The knowledge base page got a much needed re-vamp. You'll see better filtering available for your knowledge base documents as well as column sorting. You'll also notice a column that shows the status of uploads.

- This means this item is still in process of being loaded into the AI memory

- This means this website is in the process of being scraped

- Indexed files have been loaded to memory and are ready to be attached to source(s)

Table views can now be sorted by column type. This is helpful if you're searching for recently modified job flows, for example.

More cleanup has gone into client views, removing items that they should not see (like knowledge base items that they aren't attached to).

To help with our push for stability, we have added some brand new conversation logs to show exact HTTP requests and responses. While we are still working on the UI for the logs, we wanted to push out quickly to help solve some of our small persistent bugs. This will be big for support but also for you!

With the new release on Wednesday, July 2nd, we have unlocked many of the screens for usage billing and re-billing! What this means for you:

You can now attach your personal/business Stripe account to CloseBot for re-billing purposes (so we can bill on your behalf). To do this go to Settings -> Agency -> Rebilling and :

This will bring up the Stripe connect flow:

With that set up, you can now set the re-bill rate for clients under the Rebilling tab. Once that is set up, you will be able to turn on re-billing on a source by source basis! To do this, go to a the sources page, click the three dots on a source you want to re-bill, and select :

Under the tab, you can find the option to turn on Re-Billing:

After enabling, press the button, this will start the work on our end to create a new customer in your Stripe. When completed, you can choose to open the settings again to set payment methods or buy credits, or save those steps for the client if they are paying for a seat. It will look like this for either of you:

With this view, either you or your clients can add payment methods and set auto reload rates.

While you won't have access to re-billing, the wallet page has had some updates too so you can put in new cards, and put in auto reload balances to enable overbilling if you would like (a billing option available if you go over your monthly limits). Overbilling is only available for responses, and each response will be billed at 2x the rate of your prepaid per-response cost ($0.08 per message on a free account):

We have also added a transaction table to help you navigate transactions for your organization:

Many new changes with this update! We will be watching the new billing items closely but if you find something that could be an error please hop into support and let us know!

CloseBot launched this update just 16 days ago... and the adoption has been overwhelming. In just 16 days CloseBot V2 is already handling about 50% the volume CloseBot Classic was at its peak. This is impressive considering it took CloseBot Classic 2 years to reach this peak. 2 years to slowly scale infrastructure, support, stability, etc.

Since launch we have put a hard stop on new features until we are happy with the platform trust. This means our team is living in support, sifting through user messages to separate dev issues from new-user confusion and implementing UI/UX (front end) updates to alleviate user confusion issues and backend fixes to improve reliability.

The next feature we will be releasing is re-billing. And this is still expected to be released this week. The rest of the features that can be found on our roadmap HERE will start to roll out more regularly after we have attained zero active support tickets in the developer inbox... this means we have successfully reached our stability goal.

We now have users migrating from CloseBot Classic... some coming from the ZappyChat acquistion... and some coming in to CloseBot for the first time. That results in a lot of support inquiries. We now have the following set up:

| -> you will always engage with the AI first when you're chatting with support. Our AI currently resolves 55% of all chats without ever needing a human. Our goal is to get this to 70%.

| -> If the AI can't help you, we get a human involved. We have doubled our human support staff and they are constantly being trained so they will be experts in the UI and optimization of CloseBot

| -> These are the support team who know about the fine details of how things in CloseBot work. Some of them may even have some dev experience. The Level 1 team elevates chats to this level if they are unsure how to diagnose and fix an issue.

| -> Level 2 may elevate issues to the developers if they believe a fix needs to be implemented to resolve an issue. Ideally, our platform would have zero dev issues and our level 1 and 2 support team would be trained well enough to tackle 100% of inquiries... but there are always areas to improve!

CloseBot V2 is now known as CloseBot and V1 is known as CloseBot Classic. Both continue to work, but the registration page for V1 is now closed. Welcome to your new home!

We have not only been working hard on the product, but also the documentation and other support processes to make sure you win.

Help Docs

Office hours schedule

V1 users need a streamlined way to migrate to V2. This has been a large undertaking, since V2 is a complete re-build of the platform, bringing much greater capability. However, the migration plan has now been established and is in testing.

Read more HERE or check out the video walkthrough below

- usernames are used for leaderboard display in case you'd like to remain anonymous

- Personas now have the carousel view and a new table view that's searchable

- Menu for job flows that allows you to duplicate, test and other settings for agent job flows

- More intuitive UI for group creation as well as the ability to create groups from within the job flow wizard

- Each objective part has its own advanced settings

- The delay action that waits for the value of a field in your source to be filled out now moves on to the next action in line automatically instead of checking only when a new message comes in

- Now you'll see an improved testing UI complete with an AI summary of the Agent's thought process

Feature Updates: