Knowledge Intake

Teach Canonica your product before users need support.

Start from selected product links, docs, FAQs, release notes, setup notes, support macros, files, screenshots, and short recordings. Canonica prepares source-backed drafts for owner review before anything becomes support knowledge.

Selected public links, files, screenshots, and short media
KB, FAQ, surface, and answer-proposal drafts
Owner approval before publish
Knowledge Intake

Canonica product layer

Knowledge Intake

Start from selected product links, docs, FAQs, release notes, setup notes, support macros, files, screenshots, and short recordings. Canonica prepares source-backed drafts for owner review before anything becomes support knowledge.

Selected public links, files, screenshots, and short media

KB, FAQ, surface, and answer-proposal drafts

Owner approval before publish

Support truth flowReviewed
1Source content
2Product context
3Approved answer

Knowledge Intake

Start with product truth, not a blank help center.

Knowledge Intake gives founders a first-session path from existing product material to reviewed support content without creating an unbounded crawler or auto-publishing AI answers.

Inspect selected public pages

Paste a product or docs URL, review the support-worthy pages Canonica finds, and import only the pages you choose.

Bring existing files

Use TXT, Markdown, CSV, JSON, DOCX, and text-based PDF content as source material without retaining raw files by default.

Extract support context from screenshots

Upload screenshots/images when UI evidence matters. Canonica extracts support-relevant text, charges one support credit, and keeps only extracted source text for review.

Transcribe short support recordings

Use short audio/video clips when founders have walkthroughs or customer explanations. Transcription is capped, credit-charged, and never becomes official without review.

Prepare review drafts

Generate grouped drafts for articles, FAQs, product surfaces, and canonical answer proposals.

Keep answers governed

Accepted drafts publish into the existing support layer; canonical answers still go through mutation proposal review.

Stay cost bounded

Intake is owner-triggered, capped per job, license-gated, ledger-backed for paid media extraction, and avoids realtime listeners or hidden scheduler processing.

Workflow

From product material to reviewed support content.

Teach Canonica is built for first setup: add sources, generate drafts, approve what is right, and publish into the same runtime the widget and hosted help already use.

01

Create intake

Name the intake and add product/app URLs for context.

02

Add sources

Import selected pages, pasted content, support macros, release notes, supported files, screenshots, or short support recordings.

03

Review drafts

Edit, accept, or reject drafts before they become customer-facing support.

04

Publish accepted items

Write approved content into KB, FAQ, product surface, or canonical proposal paths.

Connected product truth

Intake feeds Canonica without creating a second knowledge system.

Published intake output lands in the same collections and freshness paths used by hosted help, widget search, page-aware suggestions, and governance.

Feature layer
01

Knowledge Intake

Start from selected product links, docs, FAQs, release notes, setup notes, support macros, files, screenshots, and short recordings. Canonica prepares source-backed drafts for owner review before anything becomes support knowledge.

02

Reviewed source

Published intake output lands in the same collections and freshness paths used by hosted help, widget search, page-aware suggestions, and governance.

03

Page context

Selected public links, files, screenshots, and short media

Connected surfaces
01

Knowledge Base

Accepted article drafts become reviewed KB content with embeddings attempted at publish time.

02

FAQ Management

Short answers can publish as owner-reviewed FAQs tied to source material and context keys.

03

Product Surfaces

Selected page context can become support-aware route and workflow mappings.

04

Governance

Canonical answer output stays reviewable through mutation proposals instead of auto-publishing authority.

Questions

What owners usually ask about knowledge intake.

Does intake crawl my whole site?

No. Canonica discovers bounded candidates and imports only the pages the owner selects.

Does imported content go live automatically?

No. Intake creates review drafts. Owners accept and publish selected items before users see them.

Does this replace the Knowledge Base?

No. It feeds the Knowledge Base, FAQ, product-surface, and answer-proposal workflows. Release notes can be added as source context, while changelog publishing stays in the changelog workflow.

Launch knowledge intake as part of the full support loop.

Canonica works best when knowledge intake stays connected to widget answers, hosted help, tickets, and answer review.