Website Chatbots
What the chatbot knows
Choosing its sources, uploading documents, and why it needs re-indexing after a big content change.
Last updated September 2, 2026
The chatbot answers from your own content. On Knowledge Sources you choose which:
| Source | What it contributes |
|---|---|
| Website Pages | Everything published on the attached websites. |
| Products & Services | Your active catalogue. |
| Locations | Each tribe's profile, address and contact details. |
| Case Studies | Your published Our Work posts. |
| Blog Articles | Your published articles. |
| Uploaded Documents | Files you add specifically for the chatbot. |
Your internal content is never used
The Knowledge Base and Resource Library are deliberately excluded. Those hold staff material — price lists, operations manuals — and a public chatbot must not be able to quote them.
Uploading documents
Add PDF, Word (.docx), .rtf, .odt, .txt, .md, .csv and .html files, up to 20 MB each. A document can be scoped to a single tribe, which is how you give one tribe its own price list or service list without the others seeing it.
It is only as good as your content
A thin website produces a chatbot that cannot help. If it keeps failing to answer something, the fix is nearly always to write the page rather than to change a setting.
Re-index after a big change
Deleting a document
Removes it from the chatbot's knowledge straight away. Worth doing promptly when a price list goes out of date — an assistant quoting last year's prices is worse than one that says it does not know.
See it working
A franchise website running on Gorilla Dash
Hungry Gorilla is a demonstration website for a made-up cafe franchise. Its pages, location pages, menus, online ordering and enquiry forms are all managed in Gorilla Dash, so you can see how the pieces fit together before you build your own.