Templates

Templates are saved prompt instructions that instruct your AI provider on how to structure, format, and constrain its output. They are designed for recurring workflows such as customer follow-up emails, engineering sprint syncs, interview debriefs, and architecture decision records (ADR).

1. Create a template

1. Open Settings → Templates.
2. Click Add template.
3. Provide a recognizable name and slash-command shortcut (e.g., /follow-up, /actions).
4. Select the operational scope:
   • Single meeting: For summarizing or extracting action items from an individual conversation.
   • Multiple meetings: For comparative analysis, multi-stakeholder synthesis, or periodic rollups.
5. Write your structured prompt, save it, and test against sample meetings.

Note: Built-in templates are read-only defaults. You can duplicate them to create custom versions with tailored prompt instructions.

2. Best practices for robust prompts

Effective meeting prompts explicitly define the desired schema, field definitions, and grounding boundaries:

Extract an action-item table with columns: Task, Owner, Due Date, and Spoken Evidence.

Constraints:
1. Use only explicit commitments made in the selected meeting transcript.
2. If an owner or due date was not stated, write "Unassigned" or "Not specified".
3. Preserve all technical codenames and proper nouns exactly as spoken.

Pro Tip: Never ask the model to guess omitted details. Use Custom vocabulary to ensure proper nouns and acronyms are preserved with correct casing.

3. Applying templates

• Meeting Detail Action: Select a template directly from the meeting summary dropdown.
• Slash Commands in Chat: Type / in the chat composer to open the autocomplete template selector.

Always review generated notes against the transcript before treating them as formal project records.