Companies do not avoid support chatbots because they are hard to build. They avoid them because a bot that invents a refund policy costs more than all the support time it saves.
This is a self-initiated demonstration built to answer that objection directly.
The setup. Shiftbloom is an invented shift-scheduling company, written for this demo. Its help centre — 7 documents, 33 sections covering pricing, scheduling, integrations, security and support — was written alongside it. The assistant is allowed to reply using that material and nothing else.
Three honest outcomes. It answers and prints the source underneath. Or it asks which topic you meant. Or it says the help centre does not cover this, and hands you to a person. There is no fourth option: nothing inside it writes new text, so a fabricated answer is not something it can produce even by accident.
It survives real typing. Questions arrive with typos, half-remembered wording and words the documentation never uses. The assistant repairs the spelling against its own vocabulary, understands synonyms, and measures how much of your question a page actually covers before it commits to an answer. A question made of common words cannot pull a confident reply out of an unrelated page.
Quality is tested, not claimed. A fixed set of 74 questions runs from a button on the page itself — real phrasings, typos, paraphrases, and questions it must refuse. All 74 pass. Every wrong answer found while building was turned into a test, so it cannot come back.
It runs entirely in your browser — no server, no API key, no account.
In a real project you get: your own content as the knowledge base, the assistant embedded in your site, the test questions as a file you can read, and a monthly report of the questions it could not answer — which is a map of the gaps in your own documentation.
