Customizing for Use Cases

MimicScribe’s prompts, profiles, and vocabulary are all editable. This page shows how to configure them and includes examples for common workflows.

Meeting summary structure

By default, the summary adapts its structure to each meeting (the Auto view). You can also apply a fixed summary view that renders the summary the same way every time. Pick a view from the summary’s “View” switcher after a meeting, or set a global default in Settings.

MimicScribe ships with four built-in views:

View	What it produces
Simple	A single skimmable Summary section, ordered by importance.
Walkthrough	The meeting reconstructed in the order it happened, plus Open Questions.
By Participant	One section per person — what each contributed — plus Open Questions.
Decisions & Open Questions	A Summary, then Decisions, then Open Questions.

The built-in views always produce their named sections. Auto includes Summary and Open Questions when the meeting has content for them and adapts the rest to what was discussed. Action Items (with owners, deadlines, and calendar export) are generated separately regardless of the view.

Per-view customization

Settings > Meeting Recording > Summary Views > [view name] > Summary Guidance — edit how any view shapes the summary, or add your own. A view you create is honored at the strength you write it: a loose preference (“focus on decisions and blockers”) adapts to the meeting, while an explicit requirement (“always include a Risk Register”) is always included. To force a section even when the meeting didn’t cover it, start a line with REQUIRED:.

Custom summary prompts

Settings > Meeting Recording > Summary Template — a global override that applies when no per-view instructions are set. Replace or edit the default to fit your workflow.

Sales call follow-up

Produce a brief follow-up email draft and a separate internal summary:

FOLLOW-UP EMAIL:
- Thank the prospect by name
- Restate the key points of interest they expressed
- List any commitments or next steps

INTERNAL SUMMARY:
- Deal stage and signals (positive/negative)
- Objections raised
- Action items with owners

## Strategic Opportunities
- Based on what was discussed, identify 1-3 specific opportunities
  where we could provide additional value to their business.
  Reference concrete details from the conversation, not generic suggestions.

Recruitment interview debrief

Summarize this interview in two sections:

CANDIDATE ASSESSMENT:
- Strengths demonstrated (with specific examples from the conversation)
- Areas of concern or gaps
- Culture fit observations
- Overall recommendation: Strong Yes / Yes / No / Strong No

HIRING TEAM NOTES:
- Key questions asked and quality of responses
- Follow-up questions for the next round
- Comparison notes vs. role requirements

Product review / user feedback session

Summarize this product feedback session:

KEY FINDINGS:
- List each piece of feedback as: [Feature/Area] — what the user said, their sentiment (positive/negative/neutral)
- Note exact quotes for particularly strong reactions

THEMES:
- Group findings into 2-4 themes
- For each theme, note how many participants mentioned it

ACTION ITEMS:
- Bugs or issues reported (with reproduction steps if mentioned)
- Feature requests with priority signals (e.g., "would be a dealbreaker")
- Items to bring back to the team

Engineering standup

List each participant's update in this format:
- **Name**: What they did, what they're doing next, any blockers

End with a section called "Action Items" listing anything someone committed to doing.

Assistant template (live overlay)

Settings > Meeting Recording > Assistant Template — controls the AI briefing content shown when you press the meeting assistant hotkey mid-call.

Sales overlay

Tailored for discovery and closing calls. Tracks whether the call objective has been addressed and surfaces next steps alongside the standard talking points.

If Question: ❓ "[Question]" (before bullets)

Content: 1-3 ultra-brief talking points (≤10 words each). **Bold** names/numbers. Always use bullets.
- Question for me? → key points for my answer.
- No question? → what to say or ask next.
- If key requirements haven't been covered yet, remind me.

💬 [Interpersonal dynamics suggestion] (after bullets)

If Summary: Follow with "---", then a "Next Steps" section listing
agreed-upon actions AND outstanding items that still need discussion.

Dictation profiles

Settings > Voice Typing > Dictation Profiles — create per-app overrides with custom prompts.

Email with signature and calendar link

Create a profile matching your email app. In the Dictation Prompt:

Format the dictated text as a professional email.
Always end with this signature:

Best,
[Your Name]
Book a time: https://cal.com/yourname

Enable Send Your Context and add your name and role in Your Context so the AI has it available.

Casual messaging

Create a profile matching your chat apps (Slack, Messages, Discord). In the Dictation Prompt:

Transcribe naturally. Do not formalize the text. Keep it
conversational — contractions, casual punctuation, lowercase
where appropriate. Do not add a greeting or sign-off.

Technical writing

Create a profile for your code editor or documentation tool:

Preserve technical terms exactly as spoken. Use Markdown
formatting. Do not simplify jargon or expand abbreviations.
Spell code identifiers in camelCase or snake_case as context
suggests.

Transform prompt

Settings > Voice Typing > Transform Mode > Transform Prompt — controls how transform mode responds to voice commands.

Editing assistant

You are a writing editor. When given text and an instruction,
apply the edit precisely. Match the original tone and style
unless told otherwise. Return only the edited text with no
commentary or explanation.

Reference Documents

Settings > Your Context > Reference Documents — add URLs or files that the AI can reference during meetings, voice instructions, and summaries. Content is automatically processed into searchable sections and retrieved based on what’s being discussed.

How it works

When you add a URL or file, MimicScribe fetches the content, uses AI to split it into semantic sections, and indexes them for fast retrieval. During a meeting or voice instruction, the most relevant sections are automatically included in the AI’s context based on what’s currently being discussed.

Good candidates for reference documents

• Product documentation or knowledge base pages
• Client/CRM notes for upcoming meetings
• Company wiki pages with team structure, terminology, or processes
• Project briefs or specifications

Adding documents

• Add URL — paste a URL and click Add URL. Works best with public pages or pages that don’t require authentication (e.g., llms.txt files, public documentation).
• Add File — click Add File to select local text files (.txt, .md, .json, .yaml).
• Drag and drop — drop files directly onto the Reference Documents section.

You can add up to 10 reference documents. Each document can be up to 200,000 characters. Click the document icon on any processed source to preview how it was split into sections.

Where reference documents are used

Feature	How it’s used
Meeting summary	Relevant sections included for richer, more accurate summaries (larger context budget)
Meeting assistant	Relevant sections included based on what’s being discussed
Voice instructions	Relevant sections included based on your instruction and selected text

Reference documents are not used for dictation (vocabulary handles terminology) or speaker attribution (structured task that doesn’t benefit from reference content).

Your Context

Settings > Your Context — included in AI requests across features. A well-written context improves all AI outputs.

Example

Name: Jordan Lee
Role: Product manager at Acme Corp
Tools: Linear for issues, Notion for docs, Google Meet for calls
Writing style: Clear and direct. No jargon unless talking to engineers.
Calendar: https://cal.com/jordanlee
Vocabulary: Acme Corp, OKRs, Q3 roadmap, Project Falcon

Vocabulary

Settings > Your Context > Vocabulary — add words and names that the AI should spell exactly as written. Type a term and click Add. Terms appear as removable chips.

Use this for proper names, company names, product names, acronyms, and technical terms that the transcription model might misspell. Vocabulary terms are separate from the free-form Your Context field — they’re specifically for exact spelling.