Publish trusted knowledge
Create help documents with visibility, language, tags, site scope, and a clear publish lifecycle.
Create trusted help content, publish it for the right site, see whether each document is ready for AI, and give customer service answers a clear source to cite.

Native knowledge documents are live today. Product and Blog source projections remain separate planned extensions rather than hidden automatic ingestion.
Create help documents with visibility, language, tags, site scope, and a clear publish lifecycle.
See whether the latest published document is ready to support customer answers and retry failed processing from the dashboard.
Use published knowledge as the trusted source behind AI Customer Service responses and citations.
Good AI support depends on a small, current, governed source of truth rather than unrestricted access to every workspace record.
Create Markdown help content with visibility, locale, tags, and optional site scope.
Move documents through a controlled lifecycle while keeping the currently published knowledge explicit.
See whether published knowledge is ready for AI answers and retry processing when the current version needs attention.
Keep public and site-scoped knowledge separate from internal or unpublished material.
Carry the supporting document into grounded customer answers and conversation review.
Reuse approved Product and Blog publications as managed knowledge sources without copying ownership rules.
Write trusted help content, publish it for the right audience, and let customer service use only the current approved version.
Create the help content, choose visibility, language, tags, and optional site scope.
Publish the current document so it can become eligible for site AI answers; archive or restore it as the content lifecycle changes.
AI Customer Service answers from current permitted knowledge and preserves the supporting source in the conversation.
Support customer answers, internal review, help content, and product discovery without indexing private customer data.
Organize setup guides, billing explanations, policies, troubleshooting, and FAQs.
Make active product descriptions, specifications, and approved FAQs retrievable.
Give authorized team members one current source of answers and evidence.
Provide public, fresh, site-scoped evidence for accurate chatbot answers.
Only approved content sources enter retrieval. Customer records, submissions, secrets, drafts, and stale content stay outside public AI search.
Native knowledge documents support Markdown content, visibility, locale, tags, site scope, and a publish/archive/restore lifecycle as the rollout continues.
No. Public customer answers require current permitted published knowledge; drafts, archived documents, and private customer records stay outside that path.
Not yet. Product and Blog source projections remain planned extensions so those domains can keep their own publishing and ownership rules.
Knowledge Base is rolling out to Pro workspaces and is designed to ground AI Customer Service on published sites.
Continue with the most relevant parts of the Cogo Site workflow.
We use cookies
We use cookies to enhance your browsing experience and analyze site traffic. By clicking 'Accept', you consent to our use of cookies. Learn more about our cookie policy