> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runspark.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge Files

> Teach your agent about your business by uploading documents — pricing guides, policies, processes, and more

Here's a common frustration people have in their first week with a Spark agent:

> "I asked it about our pricing and it gave me the wrong numbers!"

That's because your agent doesn't automatically know your pricing. It doesn't know your policies, your services, your team structure, or your processes — until you *teach* it.

**Knowledge files are how you teach your agent.** They're documents you upload that give your agent all the information it needs to accurately answer questions, follow your processes, and represent your business correctly.

***

## The Before and After

Let's look at the difference knowledge files make:

<Tabs>
  <Tab title="❌ Without Knowledge Files">
    **You:** A client is asking about our pricing for a team of 50. What do I tell them?

    **Agent:** I don't have your specific pricing information yet. Could you tell me your pricing structure so I can help? Or you can upload a pricing guide to my knowledge base and I'll reference it in the future.

    *The agent is guessing — or admitting it doesn't know.*
  </Tab>

  <Tab title="✅ With a Pricing Guide Uploaded">
    **You:** A client is asking about our pricing for a team of 50. What do I tell them?

    **Agent:** Based on your pricing guide, a team of 50 falls in the 26-75 user tier. Here's the breakdown:

    * **Base rate:** $32/user/month = $1,600/mo
    * **Team discount (50+ users):** 10% off = \$1,440/mo
    * **Annual option:** $1,440 × 12 = $17,280 → with annual discount: $15,552/year (saves $1,728)

    Want me to draft a pricing email for the client with these numbers?

    *Accurate, detailed, and ready to act on — because the agent has the source document.*
  </Tab>
</Tabs>

That one upload transformed your agent from "I don't know" to "here's the exact answer with a calculation and a draft email." **This is why knowledge files are so important.**

***

## What to Upload

Think about everything a new employee would need to read during their first week. That's what your agent needs too.

<AccordionGroup>
  <Accordion title="💰 Pricing & Rate Sheets">
    Your pricing tiers, packages, discounts, calculation rules, and any special rates. Be specific — include:

    * How to calculate totals step by step
    * Rounding rules ("always round up to the next whole unit")
    * Tax rates and whether to include them
    * Seasonal or promotional pricing
    * Volume discounts and when they apply

    **Example content:**

    ```
    PRICING GUIDE - Updated March 2026

    Standard Package: $45/person
    - Groups of 1-25: standard rate
    - Groups of 26-50: 5% discount
    - Groups of 51-100: 10% discount
    - Groups of 100+: contact manager for custom quote

    Always round up to the next group of 5 when calculating
    headcount (e.g., group of 27 = quote for 30).
    ```
  </Accordion>

  <Accordion title="📋 Company Policies">
    Cancellation policy, refund policy, terms of service, warranty information, privacy policy — anything a customer might ask about.

    **Why it matters:** Without this, your agent either guesses (risky) or says "I don't know" (unhelpful). With it, your agent gives the accurate policy every time.
  </Accordion>

  <Accordion title="🛠️ Services & Products">
    Descriptions of what you offer, what's included in each tier, features, limitations, and comparisons between options.

    **Pro tip:** Include a comparison chart or "which option is right for which customer" guide. Your agent will use this to make recommendations.
  </Accordion>

  <Accordion title="📝 Processes & Workflows">
    Step-by-step procedures for how you handle things: new lead intake, client onboarding, quote generation, complaint handling, refund processing.

    **Example:**

    ```
    NEW LEAD PROCESS:
    1. Create contact with all provided info
    2. Determine which package fits their needs
    3. Calculate a quote using the pricing guide
    4. Draft a welcome email using the standard template
    5. Set a follow-up task for 48 hours later
    6. If deal value is over $10,000, notify the manager
    ```
  </Accordion>

  <Accordion title="❓ FAQs & Common Questions">
    The questions you get asked repeatedly, with your standard answers. This saves your agent from guessing and ensures consistent responses.

    **Example:**

    ```
    Q: Do you offer a free trial?
    A: Yes — 14-day free trial, no credit card required.
    Full access to all features. Trial converts to the
    plan they selected unless they cancel.

    Q: Can we change plans mid-contract?
    A: Yes, upgrades are prorated. Downgrades take effect
    at the next billing cycle.
    ```
  </Accordion>

  <Accordion title="✉️ Email Templates & Scripts">
    Your standard emails, response templates, call scripts, and messaging guidelines. Your agent will use these as a starting point when drafting communications.

    **Include:** Welcome emails, follow-up templates, proposal templates, objection responses, closing scripts.
  </Accordion>

  <Accordion title="👥 Team & Company Info">
    Who does what at your company, office locations, business hours, company history, mission statement — anything that helps your agent represent your business accurately.
  </Accordion>

  <Accordion title="📊 Product/Service Catalogs">
    If you have a large inventory, menu, or catalog, upload it. Your agent can then look up specific items, check availability, and recommend options.
  </Accordion>
