Organisational memory the AI can actually use.
A wiki where pages link to the records they describe. Public articles drive the customer portal KB; internal articles ground every AI answer in your own knowledge.
What Docs does for you
Pages, spaces, search
Standard wiki shape. Rich text, tables, code blocks, mentions, and full-text search out of the box.
Linked to records
Mention an account, a deal, or a project, and the page becomes a node on the graph. Show up against the record automatically.
Powers the AI
Internal docs are RAG sources for every Cyril agent. Update a doc, agents update their answers — no retraining, no fine-tuning.
Permissions you control
Page-level visibility: org-wide, team, or specific roles. Public pages render on the customer portal; private ones never leave the org.
AI answers are only as good as what you write down.
Most "AI assistants" hallucinate because they don’t have your team’s tribal knowledge. Cyril’s Docs module is where you write that knowledge once — and every agent in every module immediately uses it.
- Update a doc → every agent’s answer updates
- Public pages drive the customer KB
- Mention syntax (`@account/Acme`) creates real graph edges
Common Docs questions
Bulk import from Markdown and HTML is on the Phase 4 roadmap. Confluence and Notion-specific importers are planned but not yet shipped.
Be one of the first to use Cyril.
Join the waitlist for early access. We'll only email you when there's something real to share.