Ground your agent’s responses in your own content.
The knowledge base gives your agent access to your own content — product docs, support articles, company policies, pricing pages, FAQs. When a user asks a question, the agent retrieves the most relevant content and uses it to generate an accurate, grounded response.Instead of scripting every possible answer, you upload your content once and let the agent find what it needs.
For URL and integration data sources, set a refresh rate to keep your knowledge base in sync with the source. You can do this on import, or retroactively by pressing the checkbox next to the data source or folder.
When your agent queries the knowledge base, it finds chunks of content most similar to the user’s question. LLM chunking strategies use AI to split your content into optimized chunks — improving retrieval quality and helping your agent find useful answers.
Strategy
Description
Best for
Smart chunking
Breaks content into logical sections grouped by topic
Complex documents with varied topics (policy docs, course catalogs)
FAQ optimization
Generates sample questions each section could answer
Product info, help center content
Remove HTML and noise
Cleans up messy formatting to make text easier to process
Blog posts, markdown-heavy docs, CMS exports
Add topic headers
Adds brief summaries at the start of each section
Long documents needing context (research papers, onboarding guides)
LLM chunking strategies consume credits on each sync. If your content doesn’t change often, reduce your refresh rate to avoid unnecessary credit usage. No credits are consumed when syncing without an LLM chunking strategy selected.
Chunking strategies aren’t one-size-fits-all. Experiment with different combinations on each data source to find what gets your agent the best results.
Attach metadata to any data source to filter what gets returned when your agent queries the knowledge base. Useful when you have multiple brands, product lines, locales, or subscription tiers and your agent needs to make sure the right information reaches the right users.For example, if you have different policies for enterprise and self-serve customers, tag each data source with plan: enterprise or plan: self-serve and filter queries accordingly.Click + in the Metadata section of the import config to add key-value pairs:
If an import fails, hover over the error icon for details. Failed files are handled gracefully — they won’t break your project and the rest of your import will still process.