> For the complete documentation index, see [llms.txt](https://docs.11x.ai/llms.txt).
> Use it to discover all available pages before exploring further.

# Knowledge base

The knowledge base is what Alice and Julian know about your company. Upload PDFs, docs, URLs, call transcripts, and battle cards, then scope them per campaign.


The knowledge base is the set of company facts your digital workers draw on. You upload source material once — **PDFs, documents, URLs, call transcripts, and battle cards** — and 11x structures it so both Alice and Julian reference it during outreach and conversations. It is a single source of truth shared by both workers, and updates take effect immediately for future interactions.

<Callout kind="tip">
This is the highest-leverage input on the platform. Generic outreach is almost always a thin-knowledge-base problem, not a model problem. Budget real time here — it is the step teams most often rush and most often regret.
</Callout>

## What it accepts

| Source | Typical use |
| --- | --- |
| **PDFs** | Product one-pagers, whitepapers, analyst reports |
| **Documents** | Positioning docs, messaging frameworks, pricing guidance |
| **URLs** | Your own product and pricing pages, published case studies |
| **Call transcripts** | Real objections and real language from real deals |
| **Battle cards** | Competitive differentiation and trap-setting questions |

Content is uploaded once and structured automatically. You don't need to format it for the platform.

<Callout kind="info">
Call transcripts are the most underused source. They contain the objections your buyers actually raise and the words they actually use — which is exactly what makes outreach sound like a person wrote it.
</Callout>

## What to cover

Work through all six. Gaps here show up directly in output quality.

| Input | Why it matters |
| --- | --- |
| **Positioning** | What you sell, who it's for, the problem it solves |
| **Product detail** | Specific enough to make a concrete claim, not a category claim |
| **Competitive differentiation** | How to respond when a prospect names an alternative |
| **Objection handling** | The five objections you hear most, and your actual answers |
| **Proof points** | Named customers, quantified results, relevant case studies |
| **Boundaries** | Claims that must never be made; topics to route to a human |

<Callout kind="alert">
**Boundaries are not optional.** They are what make autonomy safe to leave running. Write down the claims Alice must never make — unsupported performance numbers, compliance assertions, roadmap commitments — as explicitly as you write the positioning.
</Callout>

## Campaign-level scoping

You can restrict which knowledge base entries apply to a given campaign, so outreach stays focused on exactly what you're selling in that motion.

This matters most if you sell more than one product. Without scoping, a campaign for one offering can pull in context from another and produce outreach that pitches everything at once — which reads as unfocused and converts poorly.

<Steps>
  <Step title="Group entries by offering" icon="folder">
    Keep product-specific material separable rather than merged into one general document.
  </Step>
  <Step title="Scope each campaign to one offering" icon="filter">
    Select only the entries relevant to what that campaign is selling.
  </Step>
  <Step title="Keep shared material shared" icon="share-2">
    Company positioning, proof points, and boundaries usually apply across all campaigns.
  </Step>
</Steps>

## Version history

Every update is tracked with full audit visibility — what changed, when, and by whom. If new messaging underperforms, you can roll back to a previous version without losing progress.

<Callout kind="tip">
Change one thing at a time and note the date. If you rewrite positioning, differentiation, and proof points in the same week, a drop in reply rate tells you nothing about which change caused it.
</Callout>

## Shared with Julian

Both workers pull from the same knowledge base. That means the answer a prospect gets from Alice's outreach and the answer they get on a call with Julian come from one source.

Keep it that way deliberately — divergent positioning between outbound and inbound is a credibility problem that's hard to detect from inside.

## Keeping it current

The knowledge base is not a setup task you complete. Update it when:

- Positioning or messaging changes
- You launch or sunset a product
- A new competitor becomes relevant, or an existing one changes their pitch
- You win a notable customer worth citing as a proof point
- A recurring objection emerges that isn't yet covered
- Pricing posture changes

<Callout kind="alert">
A stale knowledge base degrades quietly. Output stays fluent while becoming subtly wrong — which is harder to catch than an obvious failure. Assign an owner and a review cadence.
</Callout>

## Frequently Asked Questions

<Expandable title="Why does outreach read generic?">
Almost always thin product detail or missing proof points. Add specifics that let Alice make a claim about *this* buyer's situation rather than a claim about your category. Also check whether the campaign is scoped to too many offerings at once.
</Expandable>

<Expandable title="What should I do if Alice makes a claim we cannot support?">
Add it to boundaries explicitly. Absence of a claim in the knowledge base is not the same as a prohibition on making it.
</Expandable>

<Expandable title="Why does messaging pitch multiple products in one email?">
Campaign scoping isn't set, or entries for different offerings are merged into one document. Separate them and scope the campaign.
</Expandable>

<Expandable title="Why did reply quality drop after a knowledge base update?">
Use version history to identify what changed and roll back. Then reapply the change in smaller pieces to isolate the cause.
</Expandable>

<Expandable title="Why are outbound and inbound saying different things?">
Something is scoped inconsistently between Alice's campaigns and Julian's call flows. Both read the same knowledge base, so divergence is a scoping issue rather than a content one.
</Expandable>

## Next steps

<Columns cols={2}>
  <Card title="Deep research" icon="search" href="/alice/deep-research" horizontal>
    How the knowledge base frames per-prospect research.
  </Card>
  <Card title="AI personalization" icon="pen-line" href="/alice/ai-personalization" horizontal>
    How knowledge becomes message copy.
  </Card>
  <Card title="Set up Alice" icon="settings" href="/alice/setup" horizontal>
    Where this fits in the setup sequence.
  </Card>
  <Card title="Core concepts" icon="layers" href="/core-concepts" horizontal>
    How the knowledge base relates to ICP and playbooks.
  </Card>
</Columns>
