10 AI Prompts για Συνόψεις Συσκέψεων και Action Items

You are an executive assistant. Read the meeting notes below and write a TL;DR for a busy leader who was not in the room.

Output exactly:
1. A one-sentence headline of what this meeting was really about
2. "Key outcomes" — 3 bullets
3. "Decisions made"
4. "Risks or timeline impacts"

Ignore small talk, scheduling logistics, and minor tangents. Do not use vague phrases like "the team discussed" — state what was actually decided. Keep it under 150 words.

Notes:
{{transcript}}

Extract every action item from the notes below into a table with these columns: Task | Owner | Due Date | Priority (High/Medium/Low).

Rules:
- Only create a row when there is a clear task.
- If the owner was not clearly stated, write "UNASSIGNED." If no due date was given, write "TBD." Never guess an owner or a date.
- Below the table, add a section titled "Needs clarification" listing any task where the owner or deadline is missing.

Notes:
{{transcript}}

You are a professional minute-taker. From the notes below, produce formal meeting minutes in this structure:

- Meeting title, date, and time
- Attendees (and anyone noted as absent)
- Agenda items discussed
- Decisions made (numbered)
- Action items (table: Owner | Action | Deadline)
- Open questions / parking lot
- Next meeting

Use neutral, factual language. Do not add commentary or interpretation, and do not invent motions, votes, names, or any detail that is not in the notes.

Notes:
{{transcript}}

{{transcript}}

Above is a raw meeting transcript. First, find and quote the 5–8 most important moments — decisions, commitments, and disagreements. Then, using only those quotes, write a summary with:
- Context (one line)
- Key decisions
- Action items (Owner, Due date — write UNASSIGNED/TBD if not stated)
- Open questions

The speaker labels may be generic (Speaker 1, Speaker 2). Attribute statements to the label given. Do not guess anyone's real name.

Using the meeting notes below, write a short follow-up email to attendees.

Structure:
- A one-line thank you
- "Quick recap" — 3 to 4 key points
- "Decisions made"
- "Your action items" — grouped by person, each with its deadline
- A closing line confirming the next meeting (if one was set)

Professional but warm. Under 200 words.

Notes:
{{transcript}}

Build a decision log from the notes below. For each decision, output a row:

Decision | Why (one line) | Decision owner | Alternatives considered or rejected

Only log decisions that were actually agreed — not topics that were merely discussed. If something was explicitly postponed, list it separately under "Deferred — not yet decided."

Notes:
{{transcript}}

From the notes below, pull three separate lists:

A. Open questions — things asked but never answered
B. Blockers — anything stopping progress, and who or what is blocked
C. Risks or concerns raised

Note who raised each item. Do not include anything that was resolved during the meeting. If a list has nothing in it, write "None identified."

Notes:
{{transcript}}

You are a sales assistant. Summarize the following client call for our records.

Sections:
- Key points (3–5 bullets)
- Client pain points
- Buying signals (timeline, budget, or intent cues)
- Objections or concerns (quote the client where possible)
- Competitor mentions
- Next steps (action, owner, due date)

Only list next steps that move the deal forward.

Call notes:
{{transcript}}

Summarize these 1:1 notes between a manager and their direct report.

Sections:
- Main topics discussed
- Concerns raised by the report
- Wins to recognize
- Manager follow-ups before the next 1:1

Rules: separate facts from interpretation (label anything that's an inference). Use neutral language — no evaluative labels like "strong performer" or "problematic." Stick to what was actually said.

Notes:
{{transcript}}

Here is a meeting summary: {{summary}}

Convert every action item into a prioritized task list. For each task, output:

Priority (P1/P2/P3) | Task | Owner | Due date | Effort (S/M/L)

Sort by priority, P1 first. Put anything that's blocked or missing an owner in a separate "Needs clarification" section at the bottom.