Meeting context: presets, glossary and documents
Two minutes spent before the call is what turns the prompter from a phrase generator into something that quotes your numbers. Presets are reusable — most people end up with three or four.
What goes into a preset
Every field is optional, and every field changes the answers.
- 01Your role and the goal of the call — “founder raising a seed round”, “support engineer resolving a billing complaint”.
- 02Who you are talking to, and what they care about.
- 03Tone: short, detailed, formal or friendly.
- 04Glossary: terms that must not be translated loosely — product names, legal terms, units.
- 05Documents: a price list, a spec, a CV, a deck.
How documents are used
An attached file is split into passages and indexed so that the relevant few can be put in front of the model when it drafts an answer. The whole document is not sent on every call, and the passages that were used are shown with the answer.
Indexed passages live on the server and are deleted 30 days after the last meeting that used them. If that is not acceptable for a particular document, do not attach it — the prompter still works from the call itself.
Choosing a preset for a call
Presets are chosen on the start screen, one per session, and can be left empty. The name of the preset is kept with the call in History, so you can see later which context produced which answers.
Read next
- The AI prompterHow the prompter decides when to suggest an answer, how to ask it for one, and how to make its suggestions specific to your meeting instead of generic.
- History, summary and exportWhat is kept after a call, how the summary and task list are produced, how to rename a speaker, and how to export with or without the translation.