> For the complete documentation index, see [llms.txt](https://docs.supademo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supademo.com/ai-demo-agent/agent-training.md).
# Agent Training
The Knowledge Base is what makes your agent intelligent. It's the content library the agent draws from to answer questions and make recommendations. The more relevant, high-quality content you add, the better your agent performs.
***
### Indexing Pipeline
Content goes through an **indexing pipeline** after being added: text is extracted, chunked into segments, converted to embeddings, and stored in a vector database for fast retrieval. You'll see the index status for each source:
| Status | Meaning |
| ------------ | ----------------------------------------------- |
| **Pending** | Queued for indexing. |
| **Indexing** | Currently being processed. |
| **Indexed** | Ready for the agent to use. |
| **Failed** | Indexing encountered an error. Try re-indexing. |
All Knowledge Base tabs support **bulk operations**: select multiple sources to reindex or remove them at once. You can also **reindex stale** content that may be outdated.
***
### Content Types
#### Demos
Use this tab to add interactive Supademo demos from your workspace. These are the agent's primary asset -- when a visitor asks about a feature, the agent can recommend and present the relevant demo directly in the chat. This allows users to click and explore different demos at their own pace and learn by doing.
After clicking **Add,** easily search, filter, and multi-select demos and folders to add to your Agent's knowledge base. You can also add optional hints next to these demos to ensure they're referenced/pulled up at the right context within the conversation.
{% hint style="info" %}
**Tips:**
* Add demos that show complete workflows, not isolated clicks.
* Name demos descriptively so the agent can match them to visitor questions.
* Cover your most common use cases and feature areas.
* Build demos specific to the agent use case (i.e. top-of-funnel sales, marketing) instead of reusing demos you've already created for other purposes (i.e. support docs)
* Start with a focused set of interactive demos (i.e. 10-15 core demos) instead of demos that are too granular or enablement/CS/training-focused.
{% endhint %}
#### Videos
Add video walkthroughs and tutorials. The agent recommends relevant videos when visitors want to see your product in action. These complement interactive demos by providing narrated context. For videos, you can add links from:
* Your Supademo workspace (previously recorded screen recordings)
* Youtube (by entering in a URL)
* Loom (by entering in a URL)
#### Documents
Upload PDFs, slide decks, case studies, and other documents. The agent uses these to answer pricing, feature comparison, and technical questions accurately. Supported types include PDF and other document formats.
#### Websites
Crawl your website, documentation site, or help center. Supademo uses Firecrawl to automatically crawl pages and index their content. This keeps your agent current with your latest pricing, features, and FAQs.
After adding a website URL, the crawler discovers and indexes individual pages as child sources. You can drill into a website source to see all discovered pages, their index status, and manage them individually (reindex or remove specific pages).
{% hint style="info" %}
**Tips:**
* Crawl **only specific pages on your marketing site** to avoid outdated content or hallucinations
* Re-crawl periodically to pick up important content updates
* Keep the content here focused on the Agent's use case (i.e. don't add all of your docs pages for a high-level sales use case for the AI Agent)
{% endhint %}
#### Text
Add custom knowledge snippets -- FAQs, talking points, objection handling scripts, or any information that doesn't live in a document or on your website. Useful for filling specific knowledge gaps identified in the Knowledge Gaps section.
{% hint style="success" %}
**Content hints** are available on every content type in the knowledge base: demos, videos, PDFs, documents, and website pages. When adding or editing any asset, click "Add Hint" to tell the agent exactly when and why to recommend it.
For example, hint a security whitepaper with "Surface when the prospect asks about compliance, SOC 2, or data privacy" so the agent pulls it up at the right moment instead of guessing from the title alone.
Adding hints across all your assets can improve recommendation accuracy significantly.
{% endhint %}
***
### Agent Readiness Check
Before publishing, check your agent's **Readiness Score** to evaluate whether it has enough source material to answer common prospect questions.
Click **Check readiness** in the right-side panel (or via the readiness card). The evaluation takes 15-30 seconds and grades your agent across categories of common questions.
#### Score Interpretation
| Score | Rating | Meaning |
| ------------- | ---------- | --------------------------------------------------------------------------- |
| **80-100%** | Strong | Strong source coverage. Your agent is well-prepared. |
| **50-79%** | Moderate | Some source gaps remain. Consider adding more content for uncovered topics. |
| **Below 50%** | Needs work | Significant gaps. The agent will struggle with many visitor questions. |
#### What's Evaluated
The readiness check tests whether your knowledge base can answer typical prospect questions across multiple categories. Each question is graded as:
* **Full** -- The agent has strong content to answer this.
* **Partial** -- The agent has some relevant content but may not fully answer.
* **Fail** -- No relevant content found.
Use the detailed breakdown to identify exactly what content to add. Each failed or partial question includes an explanation and, where applicable, whether a recommendable asset exists.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.supademo.com/ai-demo-agent/agent-training.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.