When an agent needs to answer "does our API do SAML?", it cannot find the doc because the doc is in four tools.
That 40-page competitor teardown you paid a consultant for — read once, never again.
Sales keeps asking for "the Acme case study" and marketing keeps hand-crafting a new version.
Because the institutional memory lives in Slack threads that vanish behind a free-tier wall.
Point at a Notion workspace, a Google Drive folder, a website. Knowledge scrapes, converts to markdown, dedupes.
When Outbound says "our enterprise SSO supports SAML and SCIM", it links the exact doc it read — not a vibe.
Tag docs as internal / enablement / customer-facing. Reply Guy never quotes internal roadmap at a prospect.
Operational Context (ICPs, playbooks) + Knowledge (product, research) are one continuous store the agents can traverse.
Fast grep for filename + path, semantic recall for fuzzy questions, always with the raw doc for inspection.
Notion/Drive sources re-sync on a schedule. Stale docs are flagged so no agent quotes a six-month-old price.
Import a competitor teardown once — every outbound, objection-handling, and reply agent benefits forever.
A new rep can ask "how do we beat Salesforce on time-to-value?" and get an answer grounded in your real docs.
Customer-facing tags mean the agent physically cannot paste an internal-only doc into an outgoing email.
PDF, DOCX, PPTX, HTML, Notion export, Google Drive. Converted to markdown, links preserved.
Point at blackmagic.engineering/docs and it pulls the full site, stays in sync, respects sitemap and robots.
When an agent writes a draft, citations are inline. Edit the draft, the citations follow the text.
Every imported doc gets an LLM-generated one-paragraph summary at the top so agents can skim before reading.
A template for closed-won post-mortems (ICP, pain, objection, outcome) that every agent knows how to query.
When multiple drafts need a fact no doc can answer, Knowledge flags the gap and suggests a doc to write.
Context is operational — ICPs, playbooks, brand voice. Knowledge is long-form — docs, research, case studies. Same on-disk store, different folders and different agent permissions.
No. Every doc has an audience tag. Outbound-facing agents are scoped to the customer-facing tag and cannot read internal-only docs.
Yes. Connect Notion, pick the workspaces / pages to sync, and Knowledge keeps a local markdown mirror that re-syncs on a schedule you set.
Edit it in place — or in Notion upstream. The next sync picks up the fix and every agent uses it immediately.