2.4 KB loader
Gzipped. Smallest in the category. Lazy-loads the chat UI only when a visitor opens the bubble.
Drop a single line on your site. AI answers fast. Conversations route to your team on the endpoint they already use — and continue on WhatsApp or Telegram if the visitor leaves.
Most chat widgets ship 200 KB of JS, block render, and pollute your CSP. This one is 2.4 KB on first load, lazy-loads the UI only on bubble click, and runs on a strict CSP.
Gzipped. Smallest in the category. Lazy-loads the chat UI only when a visitor opens the bubble.
Documented CSP directives, signed loader, no inline scripts on the host page. Buyers' security teams can sign off without exceptions.
Keyboard navigable, focus-trapped chat panel, reduced-motion respected, ARIA-labelled controls.
Colors, copy, position, triggers, and proactive greeting all configurable.
Routine questions get answered in the widget within milliseconds, with cited sources.
Long-running conversations can move to WhatsApp, Telegram, or LINE — same thread, same context, no lost state.
Even when the customer stays in the widget, agents can reply from their preferred endpoint without opening a dashboard.
The loader is 2.4 KB gzipped. The chat UI is lazy-loaded only on bubble click, so the initial page weight stays minimal.
Yes. The widget ships its own assets, uses a strict CSP-friendly bootstrap, and documents the directives buyers need to add. Configuration guidance is in the secure widget resource.
Yes. Conversations started on the website can hand off to WhatsApp Cloud API, Telegram, LINE, the PWA, or a custom endpoint. The Wake transcript carries forward.
Yes. Brand colors, position, copy, and triggers are configurable. The widget never leaks host-page state and respects reduced-motion and keyboard navigation.
The interactive widget requires JavaScript. Critical SEO content on your pages is independent of the widget — the widget enhances the page, doesn't replace it.
Bring a staging URL. We'll embed the loader live and route a real customer message through to your preferred endpoint.