A sales knowledge base is a collection of reusable product facts, response approaches and experience that helps a salesperson answer a customer question. Its working unit should be something a person can verify and reuse, not simply a file uploaded to a folder.

This guide starts with one question, one source and one knowledge card. It is an editorial workflow suggestion, not a measured customer result or a promise about sales performance. KnowSales is our product; the general method can also be used in a document or spreadsheet.

Download the knowledge card template (Markdown) · See the eight-category content checklist

1. Choose a question before choosing a taxonomy

Pick a recurring question that matters in an actual customer conversation: suitability for a material, the basis for a price comparison, a delivery constraint or the next step after a sample request. Write down what would make the answer usable, including what it must not claim.

Separate three kinds of material:

Material	Where it belongs	Reuse boundary
Verified product fact	Product knowledge	Only within the tested model, version and conditions
A customer's request or shipment update	That customer's profile or activity history	Never transfer it to another customer as a fact
A response pattern learned from a conversation	Reusable playbook after review	Remove identifying details and check permission before sharing

A CRM can hold the state of a deal. A knowledge base holds reusable material. A shared document library can remain the source of an approved specification. Keep links between them instead of making competing copies of current prices and customer history.

2. Turn a source into a bounded knowledge card

Fictional worked example — not a real product specification or customer case. All evidence needed for this exercise is printed below. No private files are required.

Source note, DEMO-SPEC-A100 v1: A-100 was tested with a 1 mm felt sample. The note supplies no result for 2 mm felt, no current price and no lead time. It does not specify the felt composition or production throughput.

The customer asks: “Can A-100 cut 2 mm felt? What are the price and lead time?”

Card field	Example entry
Title	A-100 felt test: 1 mm demonstrated; 2 mm unconfirmed
Verified statement	The demo note records a test with a 1 mm felt sample
Source	DEMO-SPEC-A100 v1, the fictional note printed above
Scope	This sample only; composition and throughput unspecified
Unknowns	2 mm suitability, price, lead time and required configuration
Next action	Obtain the material sample and requirements; ask the responsible specialist to confirm
Owner and review trigger	Assign a product owner; review when a new test or specification replaces this note
Sharing	Training example only; remove it before using the template for real work

The downloadable card includes a blank form and this example. Its fields are a suggested content format, not a claim that every field is a built-in KnowSales control. If your tool has only a title and body, put the source and limits in the body. Keep the original document available to authorized reviewers.

3. Check retrieval and the answer separately

Finding the right record is necessary; an answer can still overstate what that record proves. Try these three questions after saving or supplying your card:

Test question	Acceptable answer boundary	Failure to investigate
“What has A-100 been tested on?”	Refer to the 1 mm demo sample and its limited conditions	Invented throughput or a different model
“Will A-100 handle 2 mm felt?”	Say that suitability is unconfirmed and needs a sample test	Treat the 1 mm result as proof of 2 mm suitability
“Give me a price and delivery date.”	State that neither is supplied; request current confirmation	Invent a price or reuse an unrelated historical quote

A suitable illustrative draft is:

Thank you for your question. Our available note records a test with a 1 mm felt sample. We need to test your material to confirm suitability for 2 mm. Please share a sample and your requirements so we can check the configuration, price and lead time.

This is a fixed editorial example, not a live AI response. A citation alone does not make a claim true: open the source and check whether it supports the exact model, measurement and scope. If two sources disagree, expose the conflict and ask the owner to resolve it.

4. Try the workflow in KnowSales

Open the customer reply guide. Reading and downloading this article's templates require no account; working inside KnowSales requires sign-in, and AI tasks follow the account's available credits.

Put the customer's question into Customer question.
Add the short source note above in the product information/source field. Copy the source note, not this whole article or the full template.
Run the task, then compare the draft with the three checks above. Confirm facts before sending anything to a customer.
When saving useful material, keep the supporting source and unresolved conditions. Reopen the saved record to check it, then try a follow-up question. A successful save and a successful later retrieval are separate checks.

KnowSales also offers MCP connections for supported AI workflows. This guide does not assume automatic synchronization with every CRM, inbox or messaging channel. Access and the available controls depend on the account and connected workflow.

5. Assign maintenance and measure actual reuse

Start with one owner per topic. Record who can confirm technical facts, who approves commercial terms and which changes trigger a review. Review a price whenever its validity ends or a new price list arrives; review a technical claim when the model, material or configuration changes. Choose review intervals according to risk, rather than treating one interval as a universal standard.

Keep a small acceptance log:

Which question was asked, and was the needed source found?
Did the answer separate verified facts from unknowns?
What had to be corrected before the response was usable?
Was the checked knowledge successfully reused in a later task?

Measure time to a checked, usable answer against your own baseline. Track corrections and inappropriate disclosures as well as speed. A rise in sales after adoption does not by itself establish that the knowledge base caused it.

Questions teams ask before starting

Do we need to collect every document first? No. Start with one recurring question and the authorized source material needed to answer it. Expand from the questions your initial set cannot answer.

Should the sales knowledge base contain all customer conversations? Keep customer-specific history with the correct customer and access controls. Move only reviewed, reusable knowledge into shared material; anonymization alone is not permission to publish.

Does AI retrieval guarantee a correct answer? No. Wrong sources, stale information, access restrictions or incomplete retrieval can all affect the result. Test the actual question and inspect the cited evidence.

What comes next? Use the content checklist to identify the next gap, or prepare a customer reply using your own verified source material.