Part of AI chatbot for business
Visitors stop leaving without asking
One script tag puts a chat bubble on your site. It is not a separate bot with its own settings — it is the same assistant, with the same knowledge of your prices and services, that answers your phone.
- One script tag
- Streams replies as it types
- Opens the conversation itself
Chat on your website, answered by the same assistant
- Installs with a single script tag; renders in a Shadow DOM so it cannot collide with your site’s styles.
- Streams replies token by token rather than making the visitor wait for a finished paragraph.
- Opens the conversation itself, in the assistant’s own voice and the right language — not a configured greeting string.
- Takes colours, title and position from data attributes, or runs headless behind your own interface.
- Saves a number a visitor gives on that visitor's own record, as an unverified callback if you already hold it for someone else, so your team can follow up. It never connects the visitor to another customer.
- Serves every reply from the same knowledge base your phone and WhatsApp read from — correct a price once and all three change together.
- Runs a rate limit per sender and per tenant, with a public-demo guard on origin, so a stress test or a bot cannot run up your usage.
- Can hand a conversation to the sales pipeline the same way any other channel does, once it ends in an outcome you have mapped to a column.
Set up once, then it runs
- Paste the script tag into your site template.
- The widget opens a streaming session against the same brain as every other channel.
- A phone number a visitor gives mid-conversation is passed to your team as a contact to follow up on. A number typed on website chat is saved on that visitor's own record, as an unverified callback if it is a number you already hold for someone else. It never connects the visitor to another customer. A website visit is not connected to an existing customer automatically.
- There is also a "Talk to us" voice button that runs a live browser voice conversation through the identical pipeline as a phone call.
- A conversation that ends in a mapped outcome can open a deal on your sales pipeline automatically, the same as any other channel.
Want to see this doing your job, with your prices?
Ask on WhatsAppWhat the numbers actually say
Speed is the whole argument for a website chatbot, and the research on speed is blunt about the gap between what people expect and what most businesses deliver. Sprout Social’s 2026 pulse survey found 84% of consumers say the speed of a business’s response changes how they see the brand afterward — not eventually, immediately, in the same interaction. A widget that streams its first token in under a second and a widget that shows a spinner for four seconds are not competing on the same axis as “smart”; they are competing on whether the visitor is still there when the answer arrives.
The other number worth sitting with is about what a visitor does before they ever open the chat bubble at all. Zendesk’s own customer-experience research puts the share of people who would rather solve something themselves — search, read, find the answer — at 67%, and that number is the entire argument for pairing a website assistant with a real knowledge base rather than a scripted FAQ widget: the visitor who typed a question into Google and landed on your pricing page has already tried self-service once and failed, which is exactly the moment a chat bubble that actually knows your prices earns its place.
What the widget explicitly is not is a lead-capture form with better manners. It streams from the identical brain answering your phone, which is the part that is easy to promise and hard to build: ask it the same question by voice and by chat and the two answers should agree, because they come from one knowledge base rather than two people’s idea of what the FAQ should say. The trade a business makes for that consistency is candour about where webchat stops — it is assistant-only, with no human composer, which is a deliberate line rather than a missing feature, and the page says so rather than letting a business discover it mid-conversation.
Installation is worth being specific about, because “one script tag” is a claim a lot of vendors make and not all of them mean it the same way. Here it means literally one <script> line pasted into a site template — no plugin to install, no build step to run, no account to connect before the widget renders. The Shadow DOM boundary is what makes that safe to do on an existing site: the widget’s own styles cannot leak out and collide with a theme, and a theme’s styles cannot leak in and break the widget, which is the specific failure mode that makes most embedded widgets fragile on a site they were not designed alongside.
The headless option exists for the opposite reason — a team that does not want Kooday’s default bubble at all, but does want the same streaming session, the same knowledge base and the same contact-unification behind their own interface. That is a real trade: it needs developer time the default widget does not, in exchange for full control over how the conversation looks. Most businesses use the default widget; the option exists for the ones that specifically should not.
What a website visitor gets, by channel
| Capability | Website chat | Voice button on the same page |
|---|---|---|
| Answers from | The same knowledge base as phone and WhatsApp | The same knowledge base as phone and WhatsApp |
| Reply style | Streams token by token | Live speech, same pipeline as a phone call |
| Human takeover | None — assistant-only, and the pane says so | None — same as chat |
| File upload | Not available | Not applicable |
| Install | One script tag, or headless behind your own UI | Bundled with the same script tag |
All figures resolved from Kooday’s own product; this table is not a competitor comparison — see the FAQ for how webchat differs from a scripted widget.
Figures worth checking, not taking our word for
- 84% of consumers say response speed changes how they perceive a brand afterward — Sprout Social’s own 2026 pulse survey Sprout Social — "The State of Social Media in 2026" · read 2026-09-09
- 67% of customers would rather resolve something themselves than contact a person — Zendesk’s own customer-experience research Zendesk — self-service research · read 2026-09-09
- 1 script tag is the entire install — no plugin, no build step, renders in a Shadow DOM so it cannot collide with your site’s CSS Kooday
- ₹99/mo Kooday’s entry plan, which includes website chat and website voice from day one Kooday
- Token by token is how replies stream — a visitor sees the answer forming rather than waiting on a finished paragraph Kooday
- 2 modes a styled widget out of the box via data attributes, or a fully headless session behind your own interface Kooday
The things this does not do
Every product page in this market lists capabilities. This is the other half. If one of these is a dealbreaker, we would much rather you found out on this page than in month two.
- Website chat is assistant-only today. There is no human composer — you cannot step into a webchat thread the way you can on WhatsApp.
- There is no file upload on webchat.
- Rate limits apply per sender and per tenant, and there is a public-demo guard on origin.
- There is no visual flow builder here either — you write what it should say, in plain language, the same as every other channel. If a boxes-and-arrows canvas is what you are shopping for, we are not it.
What people ask us
Will it match my site’s design?
Colours, title and position are configurable, and the Shadow DOM means it will not inherit or break your existing CSS. For full control there is a headless mode that exposes the same session to your own UI.
Does it know the same things as the phone assistant?
Yes — same brain, same knowledge base, same tools. Answering differently by channel is the failure mode this design exists to prevent.
Can a person take over a website chat?
Not on website chat — the pane is read-only and says so. You can take over on WhatsApp, Instagram and Messenger; webchat is the one channel where the assistant is on its own, and we would rather say that than let you discover it during a difficult conversation.
How is this different from a scripted FAQ widget?
A scripted widget answers from whatever the person configuring it typed in advance, and drifts the moment a price changes. This one answers from the same knowledge base your phone assistant reads from, live, so correcting a price once corrects it everywhere.
Do I need developer time to install it?
One script tag, pasted into your site template — that is the entire install for the default widget. Headless mode, where you build your own interface against the same session, is the option that needs developer time, and it is there specifically for teams that want it.
Does it slow my site down?
It runs in a Shadow DOM specifically so it cannot collide with your site’s styles or scripts, and replies stream rather than blocking on a full response. That is a deliberate design choice, not a claim we can make about every possible hosting setup.
Can it capture a lead before answering everything?
Yes — your assistant asks for a name and a number when it is useful, and the number is passed to your team as a contact to follow up on. It does not gate the conversation behind a form first. That ordering is deliberate: a visitor who has to fill in a form before getting an answer is a visitor who often leaves before finishing the form. The number is a way for your team to reach them; it does not by itself connect the visitor to their earlier conversations.
Does it work the same for a returning visitor?
The same browser is a returning visitor, so they pick up where they left off. A returning customer who types the number you already hold for them is taken as a contact for your team to follow up on, but the assistant does not confirm their bookings or the name you hold for them on the website. Their website visit stays a separate record. It is not connected to an existing customer automatically, and a later WhatsApp message or call from that number is recorded under the sender's own customer record.
What it works alongside
- WhatsApp A WhatsApp chatbot on your WhatsApp Business number that answers text and voice notes immediately, stays inside Meta’s 24-hour window, and hands the thread to you when it should.
- AI phone agent An assistant that answers your business phone on the first ring, in the caller’s own language, and leaves you a transcript, a summary and a contact record.
- Knowledge base Upload documents or paste text and the assistant answers from them, in your words, across every channel. Correct it once and every channel changes.
If this sounds like your week
Would this work for your business?
Message us and say what your week actually looks like. You will be talking to our own assistant — the thing this page describes, doing the job on our side of the conversation.
Plans from ₹99/month.