Skip to main content
Adapt’s knowledge base is its long-term memory. It stores durable facts, definitions, procedures, and preferences about your organization, so Adapt carries that context into every future conversation without you having to re-explain it.

​
What belongs in the knowledge base

  • Business context — Metric definitions, KPIs, and terminology (how you define “active user” or “MRR”)
  • Facts — Durable information about your company, customers, products, and vendors
  • Procedures — Standard operating procedures and recurring workflows
  • Preferences — How your team likes reports formatted and which metrics matter most
Knowledge is for durable, shared context. For live or fast-changing data — today’s revenue, current pipeline, this week’s tickets — Adapt pulls from your integrations in real time instead of storing it.

​
How knowledge gets in

1

Adapt learns automatically

As you work, Adapt notices durable facts, decisions, and preferences and saves them on its own — no action required.
2

You tell Adapt directly

Say it in a conversation and Adapt will remember it:
3

You add it manually

Create entries yourself in Settings > Knowledge.

​
How an entry is structured

Each knowledge entry has two parts: Adapt matches an incoming question against the retrieval trigger, then loads the content. Writing triggers the way people actually ask gives the best results. Example

​
Personal vs. organization knowledge

Every entry is scoped to who it’s for: Adapt sets the scope automatically. When the content is clearly one person’s own preference or style — how they like emails formatted, their PR title and branch conventions, their writing voice — Adapt saves it as personal knowledge so it doesn’t add noise for the rest of the team. When a fact is genuinely team-shared or ambiguous, Adapt defaults to organization scope. At retrieval time, your personal entries and your organization’s entries are searched together, so your preferences still apply seamlessly — they just stay private to you.

​
How Adapt uses knowledge

  • Surfaced automatically — Relevant entries are pulled in based on your message before Adapt answers.
  • Searched on demand — Adapt can search the knowledge base when a task needs more context.
The result: consistent answers that reflect your definitions and preferences, without you repeating yourself.

​
Manage your knowledge base

Go to Settings > Knowledge to:
  • Browse every entry, switching the scope selector between Organization and Personal
  • Search by meaning, not just keywords
  • Add a new entry (retrieval trigger + content)
  • Edit an existing entry
  • Remove entries that are stale or no longer true

​
Best practices

Keep entries atomic

One fact, preference, or procedure per entry. Split unrelated facts apart.

Write triggers like real questions

Phrase triggers the way your team actually asks, including names and synonyms.

Store durable context

Save what stays true over time. Let Adapt fetch live data from integrations.

Review periodically

Remove outdated facts so Adapt always reflects current reality.

​
Knowledge vs. skills

Knowledge and skills both give Adapt context, but they serve different purposes:
  • Knowledge captures what is true about your business — facts, definitions, and preferences.
  • Skills capture how to do a task — workflows, templates, and step-by-step procedures.

Skills

Package workflows and templates that Adapt loads on demand

Integrations

Connect your tools so Adapt can pull live data and take action