BloomDesk Chatbot places a chat widget on your WordPress site. Visitors send messages to BloomDesk, where a conversation can be handled by an AI assistant or a human operator. The site administrator pastes a SaaS webhook URL in the plugin settings. The webhook token stays on the server; the browser only talks to your own site.
The widget can be added automatically in the footer or with the [bloomdesk_chatbot] shortcode. Existing content that uses [bloomtech_chatbot] keeps working.
This plugin does not work without an external chat service. By saving a SaaS webhook URL and using the widget, you connect the site to that service.
BloomDesk (required for chat)
The plugin calls BloomDesk when an administrator has saved a SaaS webhook URL and a visitor sends a message, the widget checks for new messages, or the visitor confirms or declines a proposal.
Data sent to BloomDesk:
Origin header set to this site’s address (added by the plugin on the server)externalSessionId, afterId, and the polling modeData received: the AI or operator reply, and session metadata needed to continue the conversation.
Google reCAPTCHA (only when an administrator turns it on and saves a site key)
When reCAPTCHA is enabled, the visitor’s browser loads https://www.google.com/recaptcha/api.js and shows the checkbox. Google receives the visitor’s IP address and interaction data under Google’s own policy. After the visitor completes the checkbox, this site’s server sends the reCAPTCHA token and the visitor’s IP address (REMOTE_ADDR) to https://www.google.com/recaptcha/api/siteverify.
JavaScript and CSS in this plugin are written by hand.
assets/js/widget.js is the human-readable source and runtime file. It is not compiled, bundled, or minified. There is no build step. Edit that file directly.
The other scripts in assets/js/ (backend-connection.js, admin.js, btcb-defaults.js, appearance-preview.js, recaptcha.js, translations.js, dashboard-hero.js) and the stylesheets in assets/css/ are also the original source.