Give a website chatbot information that is not on your public pages by uploading a file, pasting text, or adding hand-written question-and-answer pairs. Use one clear source for each fact. If the material still does not settle a visitor's question, the chatbot should leave it for a person.
A website crawl cannot read a rate card on your computer or the answer your receptionist gives from memory. Chatterbox can also take an uploaded file, pasted text, or hand-typed question-and-answer pairs. The useful choice is the smallest source that states the fact clearly.
This is not a reason to pour every internal document into the chatbot. It is a way to fill specific gaps without publishing a new page for each one.
When should information stay off public pages?
Some answers belong on the site. Opening hours, service areas, standard policies, and ordinary buying information help every visitor and should be easy to find without opening a chat window.
Other material does not fit neatly into a public page. A service team may use a short preparation guide. A consultant may have a fixed list of details needed before an initial call. A shop may keep care instructions in a document sent after purchase. Those can still answer real visitor questions even when a crawl cannot reach them.
Keep secrets out. Chatterbox shows the source passage behind an answer to the visitor. Treat every source as customer-facing material, even if it was added through the dashboard rather than published as a web page.
Which knowledge source fits the missing answer?
Use an uploaded file when the information already exists as one maintained document. This avoids copying a long guide into several smaller entries. Check it first for old versions, internal comments, and statements a customer should not see.
Paste text when the material is short, approved, and unlikely to need its own page. Give it a clear scope. A compact explanation of what customers should bring to an appointment is easier to maintain than a mixture of preparation notes, pricing, and exceptions in one block.
Use hand-typed Q&A when one question needs one exact answer. This works well for the repeated question that staff answer every day but nobody has written down. Chatterbox supports manual Q&A as one of its knowledge sources.
What should you type as a manual answer?
Write the customer's question in ordinary language. Then answer only that question. Include the condition that changes the result.
For example, do not write a broad answer saying delivery is available. State the area the business has approved and any condition that belongs with it. Do not turn a starting price into a quote for every job. If an exception still needs judgment, say that a person must confirm it rather than writing a likely outcome.
One clear answer is safer than three slightly different versions. Before adding a Q&A, search the site, uploaded files, and pasted text for the same fact. Remove or update the older version instead of making the chatbot choose between them.
What happens when the extra material still does not answer?
A file or manual Q&A does not make the knowledge base complete. Visitors will ask about a new exception, combine two policies, or request a promise the business has never made.
Chatterbox says it cannot find the answer rather than inventing one. It then asks for contact details. Lead capture collects a name, phone number, and email, and the lead reaches the dashboard and email for a person to handle.
That boundary matters most for prices, policies, and commitments. The extra source should make known answers easier to find. It should not give a standard answer permission to stretch into an unknown case.
How do you keep added knowledge useful?
Test one question that each source should answer and one it should not. Check the source passage shown with the answer. If the passage is unclear on its own, rewrite the source rather than polishing the chatbot's wording.
Keep one owner for each fact. When a rate, condition, or process changes, update the maintained source and remove the stale copy. Chatterbox can also re-crawl a website source once a day, but uploaded, pasted, and hand-written material still needs someone to keep it current.
Start with the five questions your crawl cannot answer. Add the smallest suitable source for each, then test the edge case that should still reach a person. The goal is not to make the chatbot answer everything. It is to make each answer traceable and each gap honest.