The Website Chat Widget: What the Visitor Sees and What You Set in the CRM
Most websites treat the chat bubble in the corner as a decoration. It is installed, it opens, it asks how it can help, and then it becomes a second inbox nobody reads. The interesting part is not the bubble. It is the settings behind it and where the answers to those questions end up.
In Firmspace the website chat is not a separate tool. It is one of the channels of the same conversation inbox that already holds Telegram, Viber, WhatsApp, SMS and mail. What makes it different from every other channel is the only thing that matters to a web visitor: he does not have to go anywhere. He is already on the page, and the conversation starts where he is standing.
A website chat is usually judged by how quickly it answers. Building it that way is a mistake. A visitor may not write at all: he looks at the price list, reads two help pages and leaves. The channel should make three routes out of that silence possible — a ready answer, a person, or a messenger the visitor already uses.
Inside one window there are three ways to reach someone, and the visitor does not have to choose correctly at the start. The first is a short list of common questions: the widget opens with four of them, taken from the platform's question base and shown in the visitor's language. Tapping one sends it as an ordinary message, so the conversation keeps its context instead of restarting.
The second route is the public AI assistant. It answers from the platform's own knowledge base — what the product does, which modules exist, how plans work — and it is allowed to quote prices, recalculated into the visitor's currency for the language he is reading the site in. The knowledge here is about the platform, not about the firm's internal data: an outsider must never be able to ask a public window what is written in a client's card.
The bot is kept on a leash, and the size of the leash is a setting. There is a limit per visitor, a daily ceiling for the whole site and a fallback for the moment the model is unavailable, over quota or switched off: then the widget answers from prepared, keyword-matched texts instead. A public page is not the place to find out at 3 a.m. that an API key expired.
The third route is the messenger the visitor already has on his phone. The window shows Telegram, Viber and WhatsApp buttons, but only for the channels the firm has actually connected and configured — Viber, for example, will not appear until its account address is known. A button that leads nowhere is worse than no button at all.
Contact capture happens where the visitor is, not before he has said anything. The form appears when nobody is on duty or when the bot has no answer, and accepts either an e-mail address or a phone number. The value is validated rather than trusted: an address-like string or free text is rejected, and the visitor is asked to check what he typed.
The second route has a hierarchy, and the human is always above the bot. The bot can be switched off entirely for the channel: then every message simply waits for a person. Even with the bot on, it stays quiet while a colleague has answered within the last half hour. An assistant that talks over a manager who is already handling the conversation is the fastest way to lose a customer.
The visitor can attach a file, which is often the whole point: a photo of a defect, a PDF of an order, a screenshot of an error. Images, documents, audio and video are accepted; archives and executable files are not, because a public endpoint that accepts anything is an invitation. The file goes into the firm's storage and appears in the conversation exactly like an attachment from a messenger.
The visitor can also rate the answer he received: one thumbs up or one thumbs down per reply, and only on messages written by the bot. This is not decoration for a review page. A thumbs down immediately reaches the owner with the question and the answer that failed, in the team's Telegram, together with a plain instruction to fill the gap in the knowledge base. That is the cheapest possible way to find out what your website visitors keep asking about.
On the firm's side the whole channel is configured in one place, without touching the site again: the window title, the greeting, the accent colour, the working hours with a day range and a time-zone offset, an optional call-to-action button with a link, and the switch for the answer bot. The default accent is the platform's own lime, so a new channel already looks like the product rather than like a default blue widget.
Working hours deserve their own paragraph, because they are computed honestly. The widget counts time in the firm's time zone, not the visitor's, using the offset from the settings. A visitor from another city at 2 a.m. should not read a green dot claiming that someone is here, and the owner should not have to remember to switch a status by hand before going home.
The visitor's side of the widget is deliberately small so that it can be written down in full. One bubble in the corner and one window: the first tap opens it, the second closes it. A tap outside the window closes the conversation, which is the behaviour people expect from every messenger on their phone. The window itself lives in an isolated part of the page, so the site's own styles cannot break the buttons inside it, and there is nothing to coordinate with the theme of the site beyond the accent colour.
One question decides whether a channel like this works: who answers. A widget plus a bot plus three messenger buttons can still produce a queue nobody owns. The honest fix is a rota rather than a cleverer bot: someone on duty during the stated hours, a bot that covers the rest without pretending to be a person, and a request for a contact when the question is more than the knowledge base can carry.
A chat on a website is a promise that the firm is reachable where the customer already is. The widget itself is a few dozen kilobytes and one script tag; the work is in the settings — what it says, when it is silent, in whose time zone it counts, and which unanswered questions it reports back. Everything else is a bubble in the corner.