How to build a knowledge base your AI chat can actually trust
A useful AI chat starts with current pages, precise rules and clear limits. Organise sources so every answer can be checked and uncertain questions move to a person.
Reviewed against current product behavior and plan limits.
The answer in one minute
A useful AI chat starts with current pages, precise rules and clear limits. Organise sources so every answer can be checked and uncertain questions move to a person.
- ✓Start with questions customers ask most often.
- ✓Separate facts, instructions, limits and temporary offers.
- ✓Remove duplicates and outdated pages before training.
- ✓Test answers in the sandbox and hand off anything not supported by a source.
Map real support topics first
Use conversation history, support email and sales questions. Group them into jobs such as choosing a service, payment, delivery, returns, access and technical help.
Do not import the whole website just to create volume. Prioritise pages that help visitors decide or solve a problem.
- top 10-20 questions
- questions before purchase
- human handoff reasons
- topics where accuracy is critical
Give each topic one current source of truth
Every topic needs a clear source: a page, FAQ, guide, catalogue entry or owner rule. When a price or condition appears in several places, align those pages before training.
Chtio can learn from website pages and extra URLs, and owners can add directives. Conflicting sources still produce conflicting answers.
- service or product name
- conditions and exclusions
- required steps
- valid dates for temporary rules
Write rules as verifiable decisions
“Try to help” is too vague. State what may be confirmed, which safe details to request, when to stop and when to transfer the conversation.
Do not place passwords, secret links, internal tokens or customer personal data in a shared knowledge base. Private context requires a separate protected flow.
- do not invent a missing fact
- ask for an order number, never a password
- send legal or payment disputes to a person
- reply in the language of the current message
Test before enabling AI for real visitors
Create a test set with normal, ambiguous, outdated and adversarial questions. Check both the answer and the willingness to refuse a guess.
Chtio provides an AI sandbox, unanswered-question workflows and operator corrections. Repeat the test set after meaningful website changes.
- fact accuracy
- clear next action
- readability
- correct human handoff
Maintain knowledge after launch
Assign an owner and a simple review schedule. Update sources after price, policy, catalogue or support-process changes.
Review questions that still lack a confident answer. They show which page, FAQ or instruction should be improved next.
- weekly review of new questions
- update after releases or campaigns
- remove obsolete sources
- retest critical journeys
Ready-to-adapt examples
Delivery rule
Use only delivery times published on the delivery page. If a country or method is missing, transfer the question to an operator.
The rule limits the source and forbids guessing.
Return rule
Ask for the order number and reason. Never ask for a password or card details. Transfer disputed cases to a person.
It defines safe data, a prohibition and a handoff condition.
Checklist
- Collected frequent real questions
- One current source per topic
- Removed duplicates and old conditions
- Added dates to temporary rules
- Explicitly prohibited invented facts
- Defined human handoff reasons
- Tested normal and difficult questions
- Assigned a knowledge owner
Questions about this topic
Can I simply import the whole website?+
Automatic discovery is a useful start, but quality improves when important pages are reviewed, duplicates are removed and rules do not conflict.
What should happen when AI does not know?+
It should say that confirmed information is unavailable and transfer to an operator or provide a clear next step.
Can customer personal data be added?+
Do not put personal data or secrets in the shared knowledge base. Private information needs protected context and access control.
How often should knowledge be updated?+
After any price, policy, catalogue or process change, and whenever new unanswered questions reveal a gap.
Test a safe baseline on your website
Save the domain and language. After creating the project, add reviewed pages, test answers and only then enable AI for visitors.