</AccordionGroup>

***

## How to Add Knowledge Files

### Create a Document Directly

1. Click **Knowledge** in the sidebar
2. Click **New Document**
3. Write or paste your content in the editor
4. Give it a clear title (e.g., "Pricing Guide - Q2 2026")
5. Save

### Upload a File

1. Click **Knowledge** in the sidebar
2. Click **Upload**
3. Select your file(s)
4. Your agent can read them immediately

**Supported formats:**

| Format             | Notes                                                 |
| ------------------ | ----------------------------------------------------- |
| **PDF**            | Must contain actual text (not scanned images of text) |
| **Word (.docx)**   | Converted automatically                               |
| **Excel (.xlsx)**  | Great for pricing tables and catalogs                 |
| **CSV**            | Spreadsheet data                                      |
| **Text (.txt)**    | Plain text files                                      |
| **Markdown (.md)** | Formatted text                                        |

<Info>
  **Maximum file size: 10MB per file.** There's no limit on the number of files you can upload. If you have a large document, consider breaking it into focused sections — one file for pricing, one for policies, one for processes — so your agent can find the right information faster.
</Info>

***

## How Your Agent Uses Knowledge Files

This is important to understand: **your agent does not memorize your knowledge files.** Instead, it works like this:

1. You ask a question or give an instruction
2. Your agent recognizes the topic relates to a knowledge file (e.g., you asked about pricing → it checks the pricing guide)
3. It reads the relevant document at that moment
4. It uses the information to give you an accurate answer

Think of it like a reference binder on your agent's desk. Your agent knows what's in the binder and reaches for the right section when needed — but it doesn't try to memorize every page.

**Why this matters:**

* ✅ **Updates are instant.** Change a knowledge file and your agent sees the new version the very next time it looks. No delay, no retraining.
* ✅ **More files don't slow things down.** Your agent only reads what's relevant to the current question — it doesn't get bogged down by volume.
* ✅ **Accuracy is higher.** Since it's reading the source document, it gives answers based on your actual data, not a fuzzy memory.

***

## What Makes a Good Knowledge File

The quality of your agent's answers depends directly on the quality of your documents. Here's how to make them great:

### Do: Be Specific and Concrete

<Tabs>
  <Tab title="✅ Good">
    ```
    REFUND POLICY

    - Full refund: Cancel 48+ hours before the event
    - 50% credit: Cancel 24-48 hours before the event
    - No refund: Cancel less than 24 hours before the event
    - Weather cancellations: Full refund or free reschedule
    - Group bookings (20+): Require 72-hour notice for full refund
    ```
  </Tab>

  <Tab title="❌ Bad">
    ```
    We have a flexible refund policy. Refunds are handled
    on a case-by-case basis depending on the circumstances.
    Please contact us for details.
    ```
  </Tab>
</Tabs>

The first version gives your agent exact rules to follow. The second version tells it nothing — your agent would have to guess or say "contact us," which defeats the purpose.

### Do: Include Examples and Edge Cases

