Build a Knowledge Base Assistant Using Claude Projects

Before setting up the project, do a quick audit: what are the questions customers ask you that require KB lookup? List them. Common ones:

• Return/refund policy details
• Shipping and delivery timeframes
• Product warranty terms
• Account management procedures (password reset, plan changes)
• Billing cycle and invoice explanations
• Troubleshooting for your top 3 product issues

These are the articles to prioritize uploading.

1. Log into claude.ai with your Pro account
2. Click "Projects" in the left sidebar → "+ New Project"
3. Name it "CS Knowledge Base" or "[Company] Knowledge Base"

Click "Project Instructions" inside your project and write:

You are a knowledge base assistant for Customer Service Representatives at [company type].

Your job: Answer CSR questions about company policies, products, and procedures accurately — based only on the documents uploaded to this project.

Rules:
1. Answer from the documents provided. Do not guess or fill gaps with general knowledge.
2. If the answer isn't in the documents, say "This isn't covered in the current KB — you may need to check with your team lead."
3. Give direct, actionable answers — CSRs are looking for what to tell a customer, not a lecture.
4. When quoting policy, be specific about the exact terms (e.g., "30 days from purchase date, with receipt").

Context: CSRs will ask things like "What's our policy on X?" or "How do I explain Y to a customer?" Give them what to say.

Inside the project, click the "Add files" or attachment icon. You can upload:

• PDF exports of policy documents
• Text files you create from copy-pasting KB articles
• Word documents with compiled FAQ content

Preparation tips:

• Combine related content into single files (e.g., "Return and Refund Policy.pdf" containing all return-related articles)
• Keep each file focused — one topic per file works better than one giant mixed document
• Strip out internal navigation, comments, and version notes — just the clean content

You can upload up to multiple files in a Claude Pro project. Start with your 5-10 most critical documents.

In the project conversation area, test with questions you actually get:

• "What's the policy if a customer returns a product after 35 days?"
• "How long does a refund take to appear on a credit card?"
• "What warranty terms apply to our [product category]?"

What good output looks like: A specific, accurate answer drawn from your uploaded documents. If the answer includes "per our policy" or cites the document — that's working correctly.

What to fix if output is inaccurate: If Claude gives a wrong answer, check if the relevant document is actually uploaded. Often the issue is that the content isn't in any uploaded file, not that Claude is misreading it.

This is an ongoing asset, not a one-time setup:

• When policies change, delete the old document and upload the updated version
• When you encounter a customer question with no good KB article, write a brief answer and add it to your project