A chat on a company's homepage could answer every visitor who arrives with a question, in the company's own voice, at any hour and in any language. Most companies do not put one there. The reason is not the cost. It is the fear of a single wrong answer. A support chat that invents a return policy, quotes a price the company never set, or claims a feature that does not exist is worse than no chat at all, because the customer believed it and acted on it. That fear is why the homepage chat is still rare.
The chat that ships on a Giant Context site is built to earn that place. It draws its answers only from the knowledge the site already publishes. Every reply carries the sources it used. It speaks in the company's voice and answers in the visitor's language. A grounded chat answers from what a business already publishes and declines where that knowledge runs out. That combination is what makes it safe to leave facing the public.
A grounded chat answers from what a business already publishes and declines where that knowledge runs out.
Every answer the chat gives is drawn from the company's own published material and comes with its sources attached. When it replies from a published article, it returns links to what it used, so that the visitor can open the source and the company can see where the answer came from. An answer with a citation is one a person can check. An answer without one asks a stranger to take a claim on faith, which a public chat has no standing to do.
It speaks in the company's voice rather than a generic one. The same brand voice the rest of the platform writes from is handed to the chat. The reply a visitor reads is the business's own, not a model's default. It also answers in the visitor's own language. A question asked in French comes back in French, one in Spanish in Spanish.
All of that is safe to leave on a company's homepage because of a single guarantee. The chat will not answer past what its knowledge supports. A language model, left alone, is fluent by default. Hand it a thin or off-topic passage and it will still produce a confident, well-formed paragraph, because producing one is what it does. Softer instructions do not reliably stop that. So the restraint here is not a request made of the model. It is a decision made before the model is asked to write anything. The retrieved material is scored for how well it covers the question. Only when the match is strong enough does the answer path run. When it is not, a different path runs, the one that says there is not enough to go on. The restraint is in the routing, not in the model's good intentions. The refusal is localized too. A visitor who reaches the limit of what the knowledge covers is told as much in the language they were speaking.
None of this is a second body of work. The chat reads the same published knowledge, the same brand voice, and the same facts the site itself is built from. A company does not keep one set of content for its pages and another for its bot. The chat is another surface onto the content that already exists, which is why standing it up costs a business nothing it has not already done.
The visitor never has to sign in. A stranger can open the chat, ask what they came to ask, and get an answer without making an account. The conversation is kept so they can close the page and come back to it later from the same browser. Most people who land on a company's site will never identify themselves. The chat is built for that majority rather than against it. A visitor says who they are by choosing to, not by clearing a requirement before the first answer.
Most AI chat on the public web answers everything, including the questions it has no business answering. One confident wrong reply is enough for a company to switch it off. This one is built the other way around. It answers from the content the business already maintains, cites what it used, speaks in the company's voice, and stops the moment that content runs out. A business writes its knowledge once, for its own site. The chat is a second reader of that knowledge, one that answers in the company's voice and stops where the company's knowledge stops. That is a chat a company can put in front of its customers on the first day and leave there.
If you're interested in my work or Giant Context, contact me!