```
PRICING CALCULATION EXAMPLES

Example 1: Group of 30, standard package
- 30 people × $45/person = $1,350
- Round up to next group of 5: still 30 (already divisible)
- Total: $1,350

Example 2: Group of 27, standard package
- Round up to next group of 5: 30 people
- 30 × $45/person = $1,350
- Total: $1,350 (NOT $1,215 for 27 people)

Example 3: Group of 55, standard package with referral
- Round up to next group of 5: 55 (already divisible)
- 55 × $45 = $2,475
- Group discount (51-100): -10% = -$247.50
- Referral discount: additional -5% = -$111.38
- Total: $2,116.12
```

Examples prevent miscalculations. Your agent will follow the pattern in your examples.

### Do: Keep Files Focused

One topic per file is better than everything in one giant document. Good:

* ✅ "Pricing Guide"
* ✅ "Cancellation Policy"
* ✅ "New Client Onboarding Process"
* ✅ "FAQ - Common Customer Questions"

Not as good:

* ❌ "Everything About Our Business" (too broad — agent has to dig through irrelevant info)

### Don't: Use Vague or Ambiguous Language

If your document says "prices may vary" or "typically around \$50," your agent doesn't know what to tell the client. Give it specific numbers, specific rules, and specific exceptions.

***

## Assigning Knowledge to Specific Agents

If you have [multiple agents](/agent/multiple-agents) in your workspace, you can control which agents can access which files:

* **All agents** — every agent can read this file (good for company-wide info like team structure, general policies)
* **Specific agents** — only selected agents can access this file (good for role-specific info)

**Example:** You have a sales agent and a support agent.

* The pricing guide is assigned to both (both need to reference pricing)
* The cold outreach script is assigned only to the sales agent
* The troubleshooting guide is assigned only to the support agent

You set this when creating or editing a knowledge document.

***

## Keeping Knowledge Files Updated

Your agent is only as accurate as your documents. When things change in your business:

1. **Update the relevant knowledge file** with the new information
2. That's it. Your agent will use the new version the next time it references that file.

No retraining, no waiting, no restart needed.

<Tip>
  **Set a quarterly reminder** to review your knowledge files. Pricing changes, policies get updated, new services get added. A quick review every few months keeps your agent accurate. You can even ask your agent to set up this reminder: "Every quarter on the 1st, remind me to review and update the knowledge files."
</Tip>

***

## Industry Examples: What to Upload

### Real Estate Agency

* Listing descriptions and pricing
* Commission structure and fee schedule
* Buyer/seller process walkthrough
* Neighborhood guides and market data
* Standard contract terms
* Open house procedures

### Fitness Studio

* Class schedule and descriptions
* Membership tiers and pricing
* Cancellation and freeze policies
* Trainer bios and specialties
* Corporate wellness packages
* FAQ for new members

### Marketing Agency

* Service packages and pricing
* Case studies and portfolio examples
* Client onboarding checklist
* Content creation process
* Standard timelines by project type
* Social media platform guidelines

### Insurance Broker

* Coverage types and descriptions
* Carrier comparison charts
* Quote calculation guidelines
* Claims process walkthrough
* Licensing and compliance requirements
* Renewal procedures

### Event Venue

* Venue capacity and layouts
* Package pricing (food, bar, AV, decor)
* Vendor lists and preferred partners
* Day-of coordination procedures
* Weather and cancellation policies
* Setup and teardown timelines

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="My agent is giving wrong pricing numbers">
    Check the pricing knowledge file — it's likely outdated or missing the specific scenario. Update the file with the correct numbers and add calculation examples for edge cases.
  </Accordion>

  <Accordion title="My agent says 'I don't have information about that'">
    This means you haven't uploaded a knowledge file covering that topic. Create a document with the relevant information and your agent will start referencing it immediately.
  </Accordion>

  <Accordion title="My agent isn't using information from my uploaded file">
    Make sure the file title is clear and descriptive — "Pricing Guide 2026" is better than "Document1.pdf." Also, if you have multiple agents, check that the file is assigned to the right agent.
  </Accordion>

  <Accordion title="My PDF isn't working">
    The PDF must contain extractable text — not just scanned images of pages. If your PDF is a scan, convert it to text first using an OCR tool, or re-create the content as a text document.
  </Accordion>
</AccordionGroup>
