Knowledge grounding
Grounded in
your business context
Load your own documentation and build dedicated knowledge bases so Semarize reasons with your business context - not generic assumptions.
Why it matters
Generic evaluation
isn't good enough.
When Bricks evaluate conversations, they need to understand your specific products, processes, and policies. Knowledge grounding ensures evaluation is anchored to your reality.
Without grounding
With knowledge grounding
Sources
Upload your documentation
Feed Semarize the content that defines how your business operates. Product docs, playbooks, policies, enablement materials - anything that provides context.
Product docs
Feature pages, release notes, changelogs
Playbooks
Internal process guidance, objection handling
Policies
Security, legal, compliance documentation
Enablement
Training materials, FAQs, onboarding docs
Industry context
Vertical-specific terminology, benchmarks
Custom content
Any structured text relevant to evaluation
How it works
Three steps to
grounded evaluation
Upload documentation, organise into knowledge bases, then attach them to your Kits. Evaluation immediately becomes context-aware.
Upload documentation
Add your product docs, playbooks, policies, and enablement materials. Upload once, reference everywhere.
Organise into knowledge bases
Group documentation by domain, team, or use case. Each knowledge base has a clear scope that keeps evaluation focused.
Attach to Kits
Link knowledge bases to specific Kits. When the Kit runs, Bricks use the attached documentation as context for evaluation.
Benefits
Evaluation you can actually trust
Knowledge grounding closes the gap between generic AI evaluation and your specific business reality.
Improve accuracy
When Semarize evaluates whether a rep discussed pricing correctly, it references your actual pricing model - not generic assumptions about how pricing works.
Control interpretation
Keep evaluation anchored to approved product and policy language. Ensure Bricks interpret terms the way your organisation defines them.
Specialise by use case
Create separate knowledge bases for each team, region, or product line. A security compliance Kit references security docs. A sales Kit references the playbook.
Update without disruption
Change your documentation, refresh the knowledge base, and evaluation immediately reflects your latest language and decisions. No workflow changes needed.
Example
Knowledge bases in practice
Different Kits can reference different knowledge bases. A sales Kit uses the playbook. A compliance Kit uses policy docs.
Sales playbook
Discovery frameworks, objection handling guides, pricing documentation
Product documentation
Feature specs, release notes, integration guides, API docs
Compliance & policy
Security policies, legal requirements, regulatory frameworks
Make intelligence
actually intelligent.
Ground evaluation in your documentation so every signal reflects your business - not generic assumptions.