Key takeaways
- Readers meet two meanings: the help-centre or wiki sense and the AI sense that comes from expert systems.
- In classic AI, the knowledge base holds what is known and a separate inference engine draws conclusions from it.
- A company knowledge base gives every rep and every AI draft the same positioning, pricing rules and answers.
- Ownership, review and freshness matter more than the tool the knowledge base lives in.
Knowledge base meaning: the two senses
Knowledge base means two related things, depending on who is speaking. In most companies it is a help centre for customers or an internal wiki for staff: articles people search and read.
In AI it has a narrower, older meaning. Expert systems split their design into a knowledge base, the facts and if-then rules a specialist's know-how was turned into, and an inference engine that applies those rules to a new case. The knowledge base was the part that changed as the domain changed; the engine stayed the same.
How an AI knowledge base works today
An AI knowledge base today is usually a collection of documents, records and written sections that an assistant looks up before it answers. Instead of firing rules, the system retrieves the passages most relevant to a question and gives them to a language model as context, the pattern known as retrieval-augmented generation.
The principle is the same as in the older systems: keep the knowledge outside the program, where people can read and correct it. What changes is the reader. A rule engine needs facts in a strict shape; a language model can read prose, which makes a knowledge base easier to build but harder to check, because a well-phrased but outdated entry is used as readily as a current one.
Knowledge base vs knowledge graph
A knowledge graph is one way to build a knowledge base, not a rival to it. Knowledge base names a role, the store a person or system draws on; knowledge graph names a structure, facts held as entities joined by named relationships.
Many useful knowledge bases contain no graph at all: a set of reviewed documents, a pricing table and a list of approved answers can serve a sales team well. A graph earns its effort when the questions are about connections, such as who knows whom across accounts.
Company knowledge base examples for sales and marketing
A company knowledge base for sales and marketing holds the facts every rep and every AI draft should repeat the same way. Typical entries, written by the people who own them:
- Positioning and the value proposition, in the words the company has agreed.
- Pricing, packaging and discount rules, including who can approve exceptions.
- Approved answers to common objections and to security questions.
- Case-study facts that someone has checked and the customer has cleared for use.
- The ideal customer profile, buyer personas and the segments the team sells to.
- Brand voice guidance: tone, words to use and words to avoid.
What keeps a knowledge base useful
A knowledge base stays useful when each area has a named owner, entries are reviewed on a rhythm, old material is retired and people can find what they need in seconds. Without those, it fills with duplicates and stale pages that nobody trusts.
Stale entries matter more once AI reads them. A rep might notice that a page is out of date; an assistant will repeat it fluently. Marking entries as reviewed, and removing what is no longer true, is the cheapest quality control an AI-assisted team has.
Where Pebbles Ai fits
- FoundationCompany IntelCompany Intel holds Business knowledge and Brand voice, built from the company website, company information, uploaded files and pasted text, and admins refresh it with 'Add what's missing' or 'Start fresh'. On Team and above, Library items move from Pending review to Approved.
- FoundationAgent memoryAgent memory keeps short facts a user states or confirms in chat, and Company memory reaches colleagues' assistants too.
Common questions
What should a sales team put in its knowledge base first?
Start with what reps and AI drafts most often get wrong: positioning, pricing and discount rules, and approved answers to common objections. Add case-study facts once someone has checked them.
Who should own a company knowledge base?
One named person or team per area, usually product marketing for positioning and sales or revenue operations for rules and process. Shared ownership with no named owner is how entries go stale.
Can an AI assistant answer from a knowledge base?
Yes, when it is connected to one: the assistant reads the relevant entries and drafts from them instead of from general knowledge. The answer is only as current as the entries it reads.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .