Rules and knowledge

The presenter and moderator only say what you've taught them. Slides and scripts cover the talk itself. For everything else attendees might ask, you give them knowledge (documents and FAQs) and rules (how to behave and what to stay away from). When neither covers a question, the presenter says it doesn't know and offers an email follow-up, and the question lands in your Inbox.

Where each kind of guidance goes

Slide-level context is covered in Scripts and presenter context, and persona settings in Presenters, moderators and voices.

Knowledge bases

A knowledge base is a named set of documents and FAQ entries. It belongs to the workspace, so several webinars and personas can share it.

1. Go to Knowledge bases and click New knowledge base. Give it a Name and a Description.
2. On the Documents tab, add your material with the + next to the search box:
   • Upload or pick files… opens Add documents: upload files, pick them in Google Drive, or add a recent file. You can also drop files anywhere on the tab. Each file becomes a document.
   • Webpage… adds a page from the web by its address (see below).
   • Write a document creates one you write or paste yourself. Click Edit on it later to change it.
3. On the FAQ tab, add question and answer pairs (see below).
4. Attach it to a webinar under Settings → AI knowledge → Knowledge bases. Knowledge bases attached there are shared by the presenter and the moderator.

The list groups documents by where they come from, with what needs attention (still converting, or couldn't be converted) at the top. Sizes are shown in tokens, roughly how much of the AI's reading budget a document uses (about four characters per token). Open a document to read it; the small Markdown switch next to its name shows the text as stored.

Size limit

Each knowledge base holds up to 500k tokens, about 2 MB of text, FAQ included. A written document can be up to 200k characters. How full it is shows at the right end of the tab row, and the knowledge bases list shows each one's size.

Documents count in the order they were added. When a knowledge base is full, the document that doesn't fit and every document added after it are kept but not used in webinars: they're dimmed in the list and marked "not used". The publish dialog also tells you when an attached knowledge base is over its limit. To make room, delete earlier documents, or split the material into several knowledge bases and attach them all.

Documents are Markdown text, so headings and lists help. Write them the way you'd brief a new colleague: plain facts, current numbers, and the answers you give on sales calls. If something is off-limits, say so in the rules rather than leaving it out and hoping nobody asks.

Uploading files

You can upload PDF, Word (.docx, .doc), Excel (.xlsx, .xls), OpenDocument (.odt, .ods), RTF, EPUB, HTML, CSV, Markdown and plain text files, up to 100 MB each. Each file is converted to a Markdown document, usually within seconds; large files can take a minute.

• Files are read-only. A document made from a file is named by its file, and you can read the converted text but not edit it. To change it, edit the file, delete the document and upload the file again. To write something yourself, use Write a document.
• The file is kept. Open the document to Download it; deleting the document is under ⋯.
• Recent files. Files added to any knowledge base in the workspace stay under Recent files in Add documents for 30 days. Click one to add it to this knowledge base without uploading it again. Files already here are marked.
• Duplicates are skipped. If the same file is already in the knowledge base, it isn't added again.
• Scanned PDFs aren't supported yet. A PDF that's only images has no text to convert.

From Google Drive

In Add documents, click Google Drive, sign in to Google and pick one or more files. Your Google account can be different from your Webinaric login.

• Google Docs come in as Markdown, exported by Google. Images are left out. For a Doc with several tabs, only what Google exports is included (usually the first tab).
• Google Sheets are converted to Markdown tables.
• Other files in Drive (PDF, Word, Excel and the other formats above) are converted like uploads.

These documents are read-only too, and named like the file in Drive. When the file changes in Google, open the document and click Sync to bring in the new version (a rename in Drive comes along too). The arrow next to it opens the file in Google. Deleting the document here leaves the file in Google Drive.

From a webpage

Click + → Webpage… and paste the page's address, for example https://example.com/pricing. The page is fetched and its main text (without menus, headers and footers) becomes a Markdown document named after the page.

• Public pages only. Pages behind a login can't be fetched. Pages that build their text with JavaScript after loading may come out empty; copy the text into Write a document instead.
• Read-only, and kept as fetched. The document doesn't change when the page does. Open it and click Sync to fetch the page again; the arrow next to it opens the page.
• Each page is added on its own: links on the page aren't followed.

FAQ entries

FAQ entries are question and answer pairs the moderator can answer directly in the chat, without waiting for the presenter. There are four ways to add them:

• By hand: on the FAQ tab, click + and choose Add a question.
• From your documents: click + and choose Generate from documents. The questions are saved right away and listed under New for a few minutes, so you can review them. Edit or delete any that aren't right.
• From real questions: on a webinar's Q&A tab, open a question and click Promote to FAQ. When you answer a question in the Inbox, tick Add to knowledge base. Either way, you pick the knowledge base it goes into.
• From a recording: importing a recording of the talk drafts FAQ entries from the questions asked and answered in it. You review them before they're added.

Additional context

Under the webinar's Settings → AI knowledge, Additional context for the presenter describes this particular webinar: who the audience is, what you want them to learn or do, the tone, and the call to action. It's never shown to attendees. The wand can draft it from your slides.

Sample data

Rules

A persona's Rules apply wherever that persona hosts. Use them for behaviour and boundaries, for example:

• "Don't quote prices. Offer a call with sales instead."
• "Don't compare us with named competitors."
• "Don't promise features or dates that aren't in the knowledge base."
• "Keep answers short and practical."

If a rule should apply to one webinar only, put it in that webinar's Additional context instead.

When changes reach attendees

A published version keeps its own copy of the knowledge bases, rules and context it uses. After you edit a knowledge base, publish the webinars that use it again; until then, sessions use the previous copy. Deleting a knowledge base removes it from all webinars and personas, but published versions keep their copy.