Where the work gets stuck
Chatbase’s current data-source guide lists websites, selected links, files, text, Q&A, Notion, and tickets as supported sources. For a public assistant, choose current material that answers visitors’ questions. Old campaigns and duplicate policies can make the answers unclear.
What to prepare
- An approved list of source pages
- A content owner and update schedule
- A set of expected answers and a route to the right staff member
Follow these steps
- Use Build > Data sources to add the approved website pages or sitemap.
- Exclude obsolete, unrelated, or restricted paths from the source set.
- Test questions where the correct answer depends on a region, version, or date.
- Review source updates and repeat the same questions after a change.
An example from everyday work
A training institute can start with one intake’s course information and application process. A retailer can begin with current delivery, returns, and product-use pages. Both should remove outdated material before asking the assistant to resolve a conflict.
When your team should take over
The current guide says source changes are processed automatically, without a retrain button. For urgent changes, check that visitors can see the updated answer instead of relying only on a scheduled source update.
How to check the results
- Correctness against the expected answers
- Outdated or conflicting source answers
- Time required to publish and verify a content change
Your next step
Keep a list of sources with the owner and version of each one. This makes the assistant easier to maintain when staff change.