Configuring Your Ebbot Chat Widget — Settings
Learn how to control when, where, and how your Ebbot chat widget appears — across desktop, mobile, specific pages, and multiple subdomains.
Once the widget looks the part, it's time to make it act the part.
If you haven't set up the look of your widget yet, start with the Styling guide first — then come back here. Settings is where you control the behavior of the widget: when it shows, where it sits, how it opens, and how it handles navigation on both desktop and mobile.
To get there: Chat widget → Settings
🔌 Disable Chat Widget
Sometimes you just need the bot off. Maintenance window, a specific campaign page, a section of your site where a chatbot just doesn't belong — whatever the reason, the Disable chat widget toggle handles it cleanly. Flip it to Yes and the widget disappears entirely. No fuss.
But here's where it gets clever: you don't have to disable the widget globally. By combining this setting with the Theme Manager, you can disable the widget on specific pages while keeping it live everywhere else.
For example — say your bot lives on www.ebbot.com and you want it there on most pages, but not on www.ebbot.com/solutions/telecom. Head into the Theme Manager (Chat widget → Styling → Theme Management), create a theme scoped to that URL using a starts:: or contains:: rule, and enable Disable chat widget for that theme only. The bot stays active site-wide, just silently absent on the pages you've excluded.
🖥️ Desktop Settings
Switch to the Desktop tab to control how the widget behaves on larger screens.
Chat client fixed Keep this on Yes. It means the widget stays anchored in its corner while the user scrolls. Turning it off makes it scroll with the page — which is almost never what you want.
Chat client position Place the widget in any corner of the screen using the Left/Right and Top/Bottom options. Right + Bottom is the classic default, but if something else suits your layout better, it's yours to configure.
Chat widget position offset Fine-tune the exact pixel distance from the edges. Default is 10px on both right and bottom. Got a cookie banner or a floating element crowding the corner? Nudge the widget out of the way here.
Open chat automatically on page load? Set to Yes and the chat widget opens the moment someone lands on the page — no click required. Powerful for high-intent pages like pricing or contact. Use it with intention though; nobody wants a chatbot launching at them on every single page they visit.
Disable chat widget pop-up after internal link on desktop mode When users click through pages on your site, the widget would normally re-pop on each load. Enable this and it won't. The chat stays in whatever state the user left it in — open or closed — rather than forcing itself back into view every time they navigate. Keeps the experience smooth and unintrusive.
📱 Mobile Settings
The Mobile tab covers the same positioning logic as desktop, with a few additions specific to smaller screens.
Chat client mobile size (Coverage) Controls how much of the screen the widget covers when open on mobile. Default is 90% — big enough to be fully usable, small enough that users can still see they're on a website.
Disable pop after internal link on mobile portrait view Same idea as the desktop version above, but specifically for portrait mode. If a user is browsing your site upright on their phone and tapping between pages, this stops the widget from re-popping on every navigation. Highly recommended for content-heavy or multi-page sites.
Disable pop after internal link on mobile landscape view Same thing, but for landscape orientation — useful for tablet users or anyone browsing sideways. Toggle both portrait and landscape independently depending on how your audience typically uses your site.
These two settings together make a real difference on mobile. Without them, the widget can feel like it's constantly demanding attention. With them, it feels like a natural part of the page.
🌐 Subdomain Manager — What It Is and When You Need It
Also available under Chat widget settings is the Subdomain Manager — a more technical feature aimed at teams running Ebbot across multiple subdomains.
The short version: by default, a chat session started on shop.yourdomain.com won't carry over when the user moves to support.yourdomain.com. The Subdomain Manager fixes that. Once configured, sessions stay alive across subdomains, so the conversation doesn't reset just because the URL changed.
Setup involves three steps: creating a CNAME record in your DNS pointing to ebbot.eu, registering the subdomain in the manager with an Alias and full Path, then adding an apiUrl parameter to your widget script.
👉 For the full technical walkthrough, head to the Subdomain Manager documentation.
💡 Also in Settings — General Tab
The General tab is home to a handful of additional toggles worth knowing about: message typing delays, character limits per conversation status, read receipts for agents and clients, sound notifications, and GPT message rating. Most of these are fine to leave at defaults when you're starting out — but if you're tuning the feel of conversations or troubleshooting specific behaviours, this is where you dig in.