It will not slow your store down
A chat widget that costs a store its page speed costs it more in lost shoppers than it ever earns in chats. So the script you add to your site is 3.62 KB gzipped, measured on every build, and our build refuses to ship it if it grows past its budget. The conversation itself, 30.90 KB, downloads only when a shopper opens the chat. Visitors who never open it pay for the button and nothing else.
An AI chatbot for your website, measured before it is promised
An AI chatbot for your website should not cost the site its page speed. The measured numbers are below their budgets, and we publish both rather than only the flattering one. A budget quoted as a measurement is not a measurement, and the gap is what tells you whether the ceiling is real.
-
3.62 KB
loader, gzipped
Budget 8 KB, enforced in CI. This is the measured figure from the current build.
-
3.62 KB
everything before the panel opens
Budget 45 KB. The loader is all that loads; the panel is fetched on first open.
-
0 px
of your layout reserved
The launcher is fixed-position and takes no space in your page's flow, so it cannot push anything.
-
0 KB
of CSS in your page
Every style lives inside a shadow root. Your stylesheet cannot leak in and ours cannot leak out.
What else it does
It fits every screen
On a desktop the chat opens as a panel in the corner you choose, or as a centred window. On a phone it becomes the whole screen, sized to the part of the screen the shopper can actually see, so the keyboard never covers the message box. The page behind stops scrolling while the chat is open, and the message box uses a text size that stops iPhones zooming in.
It speaks your shoppers' language
Shoppers can choose English, Tamil, Hindi, Telugu, Kannada, Malayalam, Marathi, Bengali, Gujarati or Punjabi, and the assistant answers in that language and its own script. Someone who types Tamil in English letters is answered the way they wrote. Indian-language keyboards that confirm a word with Enter no longer send half a word: the message box waits until the word is finished.
It remembers the conversation
A shopper who asks about a product and then opens the next page finds the conversation still there, even in a new tab. The chat is kept for as long as the conversation is active and cleared when the shopper ends it. A shopper can also download the transcript.
It looks like your store
Four design styles, your colours, your logo, your greeting, the corner it sits in and how far from the edge. If your brand colour is too pale for white text, the widget picks readable text by itself. The AI disclosure, “You're chatting with an AI assistant”, always sits in the header, before the first reply, as the EU AI Act expects.
It behaves well
When a message fails to send, it goes back into the box with a Try again button. When a shopper scrolls up to reread an answer, the chat stops pulling them down and offers a Latest button instead. Screen readers hear each finished reply once. If your team replies while the chat is closed, the chat button shows a dot.
Common questions about the widget
What it weighs, what it touches, and what it will not do to your page.
How big is the widget?
3.62 KB before it opens; 30.90 KB when a shopper opens it.
Which languages does it support?
English and nine Indian languages.
Does it work on mobile?
Yes: full screen on phones, sized around the on-screen keyboard.
Will it inherit or break my site's CSS?
No. The widget renders inside a shadow DOM, so your stylesheet cannot reach into it and its styles cannot leak out. That isolation is why one set of markup renders correctly on every merchant's site regardless of their theme.
How do I change the colours and wording?
In the console, under Appearance. Everything themeable is a CSS variable the widget reads at load, so a change takes effect on the next page load without touching your site or redeploying anything.
Why does the chat say “Something went wrong”?
Almost always because the site it is running on is not in your allowed-origins list. The chat refuses any request from an origin you have not allowed, and it does not explain why to the page: telling an unknown site that its widget ID is valid would help someone probing. Add the exact origin, including https:// and any www, under Install.
One script tag, on your store
The same afternoon, from the tag to the first traced sale. The quickstart has the tag, the origin allowlist and the exact CSP directives.