See how a fictional course enquiry reveals whether a website chatbot uses relevant source pages, preserves conditions and recognises missing information.
The spoken explanation, organised by chapter.
But a working link does not establish that the answer itself is correct.
A fictional studio offers an introductory course. A visitor asks whether experience is required and whether weekends are possible. The page describes entry requirements but contains no weekend schedule.
The chatbot searches agreed public pages. It can explain entry requirements and show the source. For weekends, it should identify the missing information and offer a relevant contact route.
Check whether the source supports each relevant claim. A beginner course does not mean all ages may attend. Nor should the chatbot infer a price, available place or date that the page never provides.
The same visitor might ask about their own reservation. A public website chatbot does not thereby gain access to customer information. That question needs a separate appropriate route rather than an invented status.
Who withdraws an old course page? How is the chatbot updated? Agree this in advance. If an update fails, old content must not silently reappear as confirmed current information.
Test missing answers, changed pages and misleading instructions in input. Also check mobile use, keyboard navigation and closing. Ordinary navigation and contact must remain available if the chat does not load.
Choose a question involving multiple pages or follow-ups. If a clear page or ordinary search is enough, improve that first. Then assess what the chatbot adds.
Read OXIAE’s guide to website chat with public sources and clear information boundaries.
1:50Examine a fictional answer about business documents and learn to check passages, conditions, missing information and conflicting versions separately.
Source articleChat with business documents
1:52Follow a fictional work instruction through its lifecycle and see how source owners, versions, access permissions and deletion keep an AI knowledge base manageable.
Source articleAI knowledge base
1:51Follow a fictional support question from intake to human acceptance and see why a ticket, queue placement and an accepted case are different states.
Source articleAI customer service agent