Knowledge base

Give the agent things it needs to know — pricing, FAQs, policies, a full website crawl.

Updated June 26, 2026

The Knowledge tab is where you add context the agent draws on during
conversations. Think of it as the set of documents a new team member would
skim on their first day.

Three ways to add knowledge

  1. Write it yourself — paste a title + markdown body. Great for
  2. Upload a file — PDF, DOCX, or TXT. We extract the text and chunk it.
  3. Crawl a website — enter a URL, we fetch the page + its links. Set up

How the agent uses it

On every inbound message, we search the knowledge base for chunks
semantically related to what the contact just said, and attach the top
matches to the agent's context. It's not "read everything always" — the
agent gets what's relevant to this turn.

What to put in

Good candidates:
- Pricing, packages, service menus
- FAQ — common questions with authoritative answers
- Business hours, location, contact info (beyond what's on the website)
- Policies — cancellations, refunds, deposits
- Product specs, SKUs, features

Bad candidates:
- Huge marketing pages (high token cost, low signal)
- Blog posts unless they answer FAQs
- Internal operations docs the agent shouldn't reveal

Recurring crawls

For pages that change (pricing, availability), schedule a recurring crawl —
daily or weekly. We only re-index when content has actually changed, so
your token bill doesn't climb for pages that stay still.

Deletion

Remove a knowledge entry and it stops being used immediately. There's no
caching — next inbound message, it's gone from the agent's context.