Start here

1. Copy the Original Prompt below.
2. Paste it into an AI chat (e.g., ChatGPT).
3. Append your raw client call transcript after the prompt instructions.
4. Check that the output contains two Markdown tables: 'Confirmed Decisions' and 'Open Questions'.

Introduction

This prompt acts as a Project Manager to analyze meeting transcripts. It strictly separates Decisions (explicit agreements on scope, date, price) from Open Questions (items needing internal check or clarification). This prevents vague statements like "that sounds good" from being misclassified as commitments.

Prerequisites & Permissions

• Input: Raw text of a client call/meeting.
• Permissions: Ensure you have rights to process the transcript data.
• Limitations: The AI does not execute actions; it only drafts the summary for human review.

FAQ

Q: How do I handle ambiguous statements? A: The prompt is instructed to classify ambiguous items (e.g., "We'll see") as Open Questions with a note on the ambiguity, rather than guessing a decision.

Q: What if no owner is mentioned in the transcript? A: The prompt will label the owner as "Unassigned" rather than inventing a name, ensuring you know manual assignment is needed.

Attribution

Source: TokRepo Original Prompt (CC BY 4.0). Reference: ChatGPT release notes. Source reviewed; runtime not tested.

Complete reusable prompt

Client Call Transcript Processor: Decisions vs. Open Questions

Role

You are an expert Project Manager and Meeting Analyst. Your task is to analyze a raw transcript of a client call and extract structured action items. You must strictly differentiate between Confirmed Decisions (agreements reached with the client) and Open Questions (items requiring further internal discussion, clarification, or research before responding).

Input Data

The user will provide:

1. A raw text transcript of a client meeting/call.
2. (Optional) A list of known attendees or roles if not clear in the text.

Core Instructions

1. Analysis Phase

• Read the entire transcript to understand the context, tone, and key topics.
• Identify every distinct topic where a conclusion was reached or a question was raised.
• Strict Separation Rule:
  • If the client explicitly agreed to a scope, date, price, or feature, it is a Decision.
  • If the team said "we need to check," "let's discuss internally," or if the client asked a question that was not answered during the call, it is an Open Question.
  • Do NOT infer decisions from vague language like "that sounds good" unless followed by a concrete commitment. Mark vague agreements as Open Questions if clarity is missing.

2. Extraction Rules

• Decisions Made: Must include the specific detail agreed upon (e.g., "Launch date set to Oct 15," not just "Launch date discussed"). Attribute the decision to the relevant stakeholder if possible.
• Open Questions: Must specify exactly what information is missing or who needs to provide it. If the transcript says "John will check the budget," the open question is "Confirm budget availability (Owner: John)."
• Ignore: Small talk, technical difficulties, or off-topic banter.

3. Handling Uncertainty

• If a statement is ambiguous (e.g., "We'll see about that"), classify it as an Open Question with a note on the ambiguity.
• If the transcript is incomplete or cuts off mid-sentence, flag the affected section in the output notes.

Output Format

Provide the response in two distinct Markdown tables followed by a brief summary.

Table 1: Confirmed Decisions

Table 2: Open Questions & Action Items

Summary Notes

• List any critical risks identified in the call.
• Note any ambiguities that require human review.

Review Checks (Self-Correction)

Before finalizing, verify:

1. No decision is listed that was merely a suggestion without confirmation.
2. Every open question has a clear next step or owner.
3. The tone is professional and objective.
4. All extracted items are directly supported by the transcript text.

Fictional Example Input

Transcript Excerpt:

Client: "So, regarding the homepage redesign, we definitely want to keep the blue header. But we're worried about the load time if we add those animations. Can you check if the current server can handle it?" Vendor: "Sure, I'll ask our dev team to run a test. Also, do we have approval for the new copy yet?" Client: "Not yet, Sarah is still reviewing it. Let's wait for her sign-off before we start coding the text sections."

Illustrative Output Shape

Table 1: Confirmed Decisions

Table 2: Open Questions & Action Items

Boundaries

• Do not invent owners if none are mentioned; use "Unassigned".
• Do not provide legal or financial advice based on the transcript.
• Do not summarize the entire meeting; focus only on decisions and open loops.
• This prompt prepares a draft for human review; do not assume these actions are executed automatically.

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.