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

# Context

> Everything your agent knows, organized as documents you control per channel

## What is Context?

Context is your agent's knowledge base. Everything it knows about your business is a **document**: text you write, a file you upload, a page crawled from your website, or a question-and-answer pair. Each document is assigned to the channels where it should be used (chat, voice, text, email), so you can keep a sales playbook chat-only, give voice a short script, and let email see everything.

Open it from **Context** in your agent's sidebar.

<CardGroup cols={2}>
  <Card title="Documents" icon="file-lines" href="/features/context/documents">
    Write text, pin the essentials, choose channels
  </Card>

  <Card title="Files" icon="file-arrow-up" href="/features/context/files">
    Upload PDFs, Word docs, text and markdown
  </Card>

  <Card title="Websites" icon="globe" href="/features/context/websites">
    Crawl your site; every page becomes a document
  </Card>

  <Card title="Q&A" icon="circle-question" href="/features/context/qa">
    FAQs, plus questions your agent could not answer
  </Card>
</CardGroup>

## How your agent uses it

There are two ways a document reaches your agent:

<AccordionGroup>
  <Accordion title="Pinned (Always include)">
    Pinned documents are included in every conversation on their channels, word for word. Use them for who you are, what you sell, hours, contact details, tone, and hard rules. Keep them short; they are sent with every message. Your **About** document (created from your website when you sign up) is pinned by default.
  </Accordion>

  <Accordion title="Retrieved when relevant">
    Everything else is split into passages and searched for each incoming message. Only the passages that match the customer's question are added, so a 200 page website or a long PDF only shows up when it is useful. This keeps replies focused and fast.
  </Accordion>
</AccordionGroup>

<Note>
  **Voice is different.** Phone calls have no per-message retrieval: the whole prompt is sent to the voice provider once when the call starts. Every document checked for Voice is included in full at that moment, pinned or not, up to a **voice budget** of about 40,000 characters. The budget exists mostly for latency; a bigger prompt means a longer pause before each spoken reply. Website pages are never used on Voice. See [Settings](/features/context/settings#voice-budget).
</Note>

## Channels

Every document has four checkboxes: **Chat**, **Voice**, **Text**, **Email**. A document is only used on the channels you check. Defaults:

| Source                      | Default channels              |
| --------------------------- | ----------------------------- |
| Text you write, files, Q\&A | All four                      |
| Website pages               | Chat, Text, Email (Voice off) |

Turn a channel off to keep a document without using it there. Turn every channel off (or disable the document) to park it without deleting it.

## What replaced the old Knowledge screen

If you used Clarky before Context, the mapping is:

* **General knowledge** became a pinned document called *About \<your agent>*, on all channels.
* **Chat / Voice / Text / Email knowledge** boxes each became a pinned *\<Channel> instructions* document on that one channel.
* **Website pages** are now regular documents you can search, edit, disable, or assign to channels one at a time.
* **Files** and **Q\&A** are real now.

Nothing was lost; open Context and you will see all of it as documents.

## Best practices

<AccordionGroup>
  <Accordion title="Pin the essentials, retrieve the rest">
    A short pinned About document plus longer retrieved documents beats one giant pinned wall of text. It is cheaper, faster, and answers are more precise.
  </Accordion>

  <Accordion title="One topic per document">
    "Refund policy", "Pricing 2026", "Sales playbook" retrieve better than a single mixed document, and they are easier to keep current.
  </Accordion>

  <Accordion title="Answer the questions it could not">
    Check **Context > Q\&A** now and then. Every question your agent could not answer is waiting there; answering it teaches the agent immediately.
  </Accordion>

  <Accordion title="Test before customers do">
    **Context > Settings > Test retrieval** shows exactly which documents your agent would use for any question you type.
  </Accordion>
</AccordionGroup>