Knowledge base

The knowledge base is what makes Revyn yours. The AI buyer only knows what it says; Ask Revyn cites it; scenarios are drafted from it. A thin knowledge base gives you a generic buyer; a good one gives you the buyer you will meet on Monday.

#Org knowledge base

Admins and managers manage it under Knowledge Base. Add:

• Documents. PDFs, Word files, slide decks, plain text, Markdown. Pricing sheets, battlecards, case studies, security one-pagers, objection-handling guides.
• Web pages. Paste a URL; Revyn fetches and indexes it, and can re-fetch on a schedule.
• Objection responses, promoted from objection intelligence with the approved answer.

Each document is chunked, embedded and indexed. A document can be marked buyer-visible (the AI buyer may draw on it: your public pricing, your competitor's positioning), rep-only (Ask Revyn may cite it, the buyer never sees it: your internal battlecard), or both.

#The context pack

From the documents, Revyn builds a context pack: a compact, structured summary of what you sell, to whom, against whom, at what price, with what objections. The pack is what is injected into every buyer and every Ask Revyn session, so grounding is fast and consistent. Rebuild it after a large upload, or let it rebuild nightly.

#The knowledge graph

Behind the pack, documents are linked into a graph of products, personas, competitors and objections. It is what lets a scenario be "grounded in the security objection for the enterprise persona" rather than in a document. You do not manage the graph directly; it is built from the documents and the objection library.

#Personal knowledge base

Individual accounts do not upload documents. Instead, at setup you give Revyn the URL of the company you sell for. It researches the company and builds a personal context pack: product, ICP, competitors, pricing where public, recent news. You can review and correct the pack under Knowledge Base, add notes, and re-run research when things change.

#Live on the call

During a practice call the knowledge panel shows which documents the buyer is currently drawing on. When the buyer quotes your competitor's price, you can see that it came from page four of the battlecard. If it says something wrong, that is a document to fix.

#In Ask Revyn

Every answer that uses the knowledge base cites the document inline. If a document is wrong, fix the document; the next answer will be right.

#Keeping it good

• Prefer fewer, current documents over many stale ones. A 2024 pricing sheet actively hurts.
• Mark internal material rep-only. A buyer who knows your discount floor is not a realistic buyer.
• After a lost deal, promote the objection that lost it, with the answer you wish you had given.
• Rebuild the context pack after any large change.