Visitors expect a floating bubble in the bottom right of a website. The design language has been stable for a decade; people know what the bubble means, they know how to dismiss it, and they know it is the place they go when they have a question. The bubble itself is not the problem with most chatbots. The problem is what happens after the click: a scripted decision tree, a hand-off to a contact form, or a generic LLM with no idea what site it is on. The bubble keeps its promise of availability and immediately breaks the promise of knowing anything.

SleekAI's floating-button mode keeps the familiar shape and replaces the brain. The bubble looks like the bubble visitors expect. When opened, it talks to a model the site owner configured (OpenAI, Anthropic, Google, OpenRouter) with WordPress data mapped in: the visitor's current page, the product they are looking at, the section they are on, the role they have, the cart they are carrying. None of that is reachable by an external chatbot vendor without integration code. SleekAI reads it from the database directly because it is a WordPress plugin.

The familiar bubble carries display rules underneath. The same Display tab that controls inline embeds and popups controls the floating button: scope by post type, URL pattern, taxonomy term, logged-in state, or user role. You can hide the button on checkout, only show it on docs, switch it on for members, or run a different bot on Spanish pages. All of that is settings UI, not theme code. The bubble is the same bubble; the difference is the configurability of what it does and where it appears.

There is a recurring debate about whether the floating bubble has had its day. The argument against it is that visitors are trained to dismiss it, that it covers content, and that nobody opens it on purpose. The argument has the diagnosis wrong.

Visitors dismiss floating bubbles when the bubble carries no signal that opening it would help. They open bubbles that signal awareness of the page they are on. A bubble that says 'Stuck on the size guide' on a product page is opened more often than a bubble that says 'Have a question'.

The bubble shape is not the issue; the empty bubble is the issue. SleekAI's floating-button mode treats the bubble as a context-aware surface rather than a default greeting. The bubble can change its label, its badge, its initial message, and its tone per page, per post type, per role, or per any custom variable.

Combined with display conditions that hide the bubble where it does not fit (checkout, login, account pages) and show it where it does (product pages, docs, pricing), the open rate moves materially. The familiar shape is the right default because it is what visitors expect; the brain behind it is what makes the bubble actually useful. Keeping the shape and replacing the brain is the upgrade most floating chats need.