Embeddable Chatbot
complete
S
Simon Simon
Lead cost is around half the price for PPC ads on landing pages such as https://eco4.ecowarmgrants.com/eco4-scheme-uk-4516-2326654603 with a embded version for us.
Log In
B
Bryce DeCora
marked this post as
complete
Marking this as complete, please attend the Feature Launch Party as we launch this feature live this week!
It's currently in beta and performing very well.
Sign up for that event can be found here as well as a video walkthrough and more information.
Mike Nijs
Bryce DeCora ready for this!
David Aranovich
Is there a way to hide the fact that its closebot? (not show "closebot" in the pixel)
B
Bryce DeCora
David Aranovich there's not, but if they are smart enough to inspect the page and find CloseBot name in the pixel, they'll also find the API traffic to and from CloseBot to relay the messages... and if they are smart enough to do that, either they don't care that you're using CloseBot or they're not a worthwhile client for your agency anyways.
Just like "LeadConnector" is obviously "HighLevel" to anyone who can perform a google search
B
Bryce DeCora
Have some changes to how this will work based on user feedback and striving for both simplicity and power. It looks like this will probably be done this month:
Each source will have a closebot script to add to the site header. This code initially allows us to add the widgets based on your settings, but will also allow us to track visitor information like UTM data and pages viewed (bots will be able to ingest this information in Q2).
You will be able to add multiple different widgets within a source, setting up widget priority and page rules to determine which widgets get shown on which pages. Different widgets will show up as a new CHANNEL within your source channel filters so you can make different job flows apply to different widgets if you wanted.
Thinking indicator will work bi-directional. Thinking dots work both for humans typing (manual message) and bots thinking.
You will be able to put these widgets on Webhook sources as well for people that don't have HighLevel or HubSpot (CloseBot as a standalone). Thus, we will change the name of "Webhook Source" to "_________ Source" (undecided still). This _________ Source will still have the webhook endpoint for you to tie it into external apps we don't have a native integration with, but also allows you to put a chat widget on it.
You will be able to make any page change the behavior of the chat widget to be full page by putting the following div on the website:
<div id="cb-widget-container"></div>
We will make the widget fit inside the div element for you.
Also, the script you add to the business page will be white labeled. Something like:
This is our highest voted feature request. Lots of work has gone into the platform to make this possible. We appreciate your patience and hope you share the news with everyone!
Photo Viewer
View photos in a modal
undefined undefined
Bryce DeCora great work.
Mike Nijs
Bryce DeCora any screenshots for the embedded (non floating/but open) widget? Just excited lol 😅
B
Bryce DeCora
Mike Nijs:
Photo Viewer
View photos in a modal
B
Bryce DeCora
Andrew Vernon here's how this will work...
- Each source will have a closebot script to add to the site header. This tracking code will add the chat widget site wide and handle UTM tracking. UTM tracking will be available with the Reporting Module coming out in 5 weeks (likely several weeks after initial launch).
- You will be able to create multiple chat widgets. If you want to use a different widget on a particular page, you will add it via a DIV that's automatically going to drop it in the bottom right instead of the default EX. <div id="cb-widget-123"></div>
NOTE: Using the DIV technique, you will be able to add...
a) bottom right chat widget <div id="cb-widget-123"></div>
b) full div area embedded widget <div id="cb-widget-container-123"></div>
c) button open widget <div id="cb-widget-button-123"></div>
Custom callout via the DIV technique will automatically make it so the default widget in the bottom right is not used on that page.
B
Bryce DeCora
Showing multiple widgets. Each widget acts as its own Channel for that source so you can connect different ones to different Job Flows
Photo Viewer
View photos in a modal
Mike Nijs
Bryce DeCora this id is something we can choose/update after the widget is created? So it stays "white labeled"...
B
Bryce DeCora
Mike Nijs the id will be "cb-widget...". they won't know what cb is. If they are smart enough to reverse engineer and find the script, and research and find out what "cb" stands for, they probably aren't someone who's going to be a client of yours.
This will be something we generate that cannot be changed EX. "cb-widget-container-jk4534" if you wanted to place a full-div size embedded widget on a page in that div container.
Andrew Vernon
Bryce DeCora, superb, music to my ears!👂 🎵 ❤
B
Bryce DeCora
marked this post as
in progress
Mike Nijs
Bryce DeCora 👏🏼🥳🍕
B
Bryce DeCora
Merged in a post:
CloseBot Live Chat Widget
Andrew Vernon
GHL's chat widget is killing things for us (not in a good way). The reliability of the web hook going back and forth is very unstable and bringing down CloseBot as a product.
Some responses aren't being received back and forth causing clients to drop off. It would be great to have a CloseBot live chat widget that does away with the GHL one and data gets fed back info to GHL from CloseBot. Non responses are a real big issue for us.
B
Bryce DeCora
This isn't hard for us to do. Until lately the hardest part was determining how we implement it on the UX side. We now know how we will be handling it.
- You have your Sources
- You can go to source settings and click a tab for custom channels
- You can add a chat widget
- We will give you a script you can use to add that chat widget to your site. We will push all sent and received messages to GHL
This is one of our important additions slated for Q2. Worth noting the GHL chat widget reliability affects manually sent messages and workflow sent messages at the same frequency as it affects CloseBot (and other 3rd party) messages
Andrew Vernon
Bryce DeCora
This is a serious issue for us and I'm not sure your getting fed any actual figures. I lost a client this week because of missed live chat replies, and I’m currently having to manually monitor conversations to prevent drop-offs.
In one account we’ve had 2 failures in 7 conversations in 24 hours - that’s not sustainable, especially when clicks can cost $35+ in the PI/med neg space.
I appreciate that GHL reliability affects everything equally, but from our side the problem isn’t logging - it’s when the visitor doesn’t receive a reply and the enquiry is lost. That puts us in a difficult position with clients.
It’s actually pushed me back toward building agents directly in GHL for stability, even though I’d much rather be using CloseBot.
If the blocker has been UX/product structure, I’m more than happy to help. I ran a web design and digital agency for 18 years and can contribute from a real deployment perspective if that’s useful.
B
Bryce DeCora
Andrew Vernon I encourage you to raise this with the GHL support team as it's not something we can resolve. I have not heard this report from others. GHL goes through intermittent reliability issues with their widget and some sub-accounts seem to be less reliable than others, but overall users do not have much of a problem.
The issue described affects their internal AI the same it does us at scale. You will have the same number of dropped messages using the GHL chat widget if you use a 3rd party (CloseBot), manual setter replying within GHL, or GHL AI. The non-response rate will be the same for all of them.
On the UX side, we do not need assistance, we need to keep the team focused on the areas that ensure CloseBot remains a cutting edge leader on the AI side.
Andrew Vernon
Bryce DeCora
There’s 2 issues that I can see that are effecting front end delivery.
- CloseBot gets the message and replies. It goes to the GHL conversation panel and doesn’t get delivered to the user. I’ve tracked this one, it does but just doesn’t display, if you refresh the page then the message is there so seems to be some sort of caching related issue.
- The other one that I’m currently referring to is messages coming into GHL conversations panel but not reaching CloseBot to send a response.
B
Bryce DeCora
Andrew Vernon correct.
- This same problem happens with GHL's AI, or with humans sending messages through the GHL chat widget. It's not isolated to 3rd parties.
- This same problem happens with GHL's AI, or with humans sending messages through the GHL chat widget. It's not isolated to 3rd parties. This is why you'll constantly see similar posts in the GHL group about "why didn't my AI respond?"
My point is, switching to use the internal AI to try to combat this will not help. I agree, it would be best for CloseBot to have our own chat widget. This is why it's on Q2.
Andrew Vernon
Bryce DeCora I will be keeping my fingers, toes and eyes crossed 🤪 hopefully for an early Q2 launch. This update will get you noticed if you're saying GHL also get same errors. Appreciate the hard work you guys do.
Andrew Vernon
Bryce DeCora nor sure if this is in the plan for the chat widget. There’s a big disconnect with the GHL chat widget that doesn’t have UTM tracking code unless you use a form to capture that data. This would be a game changer for agencies. It’s always the first thing we get asked. Can the chat be tracked back to the add that a client clicked through from.
Carlo Yap
looking fwd to having this as an option vs the chat widget
B
Bryce DeCora
marked this post as
planned
B
Bryce DeCora
marked this post as
open
Moved back to open. This is a Q2 item as we focus heavily on reporting in Q1
Load More
→