Skip to main content

Context & glossary

Context is the single biggest lever on summary quality. Add the names, acronyms and background ScribX can't infer from the audio alone, and every summary and translation comes out sharper. Manage it on the Context page in the web app (Settings → Context).

The Context page​

The Team Context page with manual, Outline and Notion sources12
  1. 1Add context manually, or link Outline / Notion
  2. 2Create a new context entry
Context — knowledge the AI uses to write sharper summaries and translations.

Context sources​

You can add context three ways:

  • Manual — write it yourself: a glossary of product names, people and acronyms, or a few lines of background. Markdown is supported (headings, lists, emphasis).
  • Outline — link Outline documents as reusable context.
  • Notion — link Notion pages.

Entries marked as defaults apply to every meeting automatically, so you set your glossary once.

Example glossary

A short Markdown glossary, marked as a default, is usually all you need. The Context field renders Markdown, so what you type formats in the preview:

**Glossary**
- **ScribX** — our product (never "scribe" or "scribex").
- **ARR** — Annual Recurring Revenue.
- **DLQ** — dead-letter queue.

**People**
- **Mai Tran** — Product Lead.
- **Alex Kim** — Eng Lead (sometimes heard as "Alex Km").

What context fixes​

  • Names & acronyms — "ARR", "DLQ", a teammate's name spelled correctly.
  • Background — what the project is, who's who, what last week's decision was.
  • Translations — keeps product terms and brand names consistent across languages.
tip

A short, high-signal glossary beats a long dump. List the terms ScribX is most likely to get wrong — product names, people, initialisms — and mark it as a default.

Where it's used​

Context flows into:

What's next?​