Short answer
A chatbot knowledge base is the help content, product data and policies an AI agent answers from. In Aide it holds your help center, website, Shopify products and business details, and every night Aide lists what it doesn't cover, with the text to add.- Sources
- Help center, website, your own articles, Shopify products, business information.
- Customer or internal
- Articles customers can read; snippets only Aide and your team see.
- Organizing
- Nested collections, bulk move, starred articles, drafts kept out of answers.
- Narrowing
- A procedure can answer only from up to 20 chosen sources.
- Gaps
- Every night, with the text to add and the article it belongs in.
- Measuring
- Cited articles and how often their conversations resolve, from 30 outcomes.
A help center used to be written for customers browsing on their own. An AI agent reads it differently: one question at a time, looking for the passage that answers it, and it repeats whatever it finds. That raises the bar on three things. The knowledge has to be current, the right article has to beat a similar one, and someone has to know what is missing.
This guide covers how to build and maintain that knowledge base in Aide. For getting your website and help center in the first time, see how to train an AI support agent on your website.
What goes in
Aide's Knowledge holds every source the agent answers from, and each kind does a different job.
- Help center. Imported from Zendesk, Gorgias, Front and other platforms, with its categories as nested collections. Re-import updates articles in place and keeps your team's edits.
- Website. Your policies, guides and FAQ pages, read through your links and sitemap. Text inside images, such as size charts and price lists, is transcribed so Aide can answer from it.
- Articles you write in Aide. Publish and Aide answers from it straight away, or save a draft to keep it out of answers until it's ready.
- Snippets. Internal notes, such as an escalation rule or an edge case, that Aide and Copilot use when the subject comes up. Customers never see them.
- Shopify products. Synced as real product pages with images, options, every variant with SKU, price and stock, collections, and metafields such as materials and care instructions.
- Business information. Phone numbers, email addresses, social profiles and apps, each with a note such as "Weekdays 9 to 5".
Articles and products work together. When an article names a product by its exact title, Aide reads that product's page too. Order and account questions are answered from the customer's real order, for verified customers, not from articles.
Knowledge base best practices
Most wrong answers trace back to the knowledge base, not the agent: two articles that disagree, a policy buried in a long FAQ, a page nobody has touched since last year. A few habits fix most of it.
- One answer per article. "Return window for sale items" is easier to find than a paragraph halfway down a general FAQ.
- Write out the specifics. Windows, fees, cut-off times and who qualifies, so the answer never depends on a guess.
- Group articles into collections. Collections can be nested, and you can tick many articles and move them in one step.
- Star the articles that should win. A starred article ranks higher when it matches.
- Keep internal guidance in snippets, not in customer articles, and switch off Used by Aide on pages customers should read but Aide shouldn't quote.
- Delete what's outdated. Exact copies are merged, but two versions that differ by a word are still two documents.
How Aide finds the answer
Aide searches from what the customer is asking now. In a long email thread, quoted earlier emails and signatures are left out of the search, and the words that carry the question decide which article ranks first.
When nothing matches, Aide searches again in your pages' own terms, so a visitor asking for "case studies" finds your "Customer stories" page. When no article answers fully, it writes from the one or two closest.
Some questions should come from one place only. Add "Answer only from these sources" to a procedure and pick up to 20 sources. A store with two brands can answer each brand from its own help center, and a wholesale inbox from the wholesale guide. Copilot drafts follow the same rule.
Fill the gaps every night
The Gaps list in Knowledge shows what customers ask that your team answers but your knowledge doesn't cover. It refreshes every night, and on a connected helpdesk it works from your team's past replies from day one.
Before a gap is proposed, Aide checks it against your whole knowledge base, drafts included. Each one comes as one of three fixes, with a copy button:
- A new article, with its title and text.
- A replacement for a sentence an article gets wrong, quoted as it reads today.
- A draft that only needs publishing.
Gaps are ordered by how many conversations raised them and close on their own once fixed. When the fix is a rule rather than an article, add it as an instruction instead. When teammates answer the same question differently, Aide lists the answers and asks which one is policy.
Measure what works
Analytics shows, for owners and admins, which documents Aide's chat replies drew on, how many conversations cited each, and how often those conversations were resolved. Below that, conversations Aide handed off for missing information are grouped by topic. Both download as CSV.
A routine that keeps knowledge honest:
- Weekly: work through the Gaps list.
- Monthly: look for cited articles whose conversations rarely resolve, and rewrite them.
- After any help center change: press Re-import.